ChefsSlaad / foundry_swag_docker

a how-to on running foundry-vtt in a docker container and securing the connection using nginx and swag
MIT License
28 stars 3 forks source link

I am just lost... #3

Closed Usurper-King closed 1 month ago

Usurper-King commented 1 month ago

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. Screenshot 2024-06-17 171657 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:

`# 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.

    # make sure ssl is enabled
    include~/swag-foundry/swag/nginx/ssl.conf;

    client_max_body_size 0;
    ssl_session_cache shared:SSL:10m;
    proxy_buffering off;

    location / {
        include~/swag-foundry/swag/nginx/proxy-confs;

        resolver 127.0.0.11 valid=30s;

        set $upstream_proto http;
        set $upstream_app foundry;
        set $upstream_port 30000;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;
        } 

}`

So with all this I cannot reach the site. Screenshot 2024-06-17 172216

Thanks in advance for every helping hand!

ChefsSlaad commented 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:

  1. you are using a VPN
  2. your ISP is using its own NAT service -> In this case, you could request your ISP give you a public IP address.
  3. your firewall is blocking incoming trafic -> in this case look at the steps in https://github.com/ChefsSlaad/foundry_swag_docker/tree/main?tab=readme-ov-file#test
  4. You have a second internal router -> Tis is called double NAT and it makes self hostng pretty horrible. Connect your computer directly to the router using a utp cable and try again.

Have a look at these steps and see if it helps. Let me know :)

ChefsSlaad commented 1 month ago

just to let you know, I've updated the guide, fixing some of the error other users found.

ChefsSlaad commented 1 month ago

This issue has been closed. If you problem persists, please get in touch and I will reopen this issue