Support and News Forum

Hi all,

Been trying to set up an install of 6.2.0-4-Community (latest as of this writing) so the web UI is accessed using 443 only (no HTTP on port 80). I followed the instructions in the FAQ to enable SSL encryption with a self-signed cert. This seems to work fine until I do one additional step: Commenting out "Listen 80" in /etc/apache2/ports.conf. After I make this change, it achieves the desired "HTTPS only" effect, except that the HTML5 console breaks - it will no longer get past the login screen. I can log in using Native Console, but the login screen does nothing when choosing HTML5 Console.

In other words:
- With "Listen 80" commented out, then navigating to the login page via HTTPS, choosing only Native Console allows me to log in. Choosing HTML5 does nothing.
- With "Listen 80" NOT commented out (meaning the server still listens on 80 for HTTP connections), then navigating to the login page still using HTTPS (not HTTP), both Native Console and HTML5 console works as expected.

So my question is why does the HTML5 console break when port 80 is disabled in Apache? Any guidance is appreciated.

(I hope my description above is adequate, but let me know if I can elaborate further on anything)

Thanks!

Follow up to my above post...
While I am still curious about what exactly is breaking by turning off port 80 in /etc/apache2/ports.conf, my workaround is just to leave that option enabled and apply an iptables rule for now.
This achieves effectively the same effect I was looking for:

iptables -A INPUT -i <interface> -d <interfaceIP> -p tcp --dport 80 -j DROP

<interface> is whatever has the IP address you use to access EVE's web UI. By default this is usually pnet0.
<interfaceIP> is of course the IP address of the interface above.