SLES 11 SP3. I have a number of virtual hosts running just fine on
port 80. I need to setup one for port 443. I have the certificate
and I have configured everything, but when I browse to the page, I get
a “webpage is not available, err_connection_reset” error. I’ve been
through the apache and ssl logs and I cannot figure out what I am
missing. I have run a secure site on Netware, so I have even compared
my apache config on SLES against my apache config on Netware, but
nothing appears obviously wrong. Any suggestions?
SLES 11 SP3. I have a number of virtual hosts running just fine on
port 80. I need to setup one for port 443. I have the certificate
and I have configured everything, but when I browse to the page, I get
a “webpage is not available, err_connection_reset” error. I’ve been
through the apache and ssl logs and I cannot figure out what I am
missing. I have run a secure site on Netware, so I have even compared
my apache config on SLES against my apache config on Netware, but
nothing appears obviously wrong. Any suggestions?
Thanks,
Ken[/color]
“telnet servername 80” makes a connection
“telnet servername 443” returns “could not open connection to the
host, on port 443: connect failed”
So it looks like it just isn’t listening. I’ve turned off the
firewall to verify, so that isn’t the problem.
If it is not listening, then the Apache config is probably still wrong,
though not getting errors about it is a little surprising. Have you tried
the ‘configtest’ option for the ‘apache2’ init script to see if anything
is amiss there (I assume you’ve restarted Apache httpd since setting
things up)? Anything in error_log under /var/log/apache2 or any way to
get more-verbose output? I think there’s an option to show parsing as it
happens with the service, but I do not have a box nearby to verify.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
On 11/03/2014 21:06, KeN Etter wrote:
[color=green]
Figured out part of the problem…commenting out the 2 lines listed
below in the listen.conf file and then I can access the pages.
#
<IfDefine !NOSSL>
Listen 443
#
Which setting am I missing that would cause this?[/color]
The “correct” way to enable SSL support with Apache on SLES/OES is to
set the SSL flag in /etc/sysconfig/apache2 by adding SSL to
APACHE_SERVER_FLAGS.[/color]
Thanks Simon! I figured it was something like that but I hadn’t found
it yet.
[color=blue]
That would then define SSL at Apache startup thus passing the first test
above.
If it is not listening, then the Apache config is probably still wrong,
though not getting errors about it is a little surprising. Have you tried
the ‘configtest’ option for the ‘apache2’ init script to see if anything
is amiss there (I assume you’ve restarted Apache httpd since setting
things up)? Anything in error_log under /var/log/apache2 or any way to
get more-verbose output? I think there’s an option to show parsing as it
happens with the service, but I do not have a box nearby to verify.[/color]
Simon pointed me to the missing config. So all is well now.