On 29/12/2019 15.18, Carlos E. R. wrote:
On 29/12/2019 14.57, Per Jessen wrote:
Carlos E. R. wrote:
I have done a test:
I copied /etc/apache2/vhosts.d/isengard.valinor.conf to isengard.valinor.bis.conf, listening on port 81. Works instantly.
So the error is not in that file!
For starters you could just put the apache2 apparmor profile in complain mode.
I tried stopping it, no difference.
systemctl stop apparmor
I get:
Error loading http://isengard.valinor:80/: Connection refused
/var/log/apache2/isengard.valinor-access_log:
192.168.1.16 - - [29/Dec/2019:14:11:14 +0100] "GET / HTTP/1.1" 200 710 "-" "Links (2.20.1; Linux 4.12.14-lp151.28.36-default x86_64; GNU C 7.4.1; text)"
/var/log/apache2/isengard.valinor-error_log:
[Sun Dec 29 14:11:14.779263 2019] [apparmor:warn] [pid 23178] (1)Operation not permitted: [client 192.168.1.16:56692] aa_change_hatv call failed [Sun Dec 29 14:11:14.779990 2019] [apparmor:error] [pid 23178] (1)Operation not permitted: [client 192.168.1.16:56692] Failed to change_hat to 'HANDLING_UNTRUSTED_INPUT'
Google has some hits of those aa errors, nothing conclusive. Example: <https://lists.rosenauer.org/pipermail/evergreen/2016-August/001937.html> It appears to be an old *SUSE bug, probably unrelated to my problem. Noise. Hum! Got it working on localhost. Fails on the LAN. I had replaced the "Listen 80" with "Listen 81". Current status: Browsing on localhost now works on both ports 80 and 81. Browsing from the LAN I get "Error reading from socket", both on ports 80 and 81. It is not the firewall, no entries in log. I have a guess what it might be (some "allow from"), but I need sustenace first. I'm getting a headache. . -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)