Replies: 1 comment
|
Per the suggestion from comment from Sharyar Naseem (maybe it's awaiting moderation? can't see it here) I have just tried setting the hostname in Network and FOUNDRY_LOCAL_HOSTNAME to match the original container, I removed the license.json file, and recreated the container. Though the inspection page for the container (Portainer) does reflect the changes, the same issue persists. When loading the app page, I'm directed to agree to the EULA, then input the license key, and then I get the error that license signature failed. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Due to some performance issues, DM and I decided to try moving the FVTT container to a new server to live all on its own and be unbothered by other services.
Migration of all the container data seemed to go well, but when I start the container, I keep getting an error "License signature Failed for license [redacted]". When I load the app in a browser, I get directed to the License Agreement page. I click the things to consent, and get directed to the page to input my license key. When the page loads and when I input the key, I get the same error in the UI.
So far, I've tried removing the license.json, and incrementing the version number in it all the way up to 14.365 (current version in use.) These efforts have garnered no traction.
In case it helps, these are the logs for the container:
Any help is greatly appreciated, and I'm happy to provide more info about the new server setup if it will be helpful.
All reactions