Url Not Found With Https

[century1stop]

Hello,

Currently checking out the trial version, installed to a FQDN over standard http, no control panel just Apache, worked nicely. Decided to install ssl on the server, and when I switched to https, I get the messge "the requested url not found". Url over http still work. Am I doing anything wrong? Thanks

[Michael]

It sounds like a server issue can you PM your url and also are you using the .htaccess to force https? are you also using the correct root url which should be pointing to the public_html and not the blesta install itself.

[century1stop]

PMed

nope not using .htaccess

and in httpd.conf <virtualhost > /var/www/domain/public_html

[serge]

if you create a hello.txt file having as content: Hello

 

 

and place this file at the root of your blesta install folder

 

are you able to load above file with http and https.

and see the hello in the loaded page

 

if you have issue on that, it's mean it's not related to blesta config/parameters, but from your webserver

 

-----------------------------------------------

 

above test is for static content and next you do same kind of test for dynamic content (php).

 

info.php having as content:

 

<?php

// Show all information, defaults to INFO_ALL
phpinfo();

?>

[Paul]

It sounds to me like the HTTPS virtual host does not point to the same document root. Serge's suggestion of adding a text file there and testing if it'll load via http and https is a good test. If it doesn't load in both places, they must have different doc roots.

[century1stop]

Hi

Thanks for the suggestion. 

 

Guess it's the Blesta install after all. Works nicely over http and I get a url not found over https.

 

Does this mean I need to have <virtualhost *:443> within httpd.conf as well? Directory wise, it's the same var/www/domain/public_html

[Paul]

What does your apache config look like?

[century1stop]

I have this in /conf/httpd.conf

 

<VirtualHost *:80>

     ServerAdmin webmaster@domain.net

     DocumentRoot /var/www/domain.net/public_html

     ServerName www.domain.net

     ServerAlias domain.net

     ErrorLog /var/www/domain.net/error.log

     CustomLog /var/www/domain.net-access_log common

 

</VirtualHost>

 

and this in /conf.d/sslhost.conf

 

<VirtualHost 12.34.56.78:443>

     SSLEngine On

     SSLCertificateFile /etc/pki/tls/certs/www.domain.net.crt

     SSLCertificateKeyFile /etc/pki/tls/private/www.domain.net.key

     SSLCACertificateFile /etc/pki/tls/certs/Comodo.ca-bundle

 

     ServerAdmin webmaster@domain.net

     DocumentRoot /var/www/domain.net/public_html

     ServerName www.domain.net

     ServerAlias domain.net

     ErrorLog /var/www/domain.net/error.log

     CustomLog /var/www/domain.net-access_log common

</VirtualHost>

 

PHP info in info.php loads in both http and https for domain.net/info.php whereas https://domain.net/blesta/info.php returns with url not found

[Paul]

All IPs are listening on port 80, but only 12.34.56.78 on port 443. Where does the DNS for www.domain.net point?

[century1stop]

This server's isolated, linked to a different hosting platform, using the nameservers as well. Does this cause issues for Blesta?

 

Problem is if I were to configure it *:443 httpd will restart with an error, default being port 80

[Paul]

This server's isolated, linked to a different hosting platform, using the nameservers as well. Does this cause issues for Blesta?

 

I'm not sure what you mean. How is it isolated? The name servers don't matter, I just wonder if the domain is pointing to the IP specified in the vhost for port 443. Maybe you can elaborate.

[century1stop]

No, that's just a dummy IP, apache has it in httpd.conf as well. If you like I can PM the actual url.

 

Configuration seems to be okay from what I gather with php info. Https works when it doesn't access Blesta folder. Is there a possibility I need to install it with https?

[Michael]

 

I have this in /conf/httpd.conf

 

<VirtualHost *:80>

     ServerAdmin webmaster@domain.net

     DocumentRoot /var/www/domain.net/public_html

     ServerName www.domain.net

     ServerAlias domain.net

     ErrorLog /var/www/domain.net/error.log

     CustomLog /var/www/domain.net-access_log common

 

</VirtualHost>

 

and this in /conf.d/sslhost.conf

 

<VirtualHost 12.34.56.78:443>

     SSLEngine On

     SSLCertificateFile /etc/pki/tls/certs/www.domain.net.crt

     SSLCertificateKeyFile /etc/pki/tls/private/www.domain.net.key

     SSLCACertificateFile /etc/pki/tls/certs/Comodo.ca-bundle

 

     ServerAdmin webmaster@domain.net

     DocumentRoot /var/www/domain.net/public_html

     ServerName www.domain.net

     ServerAlias domain.net

     ErrorLog /var/www/domain.net/error.log

     CustomLog /var/www/domain.net-access_log common

</VirtualHost>

 

PHP info in info.php loads in both http and https for domain.net/info.php whereas https://domain.net/blesta/info.php returns with url not found

 

 

I went to your domain without https:// and got this:

Not Found

The requested URL /blesta/info.php was not found on this server

So it might be the servers DNS. Can you turn on Blesta's error reporting please in /config/blesta.php so the errorreporting is -1.

 

I would also check OVH mate. 

HTTPS://

Hmm, domain.net is only partially available

HTTP://

Good, domain.net is up

Reference: http://sitemeer.com/

[century1stop]

the file info.php is no longer in /blesta/info.php, it can't be found. I've relocated it to domain.net/info.php which loads correctly with or without https. It's the Blesta folder that can't be accessed via https.

 

I'll configure error reporting in a jiffy. 

[Michael]

the file info.php is no longer in /blesta/info.php, it can't be found. I've relocated it to domain.net/info.php which loads correctly with or without https. It's the Blesta folder that can't be accessed via https.

 

I'll configure error reporting in a jiffy. 

 

I can't get on the site mate, and Sitemeer says: Hmm, domain.net is only partially available

[century1stop]

is it with or without https?

 

edit: sitemeer report shouldn't be a problem, just checked 2 nodes and both are down

[Michael]

is it with or without https?

 

edit: sitemeer report shouldn't be a problem, just checked 2 nodes and both are down

 

both servers down? or up haha and I did http:// no ssl.

 

It's up now though for me  Can you make a new folder called test and see if Blesta works fine there? It might be a folder issue. And do you have a caching in place?

[century1stop]

You are quite right, it really is a folder issue.

I created folder test and copied php info file there /test/info.php and I have the same issue.

Any way I can resolve it?

[mrrsm]

You are quite right, it really is a folder issue.

I created folder test and copied php info file there /test/info.php and I have the same issue.

Any way I can resolve it?

I'm guessing this is a linux server.

If you check the folders owner:group that does work and use that same owner:group combo on the new folder does it work.

After you do that, check the permissions as well.

[century1stop]

I'm guessing this is a linux server.

If you check the folders owner:group that does work and use that same owner:group combo on the new folder does it work.

After you do that, check the permissions as well.

But should it affect at all? I mean since everything works with http and https being the problem area, ownership or permissions should render folders inaccessible regardless protocol

 

edit: yup linux centos 6.5 64bit

[mrrsm]

But should it affect at all? I mean since everything works with http and https being the problem area, ownership or permissions should render folders inaccessible regardless protocol

 

edit: yup linux centos 6.5 64bit

You are right it should not matter.

Are you sure your main httpd.conf is set to load everything in your conf.d folder (it should by default).

[century1stop]

both servers down? or up haha and I did http:// no ssl.

 

It's up now though for me  Can you make a new folder called test and see if Blesta works fine there? It might be a folder issue. And do you have a caching in place?

 

I'm guessing this is a linux server.

If you check the folders owner:group that does work and use that same owner:group combo on the new folder does it work.

After you do that, check the permissions as well.

 

Solved! It was a directory issue that needed to be commented out in ssl.conf

Thanks for your help.