foundryvtt-docker VS docker-swag

Also using the felddy/FoundryVTT, nginx reverse-proxy, and lets-encrypt companion Docker containers.

I already have docker set up for Nextcloud, so threw on this guy, hooking into my existing reverse proxy+letsencrypt https://hub.docker.com/r/felddy/foundryvtt

What can you do 1. Set the default game world in Foundry configuration, that way you won't have to bother with selecting it after restart 2. The docker image has a healthcheck defined, but to my knowledge only Swarm makes use of it, every other orchestrator requires this to be defined separately. Look into azure docs to see how to define it. Have it test the whatever-is-your-url/api/status, compare the script here - this will auto restart the container if it hangs

I'll link to the github discussion I opened, rather than copy/pasting it all here: https://github.com/felddy/foundryvtt-docker/discussions/676

I'm getting ready to run a campaign for some friends using Foundry. To do this I'm running Foundry in a Docker container (https://hub.docker.com/r/felddy/foundryvtt) running on a NUC at my house. I then use NAT to forward the required ports through my firewall so the other players can access it. It sounds more complex than it really is, and I'd be happy to answer any followup questions!

The use-case is as follows; I'm hosting Foundry Virtual Tabletop in a docker container on my NAS for a friend. He does all of his prep work using the copy of Foundry VTT on his personal computer, and then uploads to the NAS using Filebrowser, which I have also set up in a docker container, giving him only access to the Foundry VTT data directory and subdirectories.

I am using this docker image: https://github.com/felddy/foundryvtt-docker I'm getting this error in the console `WebSocket connection to 'wss://foundry.****/socket.io/?session=***&EIO=4&transport=websocket' failed: WebSocket is closed before the connection is established.`

I also run a minecraft server or two from time to time, and three separate instances of Foundry Virtual Tabletop for friends.

I used Mark Feldhousen's foundryvtt-docker docker image for the foundry server, using docker compose: https://github.com/felddy/foundryvtt-docker

I have a NAS on .0.181 and a swag container (on a different port than nginx) on .0.180 that points to my public facing services. For obvious reasons, I don't want my public domain to point to any other ports/addresses on my home network. Additionally, as elegant as swag is, it requires authentication and so won't work for simple local DNS. I now have one local domain for each server and an nginx instance on each that resolves to my different services on each.

OP is even linking the Github... https://github.com/linuxserver/docker-swag

I have an UnRAID server with a few services (Jellyfin, Nextcloud, etc.) running on it behind Linux Servers' SWAG reverse proxy container, which is built on Nginx and Let's Encrypt. This is pointed to a DuckDNS link, which is then pointed at my domain with a CNAME. So I can access Jellyfin, for example, at jellyfin.mydomain.com. A few weeks ago, due to seemingly unrelated issues, I got a new modem/router, an Arris SURFboard G34. For the first few weeks, everything was working as before. But now, when on my LAN, I can't get to my services at the proxied domain. It times out every time. There are no errors in SWAG's logs, nothing seems amiss in the router's web interface, and the services are available both at their IP:port address and, when not on my LAN, I can access them at the domain no problem.

Reverse proxy, probably? I use Docker SWAG, setup here, with DuckDNS and it works really well for me. There are of course many ways to reverse proxy, as I linked to earlier.