New answers tagged

0

You're running operating system that implements Wireguard as a kernel module. Your kernel is listening on this port, and since there's no process owning that socket no PID is reported by netstat.


0

All I had to do on Debian 10 "Buster" and Debian 11 "Bullseye" was to open Outbound UDP Port 123 My inbound port 123 is not open. Restarting any service isn't necessary. Results in /var/log/syslog: Debian 10: Sep 23 18:21:19 app systemd-timesyncd[20076]: Synchronized to time server for the first time 194.35.12.189:123 (0.debian.pool....


1

In addition to Matthew's comment suspecting internal nat redirect iptables -vnL -t nat or nft list ruleset ip perhaps you could directly inspect port 80. These are some of the ways to do that: ss -4tlnp -o state LISTENING '( sport = :80 )' lsof -i:80 do a verbose tcpdump do a verbose portscan with nmap or, be even more explicit when testing with curl, ie ...


1

I also had this problem, but the problem turned out to be a missing "ServerName" directive in the section. I suggest trying this modification to your configuration file: <VirtualHost ServerIP:443> ServerName host.domain # This parameter already existed as-is SSLEngine on # These are the parameters I changed (already existed w/ ...


Top 50 recent answers are included