You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabling SSL communication within FoundryVTT (by populating the Certificate and Key fields in configuration), the docker container will falsely report that it is unhealthy even though the URL for the server is operating normally and properly utilizing the certificate file(s).
FoundryVTT | 2024-02-05 21:54:33 | [info] Software license verification succeededFoundryVTT | 2024-02-05 21:54:33 | [info] Server started and listening on port 30000
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Bug description
See #96 which details the same problem.
When enabling SSL communication within FoundryVTT (by populating the Certificate and Key fields in configuration), the docker container will falsely report that it is unhealthy even though the URL for the server is operating normally and properly utilizing the certificate file(s).
Per docker inspect command:
{ "Id": "5c374170d7afed5811cc3251f27b12de173beee2c7899a102e2e47fe9f90c426", "Created": "2024-02-04T03:17:16.701460867Z", "Path": "./entrypoint.sh", "Args": [ "resources/app/main.mjs", "--port=30000", "--headless", "--noupdate", "--dataPath=/data" ], "State": { "Status": "running", "Running": true, "Paused": false, "Restarting": false, "OOMKilled": false, "Dead": false, "Pid": 4395, "ExitCode": 0, "Error": "", "StartedAt": "2024-02-04T19:55:57.66182608Z", "FinishedAt": "2024-02-04T19:49:05.964040495Z", "Health": { **"Status": "unhealthy",** "FailingStreak": 16, "Log": [ { "Start": "2024-02-04T15:04:28.485001389-05:00", "End": "2024-02-04T15:04:28.52147859-05:00", "ExitCode": 1, "Output": "" }, { "Start": "2024-02-04T15:04:58.531513334-05:00", "End": "2024-02-04T15:04:58.581211192-05:00", "ExitCode": 1, "Output": "" }, { "Start": "2024-02-04T15:05:28.590011407-05:00", "End": "2024-02-04T15:05:28.634376391-05:00", "ExitCode": 1, "Output": "" }, { "Start": "2024-02-04T15:05:58.642992165-05:00", "End": "2024-02-04T15:05:58.678409309-05:00", "ExitCode": 1, "Output": "" }, { "Start": "2024-02-04T15:06:28.689170661-05:00", "End": "2024-02-04T15:06:28.725521568-05:00", "ExitCode": 1, "Output": "" } ] }
Removing the Certificate and Key, which reverts the internal web server to non-SSL mode, resolves the issue.
Steps to reproduce
Expected behavior
The container should report as 'healthy' once it has completed startup.
Container metadata
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: