Blank Welcome to SWAG Screen

[NathanielH-snek]

Not sure what I'm doing incorrectly but I'm not getting the foundry login in screen. I only seem to get this

I'm genuinely not sure what I'm doing incorretly as the containers and associated processes seem to be working fine. Here's my config file for the containers.

version: "3.8"

services:
  duckdns:
    image: ghcr.io/linuxserver/duckdns
    container_name: duckdns
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York                                     # replace with your local timezone https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
      - SUBDOMAINS=notroll20                                   # replace with to your DuckDNS subdomain name.
      - TOKEN=<my_token>                                    # replace with your DuckDNS token here
    restart: unless-stopped

  foundry:
    container_name: foundry
    hostname: foundry
    image: direckthit/fvtt-docker:latest
    expose:
      - 30000
    volumes:
      - ~/foundry/data:/data/foundryvtt     # replace with the correct path to your foundry config dir
      - ~/foundry/resources:/data/foundryvtt/Data/resources  # replace with the correct path to your resources
      - ~/foundry/zip:/host                     # 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:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York                                     # replace with your timezone
      - URL=notroll20.duckdns.org                               # replace with this to your DuckDNS hostname
      - VALIDATION=http
      - DUCKDNSTOKEN=<my_token>                             # replace with your DuckDNS token here
      - EMAIL=<my_email>                              # replace with your email address (optional).
    volumes:
      - ./swag:/config
    ports:
      - 80:80
      - 443:443
    restart: unless-stopped

[StarGeekSpaceNerd]

What is the URL you are using? I think the image you show is what you should be getting with http://127.0.0.1 or http://localhost You have Foundry set on port 30000, so your URL should be http://127.0.0.1:30000 or http://localhost:30000

Edit: Or course, all that isn't correct if you are not viewing it locally. I'm not sure what needs to be set to redirect it correctly if you're viewing that over the internet rather than local network.

[NathanielH-snek]

What is the URL you are using? I think the image you show is what you should be getting with http://127.0.0.1 or http://localhost You have Foundry set on port 30000, so your URL should be http://127.0.0.1:30000 or http://localhost:30000

Edit: Or course, all that isn't correct if you are not viewing it locally. I'm not sure what needs to be set to redirect it correctly if you're viewing that over the internet rather than local network.

Yeah I'm testing this with my domain over the internet because presumably that's how my players will be accessing the game. I haven't tried accessing over the local network though that'd be a good troubleshooting step.

Edit the url I'm using is https://(mydomain).duckdns.org

[StarGeekSpaceNerd]

I would say that your problem lies with the Configure reverse proxy section. Your image shows that you are connecting to the swag, but the reverse proxy isn't redirecting you to Foundry. So I'd guess that something is misconfigured in this area.

Network stuff isn't my strong suit, so there isn't much I can otherwise help with except some educated guesses.

[NathanielH-snek]

Unfortunately networking isn't my strong suit either. Thank you for your help 🙂, maybe it's time for me to git gud with the networking stuff.

[ChefsSlaad]

ok, lets find out if foundry is running at all.

on your internal network, go to

http://<ip-address>:30000 

and verify that you can access foundry. if that's working, your reverse proxy is incorrect (as @StarGeekSpaceNerd said).

could you just verify that you have configured foundry in swag like so and have added your duckdns adress in the line that starts with server_name?

after you've done that, your should restart using

docker-compose restart

please let me know the result

[NathanielH-snek]

Hey thanks for your help, I finally had a chance to troubleshoot. I checked the internal IP and I don't think foundry was running at all, but I also discovered that I was having some drive errors so I've ordered a new one and am awaiting that for further testing. I'll update again soon.

[NathanielH-snek]

Yep so I'm still having issues. I changed the paths in the foundry config file since the "config" folder didn't exist and that didn't seem to fix it. I also am not sure if I installed foundry correctly as I included the path to the zip file form the download URL as well as the download URL in the configuration file. Visiting my IP doesn't produce anything either so it seems like foundry isn't even working at all.

[ChefsSlaad]

if you run docker-compose up (without -d) you will get a verbose output of your deployment. that should give us some hints. Could you copy and paste that output in this ticket?

[NathanielH-snek]

Attaching to duckdns, foundry, swag
foundry  | Entrypoint | 2024-06-27 01:03:55 | [info] Starting felddy/foundryvtt container v12.327.0
foundry  | Entrypoint | 2024-06-27 01:03:55 | [info] Foundry Virtual Tabletop 12.327 is installed.
foundry  | Entrypoint | 2024-06-27 01:03:55 | [info] Installation not yet licensed.
foundry  | Entrypoint | 2024-06-27 01:03:55 | [warn] Unable to apply a license key since neither a license key nor credentials were provided.  The license key will need to be entered in the browser.
foundry  | Entrypoint | 2024-06-27 01:03:55 | [info] Setting data directory permissions.
foundry  | Entrypoint | 2024-06-27 01:03:55 | [info] Starting launcher with uid:gid as foundry:foundry.
foundry  | Launcher | 2024-06-27 01:03:55 | [info] Generating options.json file.
duckdns  | [migrations] started
duckdns  | [migrations] no migrations found
duckdns  | usermod: no changes
duckdns  | ───────────────────────────────────────
duckdns  |
duckdns  |       ██╗     ███████╗██╗ ██████╗
duckdns  |       ██║     ██╔════╝██║██╔═══██╗
duckdns  |       ██║     ███████╗██║██║   ██║
duckdns  |       ██║     ╚════██║██║██║   ██║
duckdns  |       ███████╗███████║██║╚██████╔╝
duckdns  |       ╚══════╝╚══════╝╚═╝ ╚═════╝
duckdns  |
duckdns  |    Brought to you by linuxserver.io
duckdns  | ───────────────────────────────────────
duckdns  |
duckdns  | To support the app dev(s) visit:
duckdns  | DuckDNS: https://www.patreon.com/user?u=3209735
duckdns  |
duckdns  | To support LSIO projects visit:
duckdns  | https://www.linuxserver.io/donate/
duckdns  |
duckdns  | ───────────────────────────────────────
duckdns  | GID/UID
duckdns  | ───────────────────────────────────────
duckdns  |
duckdns  | User UID:    1000
duckdns  | User GID:    1000
duckdns  | ───────────────────────────────────────
duckdns  |
swag     | [migrations] started
swag     | [migrations] 01-nginx-site-confs-default: skipped
swag     | [migrations] done
swag     | usermod: no changes
swag     | ───────────────────────────────────────
swag     |
swag     |       ██╗     ███████╗██╗ ██████╗
swag     |       ██║     ██╔════╝██║██╔═══██╗
swag     |       ██║     ███████╗██║██║   ██║
swag     |       ██║     ╚════██║██║██║   ██║
swag     |       ███████╗███████║██║╚██████╔╝
swag     |       ╚══════╝╚══════╝╚═╝ ╚═════╝
swag     |
swag     |    Brought to you by linuxserver.io
swag     | ───────────────────────────────────────
swag     |
swag     | To support the app dev(s) visit:
swag     | Certbot: https://supporters.eff.org/donate/support-work-on-certbot
swag     |
swag     | To support LSIO projects visit:
swag     | https://www.linuxserver.io/donate/
swag     |
swag     | ───────────────────────────────────────
swag     | GID/UID
swag     | ───────────────────────────────────────
duckdns  | Detecting IPv4 via DuckDNS
swag     |
swag     | User UID:    1000
swag     | User GID:    1000
swag     | ───────────────────────────────────────
swag     |
foundry  | Launcher | 2024-06-27 01:03:55 | [warn] No 'Admin Access Key' has been configured.
foundry  | Launcher | 2024-06-27 01:03:55 | [info] Starting Foundry Virtual Tabletop.
swag     | using keys found in /config/keys
duckdns  | DuckDNS request at Wed Jun 26 21:03:56 EDT 2024 successful. IP(s) unchanged.
duckdns  | [custom-init] No custom files found, skipping...
duckdns  | [ls.io-init] done.
swag     | Variables set:
swag     | PUID=1000
swag     | PGID=1000
swag     | TZ=America/New_York
swag     | URL=notroll20.duckdns.org
swag     | SUBDOMAINS=
swag     | EXTRA_DOMAINS=
swag     | ONLY_SUBDOMAINS=false
swag     | VALIDATION=http
swag     | CERTPROVIDER=
swag     | DNSPLUGIN=
swag     | [email protected]
swag     | STAGING=
swag     |
foundry  | FoundryVTT | 2024-06-27 01:04:00 | [info] Running on Node.js - Version 18.20.3
foundry  | FoundryVTT | 2024-06-27 01:04:00 | [info] Foundry Virtual Tabletop - Version 12 Build 327
foundry  | FoundryVTT | 2024-06-27 01:04:00 | [info] User Data Directory - "/data"
foundry  | FoundryVTT | 2024-06-27 01:04:00 | [info] Application Options:
foundry  | {
foundry  |   "awsConfig": null,
foundry  |   "compressSocket": false,
foundry  |   "compressStatic": false,
foundry  |   "cssTheme": "foundry",
foundry  |   "fullscreen": false,
foundry  |   "hostname": null,
foundry  |   "hotReload": false,
foundry  |   "language": "en.core",
foundry  |   "localHostname": null,
foundry  |   "passwordSalt": null,
foundry  |   "port": 30000,
foundry  |   "protocol": null,
foundry  |   "proxyPort": null,
foundry  |   "proxySSL": false,
foundry  |   "routePrefix": null,
foundry  |   "sslCert": null,
foundry  |   "sslKey": null,
foundry  |   "updateChannel": "stable",
foundry  |   "upnp": false,
foundry  |   "upnpLeaseDuration": null,
foundry  |   "world": null,
foundry  |   "adminPassword": null,
foundry  |   "deleteNEDB": false,
foundry  |   "noBackups": false,
foundry  |   "serviceConfig": null
foundry  | }
foundry  | FoundryVTT | 2024-06-27 01:04:00 | [warn] Software license requires signature.
foundry  | FoundryVTT | 2024-06-27 01:04:00 | [info] Server started and listening on port 30000
swag     | Using Let's Encrypt as the cert provider
swag     | E-mail address entered: [email protected]
swag     | http validation is selected
swag     | Certificate exists; parameters unchanged; starting nginx
swag     | The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
swag     | **** The following site-confs have extensions other than .conf ****
swag     | **** This may be due to user customization. ****
swag     | **** You should review the files and rename them to use the .conf extension or remove them. ****
swag     | **** nginx.conf will only include site-confs with the .conf extension. ****
swag     | /config/nginx/site-confs/foundryvtt
swag     | [custom-init] No custom files found, skipping...
swag     | [ls.io-init] done.
swag     | Server ready
foundry  | FoundryVTT | 2024-06-27 01:04:25 | [info] Created client session 9f0accf9d1fd85847b088faf

Here's the output, the only thing I catch is that my install isn't licensed on a cursory glance. Also I do have my foundryvtt file configuration without a .conf extension that could also be an issue?

[NathanielH-snek]

Changing that produced a "no such directory exists" for my ssl conf file. I tried changing that path to reflect the actual path in my setup to the ssl.conf file but it still says that no such directory exists. This means that either A the folder containing the .conf files have the wrong permissions or B that something isn't being mounted correctly in the docker contrainer correct?

[ChefsSlaad]

Thanks for this. I found some errors in my docker-compose.yaml file that I corrected.

the warnings in foundry you're getting are just configurations you need to do later on. You will be prompted for your licence key and will be asked to provide an admin password to setup foundry. all of this happens later.

what you can do to fix your errors (hopefully):

change

    expose:
      - 30000

to 

    ports:
        -30000:30000

this will allow you to connect to foundry from you local network by entering http://your.local.ip:30000

that will allow you to test your foundry setup

I also added a comment in the duckdns docker-compose.yaml prompting you to update the following path:

    volumes:
      - /path/to/your/swag/directory:/config                    # replace with the correct path to your resources

this will actually allow you to configure swag so that you can place a foundryvtt.conf file in the correct directory.

could you check this out and let me know how it goes?