localhost inaccessible to browsers
Having installed Leap 15.4 with KDE on one of my computers, I have a strange problem with browsing, being localhost inaccessible to Firefox (version 101.0) as well as to Chromium and Google Chrome (both version 102.0.5005.xxx). This is very boring for developing a web page. Replacing localhost by "az", the computer's name, or "192.168.2.17", its internal IP address, does not help; these specifications are likewise rejected. But "ping localhost", "ping az" and "ping 192.168.2.17" work fine. There is no problem with accessing any other internal or external address. Any ideas? Thanks in advance, Wolfgang
Wolfgang Mueller wrote:
Having installed Leap 15.4 with KDE on one of my computers, I have a strange problem with browsing, being localhost inaccessible to Firefox (version 101.0) as well as to Chromium and Google Chrome (both version 102.0.5005.xxx). This is very boring for developing a web page.
Replacing localhost by "az", the computer's name, or "192.168.2.17", its internal IP address, does not help; these specifications are likewise rejected.
But "ping localhost", "ping az" and "ping 192.168.2.17" work fine.
There is no problem with accessing any other internal or external address.
Any ideas?
Same one as yesterday :-) is apache actually listening on localhost:80 ? Or 192.168.2.17 ? Easy to verify with "ss -ltn". -- Per Jessen, Zürich (19.2°C)
On Sat, 11 Jun 2022 at 10:21:28 +0200, Per Jessen wrote:
Wolfgang Mueller wrote:
Having installed Leap 15.4 with KDE on one of my computers, I have a strange problem with browsing, being localhost inaccessible to Firefox (version 101.0) as well as to Chromium and Google Chrome (both version 102.0.5005.xxx). This is very boring for developing a web page.
Replacing localhost by "az", the computer's name, or "192.168.2.17", its internal IP address, does not help; these specifications are likewise rejected.
But "ping localhost", "ping az" and "ping 192.168.2.17" work fine.
There is no problem with accessing any other internal or external address.
Any ideas?
Same one as yesterday :-) is apache actually listening on localhost:80 ? Or 192.168.2.17 ? Easy to verify with "ss -ltn".
Having rechecked and corrected my apache2 configuration files, I do not have the acessibility problem described above any more. So, you guessed right - thank you very much! Have a nice weekend, Wolfgang
On Sat, Jun 11, 2022 at 10:21 AM Per Jessen <per@computer.org> wrote:
Same one as yesterday :-) is apache actually listening on localhost:80 ? Or 192.168.2.17 ? Easy to verify with "ss -ltn".
this works fine as sudo but with addtl parameter "p"
sudo ss -ltnp
shows process name and owner fine. ty.
Le 11/06/2022 à 10:16, Wolfgang Mueller a écrit :
strange problem with browsing, being localhost inaccessible to Firefox
in port 80 open in the firewall? jdd -- http://dodin.org http://valeriedodin.com
On Sat, 11 Jun 2022 at 11:18:47 +0200, jdd wrote:
Le 11/06/2022 à 10:16, Wolfgang Mueller a écrit :
strange problem with browsing, being localhost inaccessible to Firefox
in port 80 open in the firewall?
Thank you, Jean-Daniel, but it was an apache2 configuration problem, as I have already pointed out in my reply to Per Jessen. Bye, Wolfgang
participants (4)
-
cagsm -
jdd＠dodin.org -
Per Jessen -
Wolfgang Mueller