If I had to guess, the container station might be giving the docker container a new network/ip address, one that the NAS is not using so that port 443 works and doesn’t conflict with the NAS. If you start the container station then inspect the container you might see how they do it, but macvlan is typically how you would configure it.

services: my-lan-service: image: nginx:latest container_name: lan_container # 1. Attach the service to the custom macvlan network networks: lan_network: ipv4_address: 192.168.1.200 # The dedicated LAN IP for this container # 2. Ports are exposed directly to the LAN; do NOT use the “ports” block restart: unless-stopped

networks: lan_network: driver: macvlan driver_opts: parent: eth0 # Change to your host’s physical network interface name ipam: config: - subnet: 192.168.1.0/24 # Matches your physical local network setup gateway: 192.168.1.1 # Your physical router IP

I wonder if this is an Nvidia thing. It’s been working quite well on my AMD hardware. I played for like 4 hours yesterday and then left the game open for 2 more by accident and it was still stable. I did lower some environment graphics settings to reduce microstutters but otherwise it’s running quite well at 60 fps.

Check ethtool to make sure your link is actually operating at 2.5gbit with full duplex. You may need to make sure the kernel module for that ethernet nic supports 2.5gbit.