Server connectivity troubleshooting reddit / selfhosted ---------------------------------------------------------------------- cinclodes · 2023-12-23 19:10 I've new to selfhosting, looking for some advice troubleshooting connection issues. I'm experiencing connectivity issues with my selfhosted stack running running on my SBC. I'm forwarding ports 80 and 443 to my server and updated my dns records, but the connecting is timing out: $ curl -v https://example.com * Host example.com:443 was resolved * IPv6: (none) * IPv4: 12.34.567.89 * Trying 12.34.567.89:443... * connect to 12.34.567.89 port 443 from 192.168.1.67 port 47430 failed: Connection timed out * Failed to connect to example.com port 443 after 133362 ms: Couldn't connect to server curl: (28) Failed to connect to example.com port 443 after 13362 ms: Couldn't connect to server It *sometimes* goes through, but it's about 1/10. Ping always works fine: $ ping example.com PING example.com (12.34.567.89) 56(86) bytes of data. 64 bytes from 12.34.567.89 (12.34.567.89): icmp_seq=1 ttl=64 time=1.39 ms 64 bytes from 12.34.567.89 (12.34.567.89): icmp_seq=1 ttl=64 time=7.82 ms ^C --- example.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 1.388/4.606/7.824/3.218 ms My router's ports are open: $ sudo nmap -Pn example.com Starting Nmap 7.94 ( https://nmap.org ) at 2023-12-23 13:00 CST Nmap scan report for example.com (12.34.567.89) Host is up (0.0035s latency). Not shown: 996 closed tcp ports (reset) PORT STATE SERVICE 53/tcp open domain 80/tcp open http 111/tcp filtered rpcbind 443/tcp open https Nmap done: 1 IP address (1 host up) scanned in 1.44 seconds As are my server's: $ sudo nmap -Pn 192.168.1.200 Starting Nmap 7.94 ( https://nmap.org ) at 2023-12-23 13:04 CST Nmap scan report for orangepi5-2.attlocal.net (192.168.1.200) Host is up (0.0067s latency). Not shown: 996 closed tcp ports (reset) PORT STATE SERVICE 22/tcp open ssh 80/tcp open http 111/tcp open rpcbind 443/tcp open https MAC Address: AA:BF:30:8E:86:FB (Unknown) Nmap done: 1 IP address (1 host up) scanned in 0.46 seconds I'm running Nextcloud and Caddy in docker, but I'm pretty sure they're not the issue as I'm not even getting a connection to the server, and replacing them with a simple http server on the host yeilds the same results. Results online for troubleshooting connection issues are generally DNS issues, which I'm pretty sure is not the case here. Any guideance for where to go from here would be greatly appriciated, as this is about the extent of my network troubleshooting knowledge. ---------------------------------------------------------------------- shoesli_ · 2023-12-23 20:35 What kind of router do you have, Opnsense? Port 53 is open, and I saw that one hostname was orangepi5. Maybe you have created a DNS loop or something? ---------------------------------------------------------------------- arcadianarcadian · 2023-12-24 11:06 connect to 12.34.567.89 port 443 from 192.168.1.67 port 47430 failed: Connection timed out It's not DNS. DNS works and resolves the IP, done. It appears OP's problem on after DNS. ---------------------------------------------------------------------- arcadianarcadian · 2023-12-24 11:08 Is there any explicit routing rule on your router? Ping works with ICMP and does not rely on TCP. ---------------------------------------------------------------------- cinclodes · 2023-12-24 17:08 Thanks for your comment. In the "Packet Filtering" section of my AT&T router there are a number of rules: * Drop IPv4 & IPv6 Ingress LAN, egress WAN, TCP destination [1.2.3.4](http://1.2.3.4) port 80 * Drop IPv4 & IPv6 Ingress LAN, egress WAN, TCP destination 1:2:3::4 port 80 * Drop IPv4 Ingress LAN, egress WAN, TCP port 21 * Drop IPv6 Ingress WAN egress LAN tcp port 80 * Drop IPv6 Ingress WAN egress LAN It's dropping all ipv6 packets, but that shouldn't be a problem since I'm using ipv4. There's also a "Firewall Advanced" page with settings to allow incoming ICMP echo reqeusts to LAN, but block them on LAN and WAN devices. ---------------------------------------------------------------------- arcadianarcadian · 2023-12-24 20:15 Those are Firewall rules, Routing rules are different. ---------------------------------------------------------------------- cinclodes · 2023-12-25 03:41 Ok, I've looked through all the router's settings pages and haven't been able to find anything related to routing rules. Nearly all the settings appear to be defaults. Are there tools like ping that will test TCP/UDP connections? ---------------------------------------------------------------------- kmisterk · 2023-12-25 23:31 ## Post Removed Hey, cinclodes! Thanks for your submission on selfhosted. Your post has been removed due to a violation of the purpose of the subreddit: **Self Hosting** ## Not Self-Hosted When it comes to posts regarding applications in this subreddit, they must feature a self-hosted tool, or a tool that *can be* self-hosted, or some kind of related information, help request, or otherwise related to a tool that is something that one can self-host. If you believe this post *is in fact* relevant to /r/selfhosted, feel free to [message the mods](https://www.reddit.com/message/compose/?to= /r/selfhosted&subject=Removed For Not Being Self- Hosted&message=[Removed Post](https://www.reddit.com/r/selfhosted/comments/18pcnl8/-/\)) with your concerns.