Closed Usurper-King closed 1 month ago
It looks like duckdns is not getting a response from your system. there could be one of two reasons:
looking a https://whatismyipaddress.com/hostname-ip it appears that wiederaufbauerel.duckdns.org directs to a datacenter in Frankfurt am Main. It looks like:
Have a look at these steps and see if it helps. Let me know :)
just to let you know, I've updated the guide, fixing some of the error other users found.
This issue has been closed. If you problem persists, please get in touch and I will reopen this issue
Hi there,
first of all: thank you for the very detailed guide. I am a absolut beginner to all of this and I managed to follow through with every single step of the guide.
I did all the steps of the preparations, setting up the host and setting up the containers. I have all three containers running and did configure the reverse proxy.
I configured everything to my knowledge within the code from the guide.
`version: "3.8"
services: duckdns: image: ghcr.io/linuxserver/duckdns container_name: duckdns environment:
TOKEN= -my token-
replace with your DuckDNS token here
restart: unless-stopped
foundry: container_name: foundry hostname: foundry image: direckthit/fvtt-docker:latest expose:
~/swag-foundry/FoundryVTT-12.327.zip # replace with the correct path to your foundry-x.x.x.zip file restart: unless-stopped
swag: image: ghcr.io/linuxserver/swag container_name: swag cap_add:
`# only serve https map $http_upgrade $connection_upgrade { default upgrade; '' close; }
server { listen 443 ssl http2; server_name wiederaufbauerel.duckdns.org www.wiederaufbauerel.duckdns.org ; # add your domain name here. if you want to use both with and without www add both here.
}`
So with all this I cannot reach the site.![Screenshot 2024-06-17 172216](https://github.com/ChefsSlaad/foundry_swag_docker/assets/173076400/0e64661a-e177-47f1-9445-fcbaab715c7a)
Thanks in advance for every helping hand!