Yeah, I looked at those config but they didn’t work with NginxProxyManager. 

i dont know on that one i will have to have a look at it and test it on my system and get back to you

Am I supposed to install the Linux version or the node.js version since I plan on running Foundry as a dedicated server?

i did it based on the Linux version and that works well, but from what i can tell the node.js one could work as well

Edited April 16, 20215 yr by fithwum

Minor question, when accessing Foundry through swag i am required to append a path like /setup or /join in order for the Foundry page to show up. If I dont do that it shows the swag landing page. When I connect over IP from the local network it automatically redirects to the above mentioned paths. Any idea if that is fixable?

5 hours ago, rumo said:

Minor question, when accessing Foundry through swag i am required to append a path like /setup or /join in order for the Foundry page to show up. If I dont do that it shows the swag landing page. When I connect over IP from the local network it automatically redirects to the above mentioned paths. Any idea if that is fixable?

I have my SWAG forward setup so that my players just enter https://foundryvtt.<domain> and it forwards to the '/join' url, swag config below, note the /join on the end of the proxypass line.  I then VPN in to my network access the setup page via local IP bookmark with /setup on it, I try to keep admin and management ui's to things not externally facing, as I pretty much never have to go in there once a game is setup. 
 

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name foundryvtt.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app foundryvtt;
        set $upstream_port 30000;
        set $upstream_proto https;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port/join;

        proxy_max_temp_file_size 2048m;
    }
}

This works for me either with or without the /join, if I have a world started and don't have the '/join' in proxypass line it will default to that, otherwise it just gives me a white page with Foundry VTT and version number until I start a world. 

Edited June 1, 20215 yr by Dawthus

The container doesnt seem to work in bridge mode, and I need to use bridge mode to do port mapping since i want to run two instances of Foundry (two different licenses) on my unraid server and both cant have port 30000.

 

 

EDIT: Hmmmm, turning ONE to bridge mode with host port 30000 mapped to container port 30000 works but the other one with a port mapping from host port 30001 to container port 30000 doesnt....

 

EDIT2: Looks like when i change the Host Port template variable it changes the container port.....

 

Why wont it let me change the container port value?

 

EDIT3: aparently unraid doesnt let you change container ports, gotta just remove and add it. All working now! 

Edited June 2, 20215 yr by Taako

I have mine on a custom proxynet for use with swag, you might be able to run that way to have 2 instances running.

 

Glad to see you got it working tho

Edited June 2, 20215 yr by fithwum

has anyone had luck configuring a jitsi on unraid with foundryvtt on unraid?

My group uses TeamSpeak3 and sometimes nextcloud talk.

1 hour ago, beckett said:

has anyone had luck configuring a jitsi on unraid with foundryvtt on unraid?

We just use Discord.

Is there a way to install backend support for Plutonium? If so can anyone point me in the right direction or link a guide? Thanks in advance!

Im having a problem where i can access fine fvtt trough a domain but when i paste the key and get to the configuration to start a world the "play" button goes grey and do nothing. If i access directly trough unraid:port everything works.

 

Im using this proxy manager:

As options i enable Cache assets, Websocket support, Force SSL (letsencrypt) and i added in the custom configuration this bit:

add_header Referrer-Policy "same-origin" always;
add_header Access-Control-Allow-Origin https://domain.redacted always;
client_max_body_size 1024M;
fastcgi_buffers 64 4K;
set $upstream_app FoundryVTT;
proxy_max_temp_file_size 1024m;

 

The complete automated config file looks like this:

# ------------------------------------------------------------
# domain.redacted
# ------------------------------------------------------------


server {
  set $forward_scheme http;
  set $server         "192.168.8.105";
  set $port           30000;

  listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443;


  server_name domain.redacted;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-2/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-2/privkey.pem;

    # Force SSL
    include conf.d/include/force-ssl.conf;


proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


  access_log /data/logs/proxy-host-2_access.log proxy;
  error_log /data/logs/proxy-host-2_error.log warn;

add_header Referrer-Policy "same-origin" always;
add_header Access-Control-Allow-Origin https://domain.redacted always;
client_max_body_size 1024M;
fastcgi_buffers 64 4K;
set $upstream_app FoundryVTT;
proxy_max_temp_file_size 1024m;

location / {

    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    

    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

proxy.conf:

add_header       X-Served-By $host;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Scheme $scheme;
proxy_set_header X-Forwarded-Proto  $scheme;
proxy_set_header X-Forwarded-For    $remote_addr;
proxy_set_header X-Real-IP          $remote_addr;
proxy_pass       $forward_scheme://$server:$port;

 

options.json

{
  "port": 30000,
  "upnp": false,
  "fullscreen": false,
  "hostname": "domain.redacted",
  "routePrefix": null,
  "sslCert": null,
  "sslKey": null,
  "awsConfig": null,
  "dataPath": "/foundry/data",
  "proxySSL": true,
  "proxyPort": 443,
  "minifyStaticFiles": true,
  "updateChannel": "release",
  "language": "it.FoundryVTT - it-IT",
  "world": null
}

 

On this proxy i have all sort of hosts: plex, wikijs (that runs on nodejs and has no problems of sorts), my firm site, a gitlab etc and foundryvtt is the only one I am having problems with.

 

What Im doing wrong?

Edited August 15, 20214 yr by exico

1 hour ago, exico said:

fvtt

What happens on port 30000? Is it a http website or something different? You can't use Nginx server configs for every type of data. Some need "stream" configurations.

 

Or does it work with swag? Then we could try to compare the configs.

Fvtt docker is on port 30000. Is a web application based on nodejs for D&D and more

Quick note here, if you're also using 5eTools/Plut and want to local host the images, set the symlink via the container shell and not unraids!

I can't seem to get this to run on any port other than 30000. I'm using "host" network and tried to remove and re-add the port as host port 30001/default 30001. (suggested above)

 

(Incidentally, I don't see "container port" even showing up in the port config.)

 

Is there a config file I can edit by hand? Anything else I can do?

 

Edited October 25, 20214 yr by ksignorini
more info and pics

32 minutes ago, ksignorini said:

I can't seem to get this to run on any port other than 30000. I'm using "host" network and tried to remove and re-add the port as host port 30001/default 30001. (suggested above)

 

(Incidentally, I don't see "container port" even showing up in the port config.)

 

Is there a config file I can edit by hand? Anything else I can do?

 

 

 

I worked it out. Had to manually change the settings file for Foundry to target 30001. That's in the "config" folder: options.json. I suppose you could connect at 30000 first, change it in Foundry's settings screen, then adjust the port on the Docker and restart, too.

you should also be able to set your network to bridge and change the port that way. i run mine through swag and they have a config for foundry now i think.

It's actually all been working great up until now, with 3 instances running.

 

Today I updated the container on one of the 3 instances and now I can't get it to restart. I don't know what things might have changed such that it won't start anymore. The other 2 (older) versions are still running fine.

 

There is nothing in the logs.

 

Where should I start looking for what broke?

 

I am not sure why that is happening the update is working fine on my system. the error is normally an unraid error as far as i know

I've been loving this but I am starting to run into version incompatibilities. How should I update? Should I make a PR on the GitHub repo bumping the version? Update from within the app itself?

what version incompatibilities are you running into?

 

Most things can be updated from within the app itself i think even foundry can update from inside now.

Hi there I am having a weird issue with Foundryvtt docker.
I tried settign it up using a reverse proxy with swag.
I can even connect to the Server but am stuck on the default screen then.
It works fine with a using the direct port and duckdns so I am very confused.
I have attached my foundry swag config and the options config from the foundry server.
Thank you so much for your help and all the work you put into these projects.

options.json foundryvtt.subdomain.conf

your site seems to load just fine. in an older post i put up my working proxy config for swag you could have a look at that and see the difference with yours