-
|
Dear Community, first of all - thanks for providing this image, it really helped me hosting my Foundry VTT on my Synology NAS. Unfortunately, I am a mere novice when it comes to server administration and Docker, and I ran into some issues. I purchased a second License Key to being able to run two worlds in parallel. So I created a second container and defined the variable Now, everything is running smoothly, the container starts working however I cannot access it via browser. Looking at the protocol, it reports: So, I set up the container a second time, trying to change the command beneath the environment variables.
Standard command looks like this: So I copied that and just changed the port to |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
|
Good question... The server in the container will always listen on port Line 78 in d7bbea8 You need only publish the port to your desired target. In your case This is how it would be accomplished using the CLI: docker run \
--env FOUNDRY_USERNAME='<your_username>' \
--env FOUNDRY_PASSWORD='<your_password>' \
--publish 40000:30000/tcp \
--volume <your_data_dir>:/data \
felddy/foundryvtt:release |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I could change the port, so the local port is 40000 now, while the container port remains 30000.
That worked, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hey! I think I'm having the same issue but I'm using docker-compose. Is this not the correct usage? I've starred out sensitive fields but this configuration works with my primary server but not when I try to create a new one on a different port. version: "3.8"
services:
foundry:
image: felddy/foundryvtt:release
hostname: ****
init: true
volumes:
- type: bind
source: ****
target: /data
environment:
- FOUNDRY_PROXY_PORT=true
- FOUNDRY_PASSWORD=****
- FOUNDRY_USERNAME=****
- FOUNDRY_ADMIN_KEY=****
- FOUNDRY_LICENSE_KEY=****
ports:
- target: 30001
published: 30001
protocol: tcp |
Beta Was this translation helpful? Give feedback.
-
|
The So your ports:
- target: 30000
published: 30001
protocol: tcpSee: Also, |
Beta Was this translation helpful? Give feedback.
-
|
I am running into a similar issue. I've got the containers running side by side just fine, but I'm having trouble reaching them externally through my reverse proxy set up. I use traefik: Everything matches my working config except for the relevant ports and names, and I've triple checked DNS in both my local and domain provider settings. trying to navigate to the url gives a bad gateway, navigating to the ip at port 30001 works fine. also looks good in traefik dashboard: |
Beta Was this translation helpful? Give feedback.
-
|
I fixed this by just using the same load balancer as my normal instance,
and then it works |
Beta Was this translation helpful? Give feedback.
-
|
I spoke too soon. I can get the page, but after entering the admin password it doesn't go further |
Beta Was this translation helpful? Give feedback.
-
|
No matter what I do I see the portainer docker container's console say it's listening on port 30000. This is a second foundry server container on the same box so it seems like if both server instances are listening on port 30000 on the same box it's going to be a problem, right? Or is there some configuration I can do? I've tried everything in this thread. Is there a combo of configurations that I need to do at the same time or something? |
Beta Was this translation helpful? Give feedback.
Good question...
The server in the container will always listen on port
30000. This port is exposed by the container:foundryvtt-docker/Dockerfile
Line 78 in d7bbea8
You need only publish the port to your desired target. In your case
40000. There is no need to modify the entry point, or the arguments. I'm not familiar with the Synology GUI but I expect the configuration you are searching for is in the "Netzwerk" tab.This is how it would be accomplished using the CLI: