Page 1 of 1

http does not work, but https works!

Posted: Wed Dec 04, 2013 8:34 pm
by gtzen
Hi:

I created a domain with ssl enabled. While accessed to the http port, http://domain.tld, it shows up default.domain page whereas https://domain.tld shows up the relevant page of the domain. How does the http://domain.tld shows up domain.tld page instead of the default.domain page? Thanks!

Re: http does not work, but https works!

Posted: Wed Dec 04, 2013 8:46 pm
by jhewit
gtzen wrote:Hi:

I created a domain with ssl enabled. While accessed to the http port, http://domain.tld, it shows up default.domain page whereas https://domain.tld shows up the relevant page of the domain. How does the http://domain.tld shows up domain.tld page instead of the default.domain page? Thanks!
A few questions when setting up this domain what did you set for the following options:

Apache Template
Ngix Template

And once you checked SSL support what did you set the following to:

SSL Home

Re: http does not work, but https works!

Posted: Wed Dec 04, 2013 8:54 pm
by gtzen
jhewit wrote:
gtzen wrote:Hi:

I created a domain with ssl enabled. While accessed to the http port, http://domain.tld, it shows up default.domain page whereas https://domain.tld shows up the relevant page of the domain. How does the http://domain.tld shows up domain.tld page instead of the default.domain page? Thanks!
A few questions when setting up this domain what did you set for the following options:

Apache Template
Ngix Template

And once you checked SSL support what did you set the following to:

SSL Home
1.
Apache Template >> Default
Nginx Template >> Default
SSL Home >> public_shtml

I created two domains with SSL enabled with two different site certificates, but both seems to point to the same domain even in ssl mode (https)!

2. I also enabled webstatistics >> webalizer as well as awstats alternatively, but getting a 404 error page at http(s)://domain.tld/(v)stats/ () means alternatives tried.

Re: http does not work, but https works!

Posted: Wed Dec 04, 2013 9:50 pm
by jhewit
gtzen wrote:
jhewit wrote:
gtzen wrote:Hi:

I created a domain with ssl enabled. While accessed to the http port, http://domain.tld, it shows up default.domain page whereas https://domain.tld shows up the relevant page of the domain. How does the http://domain.tld shows up domain.tld page instead of the default.domain page? Thanks!
A few questions when setting up this domain what did you set for the following options:

Apache Template
Ngix Template

And once you checked SSL support what did you set the following to:

SSL Home
1.
Apache Template >> Default
Nginx Template >> Default
SSL Home >> public_shtml

I created two domains with SSL enabled with two different site certificates, but both seems to point to the same domain even in ssl mode (https)!

2. I also enabled webstatistics >> webalizer as well as awstats alternatively, but getting a 404 error page at http(s)://domain.tld/(v)stats/ () means alternatives tried.
Because you set SSL Home to public_shtml here is whats happening:
When accessing using https:// files will be pulled from public_shtml
When accessing using http:// files will be pulled from public_html

If you change SSL Home to public_html they will both pull from public_html.

Re: http does not work, but https works!

Posted: Thu Dec 05, 2013 5:21 am
by gtzen
Like I stated earlier, when I assigned to public_html, the ssl connection resulted an error page whereas the non-ssl (http) results the defaut.domain's index page instead of the newly-created site. So both ways it was a no go.

BTW, what are these Apache and Nginix Templates signify viz. default, hosting and so on?

@forumadmin: Please remove the limitation of embedding max 3 quotes in replies. I got "You may embed only 3 quotes within each other." Thanks!

Re: http does not work, but https works!

Posted: Thu Dec 05, 2013 6:04 pm
by skid
Information about templates in a nutshell

Apache
default - no additional settings, works well for any site
basedir - to fight with phpshells using openbasedir directive
hosting - php limits for each domain (php_admin_value memory/safemode/etc)
phpcgi - tempalte to run php as cgi. can be useful to run php4 or php5.2
phpfcgid - to php as fcgi
wsgi - template to run python projects

Nginx
default - serves static content, works well for most sites
hosting - disable_symlinks directive to protect from symlink atacks
сaching - dynamic pages are cached for 15 min to handle spontaneous traffic aka reddit-effect

DNS
default - general dns records
gmail - predefined records to host mail on google app
child-ns - template for vanity name servers

Re: http does not work, but https works!

Posted: Thu Dec 05, 2013 6:06 pm
by skid
Try to change ssl home afterwards. Also make sure the ip address configured in the panel match the ip you get by pinging domain.

Re: http does not work, but https works!

Posted: Sat Dec 07, 2013 8:19 am
by gtzen
skid wrote:Information about templates in a nutshell

Apache
default - no additional settings, works well for any site
basedir - to fight with phpshells using openbasedir directive
hosting - php limits for each domain (php_admin_value memory/safemode/etc)
phpcgi - tempalte to run php as cgi. can be useful to run php4 or php5.2
phpfcgid - to php as fcgi
wsgi - template to run python projects

Nginx
default - serves static content, works well for most sites
hosting - disable_symlinks directive to protect from symlink atacks
сaching - dynamic pages are cached for 15 min to handle spontaneous traffic aka reddit-effect

DNS
default - general dns records
gmail - predefined records to host mail on google app
child-ns - template for vanity name servers
Thanks for explicit explanation.