I’ve come to take the verified badge with a big grain of salt. Some modern games that they mark as verified are pretty unplayable imho.

Commandos, I should have said.

It’s more like the Commando or Shadow Tactics series, if you’ve heard of those. Not like Age of Empires or Warcraft.

Actual Budget has been awesome for my partner and me.

Neither I or the person I was replying to were talking about frame gen.

As for the latency, not in a way that I notice. I’d rather play 80 or more fps upscaled with minute artifacts that I don’t notice, than 40 fps native 4k, just as I said. It feels much better to me, even if it’s placebo.

I’m sure you’re not alone but can I ask why? Some games use it better than others, and the tech has come a long way. If I have to choose between native 4k and 40fps, or 80 or even more fps with tiny artifacts that I only really notice when I’m actively pixel peeping… I mean, I’ll take the latter, personally.

I was just pointing out that you don’t buy the game. A more appropriate comment might have been something like, “I won’t be buying any of their content”.

It’s free to play.

I mean, it’s not like the Steam deck was the first device that could suspend games.

I hope Canada can get some better prices out of this.

What is femme about Wyll, Halsin, or Minsc? What is butch about Shadowheart, or Minthara?

Also, did you consider that losing a battle meant you should consider alternative tactics?

I am not a huge fan of the game for the record.

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?

https://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-14_access.log, proxy-host-14_error.log, or error.log. Just nothing at all. When I access from outside the network, entries in the access 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. https://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?

https://puu.sh/Ks252/fa872908d9.png

(Also, I do not think NAT loopback will be possible with my router/ISP from some reading up I just did)

Aaand wish listed. Thanks!

HAOS on a virtual machine inside on unraid on home server made from old pc parts.

I don’t know what corner I’m backed into mate.