I can no longer access the web front end via TLS

Security
1

Dear all

I can no longer access the web front end via TLS. The error message in the browser always reads:

ERR_SSL_PROTOCOL_ERROR

I found the relevant instructions (‘https://www.ipfire.org/docs/optimization/ssl_cert’) and followed them. However, when I get to the last point, ‘/etc/init.d/apache restart’, I get the following error message:

Stopping Apache daemon… Not running. [ WARN ]
Starting Apache daemon…
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:444
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:444
no listening sockets available, shutting down
AH00015: Unable to open logs

When checking which service is listening on port 444, I get the following response:

tcp 0 0 192.168.1.1:444 0.0.0.0:* LISTEN 3019/(squid-1) off (0.00/0/0)

What else can I do to solve the problem?

Many thanks in advance.

Best regards Jürg

2

It looks like you have configured the web proxy to use port 444 which is also being used by the web UI. So you will have to change your proxy port and then reboot and you should be back.

Since you are not able to do this over the UI, the easiest way is to manually stop the proxy and then start apache for the web UI:

/etc/init.d/squid stop
/etc/init.d/apache start

You should then be able to access the web UI.

3 Likes
3

Michael,

many thanks for your support. The issue is fixed now. No idea where the missconfiguration came from…

Best regards Jürg

1 Like