• 1 Post
  • 195 Comments
Joined 11 months ago
cake
Cake day: June 7th, 2024

help-circle


















  • Thanks for the suggestions.

    Ping from PC to docmost.example.com: Pings fine, packet loss.

    Ping from PC to 192.168.1.80: Pings fine, no packet loss.

    Traceroute from PC to docmost.example.com: 1 hop, all <1 ms, to 192.168.1.80

    Traceroute from PC to 192.168.1.80: 1 hop, all <1 ms

    Ping from Nginx container to PC: Pings fine, no packet loss.

    Traceroute from Nginx container to PC: Hops to 172.18.0.1 in <1ms, and then it times out on subsequent hops.

    I decided to try to traceroute from my PC to 172.18.0.1 and 172.18.0.9 which is the actual IP of the Nginx container according to UNRAID, and in both cases they hop to 192.168.1.254 which is my router, and then all subsequent hops time out.

    Do you know why pings would go through without any loss but traceroutes would fail? Any idea what’s going on here?


  • Couldn’t I troubleshoot this by using a different browser, or even incognito mode? Because when I do that, it still times out. I appreciate the explanation and advice. I’m not too worried about it at this stage only because my service I am trying to get working, Docmost, will really only be accessed from my desktop. Plus, as I said in OP, I am enjoying learning about this stuff and want to figure out why this specifically isn’t working for educational purposes, even if I switch to a different solution.