iAmTheTot

Jedi Fallen Order and Jedi Survivor have a really attractive bundle for both, actually. Pretty fun games if you like the soulsbourne formula.

Or just make sure you check isthereanydeal.

Detroit is a great game if you like cinematic, story-driven experience. It’s like a Choose-Your-Own Adventure book, in video-game form. Kind of like an interactive movie.

That is a very strange equivocation to make and not at all like what I said. But if I did give someone a free car, yes I would expect them to take care of it.

Maybe I’m just callous but I just don’t see that as a problem myself. If I’m offering my own self hosted services for friends or family, the least they can do is put in some effort to learn how to use it. If they couldn’t bother, that is their loss.

I wasn’t ignoring you. I explicitly put the caveat after “but” specifically because of what you said.

I mean, even in that regard, I did not find it that hard, but I do have a domain.

Excuse me, I thought the comment I replied to was talking about the setup process of the jellyfin server itself.

I would not let anyone access my self hosted stuff who is not using a password manager and secure passwords.

I have read many people say this, but I don’t understand what they mean by it. When I set up Jellyfin, it was a very simple process.

Nginx forwards all traffic correctly outside of the local network, so accessing docmost.example.com from outside local network works completely as expected, with certs and all.

Could you expound? My understanding of the goal here is that Adguard DNS catches my request for docmost.example.com and redirects it to my UNRAID server, which has Nginx listening for traffic. Nginx then directs to the appropriate IP and port.

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.

It does not look like NAT loopback will be an option for me due to router/ISP.

Thanks for the ping suggestion. Copied from another comment of mine:

When I ping docmost.example.com, looks like Adguard is correctly catching it and routing it to an internal IP 192.168.1.80, which is exactly what I’ve told it to do. I tried to ping anothersub.example.com as well, and it was pinging my duckdns address and timing out. So when I ping, it looks like the packets get through but when I try to access it from a browser, it times out?

puu.sh/Ks252/fa872908d9.png

When I try to connect to docmost.example.com, I do not see anything come up on my proxy-host-##_access.log, proxy-host-##_error.log, or error.log. Just nothing at all. When I access from outside the network, entries in the log show up as expected from the IP I access it from (in this case, my phone off WIFI).

I pinged 192.168.1.85 from within my nginx container and looks like it communicated just fine. puu.sh/Ks29s/367c0b6144.png

Thanks for the ping suggestion. When I ping docmost.example.com, looks like Adguard is correctly catching it and routing it to an internal IP 192.168.1.80, which is exactly what I’ve told it to do. I tried to ping anothersub.example.com as well, and it was pinging my duckdns address and timing out. So when I ping, it looks like the packets get through but when I try to access it from a browser, it times out?

puu.sh/Ks252/fa872908d9.png

If you want to go waaaay back before there was even time tracking, it would no doubt be Maplestory and Warcraft 3.

For games I can provide concrete numbers for, it’s Anno 1800 at nearly 500 hours, Stardew Valley at over 400, and Rocket League at nearly 300.

I love Chrono Cross.