Results 1 to 6 of 6

Thread: Apache https not working

  1. #1
    Join Date
    May 2013
    Beans
    36

    Apache https not working

    Hi,

    I used this tutorial: http://www.howtoforge.com/how-to-set...0-debian-lenny to configure a https-page on my Ubuntu 10.04 LTS (I tried some other tutorials too but with the same result).

    Unfortunately it is still not working, all https-pages are not accessible. The funny thing: there are no helpful information in /var/log/apache2/error.log. Same for /var/log/apache2/ssl_access.log, this file is empty.

    So any ideas whre I could have a lookt/what could be wrong?

    Thanks!

  2. #2
    Join Date
    Dec 2012
    Beans
    66

    Re: Apache https not working

    Check your firewall and make sure port 443 isnt blocked. Why do you think it doesnt work?

  3. #3
    Join Date
    May 2013
    Beans
    36

    Re: Apache https not working

    It is not working because the webpage is not delivered, it can't be accessed from a webbrowser.

    It is not a problem of firewall settings, I can connect to Apache and port 443. Amazingly wget shows this error message:

    OpenSSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

  4. #4
    Join Date
    May 2013
    Beans
    36

    Re: Apache https not working

    Any other ideas?

  5. #5
    Join Date
    Apr 2014
    Beans
    2

    Re: Apache https not working

    Hi Elmi77,

    Did you ever figure out the issue here? I've been searching for hours and can not get this to work. Your post seems to reflect the exact same issue I'm having. I am getting nothing in the apache error logs, and the connection is simply timing out from a browser. My domain works correctly from a non-secure url. I followed multiple tutorials including the one you linked to originally, but I can't figure out what the issue is here. Did you ever figure it out?

    Thanks a lot!

  6. #6
    Join Date
    Apr 2014
    Beans
    2

    Re: Apache https not working

    If anyone else is having the same problem, it turns out I simply did not have port 443 enabled on my server. I'm using an Amazon EC2 instance, so I had to specifically open port 443 for traffic via the EC2 Management Console. Once I did that everything worked as expected.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •