I've been running Foundry for a few years now, but after upgrading to 12.325 today, I'm getting an error about verifying my license key. I'm using the username/password method, which has worked flawlessly until now. I even manually entered the license key into the variable, and still it doesn't work.

 

Any ideas?

Were you able to get this figured out? I just tried upgrading to 12.325 and I'm having the exact same issue. The page to accept the license agreement is blank.

I've been fighting to get the other release's container up and running for weeks.

I just got yours up and running with just the license and the download link from my accounts page, easy peasy, thanks!

 

One thing though, I'd like to share my Nvidia card that I'm sharing with my Plex docker to this one too for better performance. How would I go about doing that? Do I add the 2 variables I've got in my Plex docker? Like:

 

Adding --runtime=nvidia to "Extra Parameters:" at the top of the advanced view

 

Adding variables:

NVIDIA_DRIVER_CAPABILITIES: All

NVIDIA_VISIBLE_DEVICES: Nvidia device ID

 

Edited July 14, 20241 yr by Squirreljester

On 5/23/2024 at 10:26 PM, raven.warsong said:

hello how do I fix this error I cant save any thing every time I reboot the docker I have to set my admin password and nothing will save only my key is saved thanks so much. 

  

I struggled with this until I was editing the settings of the container I clicked the "show more settings" at the bottom. The preserve config variable is in the expanded settings list.

Having this issue where some images show up on actors etc but images in the journal don't show up, server gives 404 error. Checked the server directory and the files are present. 

For some reason, files would not show up for me in the Appdata folder. I tried several hours of troubleshooting and the only way I was able to fix this was by un-installing and re-installing the app. FYI

On 7/10/2024 at 4:32 AM, prophecy0 said:

Were you able to get this figured out? I just tried upgrading to 12.325 and I'm having the exact same issue. The page to accept the license agreement is blank.

I'm having the same issue on 12.331. Has anyone found a way to resolve this?

Hey, I don't think FOUNDRY_VERSION should be part of the template, according to the author of the docker, we shouldn't be setting FOUNDRY_VERSION as it is set by the container. Specifying the foundry version you want should be set by the docker tag, not the environment variable so you get a node version to match the foundry version that have been tested together. I removed the argument from my template and I thought I'd post it here since I saw others getting errors related to this.

Hello,

 

I'm having some issues, I was wondering if anyone has been through something similar with this image?

1. When I start the container and visit the webURL, I just get stuck on the /license page and I don't have any input or way to get past this page. EDIT: resolved by enabling websockets support on NPM.

2. I get the following error/crash every time I restart the container. It seems to have something to do with the json lock file? Anyone else experience this? It seems like the image is not removing the lock file? EDIT: Solved this by setting the --restart unless-stopped

 

```FoundryVTT | 2025-01-27 14:05:34 | [error] A fatal error occurred while trying to start the Foundry Virtual Tabletop server: Foundry VTT cannot start in this directory which is already locked by another process.
Error: A fatal error occurred while trying to start the Foundry Virtual Tabletop server: Foundry VTT cannot start in this directory which is already locked by another process.
    at _acquireLockFile (file:///home/foundry/resources/app/dist/init.mjs:1:5233)
    at async _initializeCriticalFunctions (file:///home/foundry/resources/app/dist/init.mjs:1:2861)
    at async Module.initialize (file:///home/foundry/resources/app/dist/init.mjs:1:1788)
```

Edited January 27, 20251 yr by adman234

Can someone tell me how to change the user and group of the process in v13, since the uid and gid has been deprecated? This post mentions it, but I‘m not sure how to add it to the template.

Watchtower automatically updated to the v13 container, from what I can see it's wrong node version so we need to install the old v12 container but I can't work out what the repository value should be.

Normal is:

felddy/foundryvtt:release

I've tried:

felddy/foundryvtt:v12

felddy/foundryvtt:v12.331.0

But no luck. Can anyone advise what repository value I should use to get back the version that works? 😧

 

Found the issue - I thought it needed the gitbhub tags so I had the 'v' in there. Remove the v and it works fine.

 

So overkongen just change your repository to the following and it should work again:

felddy/foundryvtt:12.331.0

(or whatever version you were using)

Edited May 1, 20251 yr by TheTeal

For the image to use, try felddy/foundryvtt:release-12.331.0

On 5/1/2025 at 5:18 AM, TheTeal said:

So overkongen just change your repository to the following and it should work again:

felddy/foundryvtt:12.331.0

Thanks. But the thing I'm trying to do is getting v13 up and running.

 

I kinda fixed it by using this repository: felddy/foundryvtt:13.341 and changing the ownership of the data path as described in this discussion.

I would however much rather change the owner in the container but I'm not sure how you add "user: xxx:xxx" to your container as described in the previous link.

Edited May 4, 20251 yr by overkongen
more info

On 5/4/2025 at 7:20 AM, overkongen said:

Thanks. But the thing I'm trying to do is getting v13 up and running.

 

I kinda fixed it by using this repository: felddy/foundryvtt:13.341 and changing the ownership of the data path as described in this discussion.

I would however much rather change the owner in the container but I'm not sure how you add "user: xxx:xxx" to your container as described in the previous link.

If you are still struggling with this the solution is to use the Extra Parameters field under Advanced View:

--user 99:100

This will ensure the container is created with expected Unraid permissions.

Hope this helps!

total newb here. Trying to get this up and running to use the CosmereRPG when it comes out. I already added an A name DNS registry, got Nginx setup for port 30000, and created a share to put the game in called VTT and a folder in the share called Data. However, when I run the docker, it immediatly stops. nothing downloads, nothing. here is the log:

Entrypoint | 2025-06-24 16:01:39 | [debug] Data directory: /data

Entrypoint | 2025-06-24 16:01:39 | [debug] Mount info for /data: shfs[/VTT/Data] fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other

Entrypoint | 2025-06-24 16:01:39 | [debug] Testing permissions on /data/.container-permissions-test.txt

Entrypoint | 2025-06-24 16:01:39 | [error] Volume write test failed.

Entrypoint | 2025-06-24 16:01:39 | [error] Volume read test failed.

Entrypoint | 2025-06-24 16:01:39 | [debug] Volume delete test succeeded.

Entrypoint | 2025-06-24 16:01:39 | [error] Aborting due to insufficient permissions on /data

Entrypoint | 2025-06-24 16:01:39 | [error] Container running as uid:gid: 1000:1000

Entrypoint | 2025-06-24 16:01:39 | [error] For more information see the discussion at: https://github.com/felddy/foundryvtt-docker/discussions/1197

VTT is set to export and is public. What is going on? can the data not be stored on a share?

On 6/24/2025 at 6:12 PM, elihaun said:

total newb here. Trying to get this up and running to use the CosmereRPG when it comes out. I already added an A name DNS registry, got Nginx setup for port 30000, and created a share to put the game in called VTT and a folder in the share called Data. However, when I run the docker, it immediatly stops. nothing downloads, nothing. here is the log:

Entrypoint | 2025-06-24 16:01:39 | [debug] Data directory: /data

Entrypoint | 2025-06-24 16:01:39 | [debug] Mount info for /data: shfs[/VTT/Data] fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other

Entrypoint | 2025-06-24 16:01:39 | [debug] Testing permissions on /data/.container-permissions-test.txt

Entrypoint | 2025-06-24 16:01:39 | [error] Volume write test failed.

Entrypoint | 2025-06-24 16:01:39 | [error] Volume read test failed.

Entrypoint | 2025-06-24 16:01:39 | [debug] Volume delete test succeeded.

Entrypoint | 2025-06-24 16:01:39 | [error] Aborting due to insufficient permissions on /data

Entrypoint | 2025-06-24 16:01:39 | [error] Container running as uid:gid: 1000:1000

Entrypoint | 2025-06-24 16:01:39 | [error] For more information see the discussion at: https://github.com/felddy/foundryvtt-docker/discussions/1197

VTT is set to export and is public. What is going on? can the data not be stored on a share?

That link at the end of the logs tells you what to do. You need to fix the share permissions.

Edited June 26, 20251 yr by voyager12
share typo

On 6/25/2025 at 9:52 PM, voyager12 said:

That link at the end of the logs tells you what to do. You need to fix the share permissions.

Thanks. i think my mind just glazed over the link. I got it working on the unraid local-webUI, but am still working to actually get it to work with my domain

New 'issue': every time I start the WEBui it askes me to agree to the EULA.

Ok, I think I figured out the issue I was having with my domain. you have to stop the array, go to setting>dockers> and change 'Host access to custom networks' to enabled. after that, start back the array and it worked. Hopefully this can help someone else!

On 6/29/2025 at 12:50 AM, elihaun said:

New 'issue': every time I start the WEBui it askes me to agree to the EULA.

From a quick Google search: https://github.com/felddy/foundryvtt-docker/discussions/159

I just started getting this error out of the blue:

FoundryVTT | 2025-07-15 15:40:50 | [error] A fatal error occurred while trying to start the Foundry Virtual Tabletop server: EACCES: permission denied, open '/data/Data/systems/README.txt'

Error: A fatal error occurred while trying to start the Foundry Virtual Tabletop server: EACCES: permission denied, open '/data/Data/systems/README.txt'

On 7/15/2025 at 10:42 AM, Squirreljester said:

I just started getting this error out of the blue:

FoundryVTT | 2025-07-15 15:40:50 | [error] A fatal error occurred while trying to start the Foundry Virtual Tabletop server: EACCES: permission denied, open '/data/Data/systems/README.txt'

Error: A fatal error occurred while trying to start the Foundry Virtual Tabletop server: EACCES: permission denied, open '/data/Data/systems/README.txt'

Did you update from v12 to v13? If so, it's because the permission handling is different now. See https://github.com/felddy/foundryvtt-docker/releases/tag/v13.341.0. let me know if that doesn't help.

12 hours ago, voyager12 said:

Did you update from v12 to v13? If so, it's because the permission handling is different now. See https://github.com/felddy/foundryvtt-docker/releases/tag/v13.341.0. let me know if that doesn't help.

I've done all the updates that have come up when it says there's one available. How do I check if it's v12 or v13 when it won't stay running anymore?

36 minutes ago, Squirreljester said:

I've done all the updates that have come up when it says there's one available. How do I check if it's v12 or v13 when it won't stay running anymore?

What docker tag are you using in your template? If it's latest or release, then it will auto upgrade major versions.

41 minutes ago, voyager12 said:

What docker tag are you using in your template? If it's latest or release, then it will auto upgrade major versions.

I apologize, where do I find that?