Describe the issue
After updating the Chevereto Docker container on Unraid, the WebUI is no longer reachable.
The container starts correctly and Apache appears to be running, but the web interface cannot be accessed from the browser ("Unable to reach the page").
Logs
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2
[mpm_prefork:notice] Apache/2.4.66 (Debian) OpenSSL/3.5.5 configured -- resuming normal operations
[core:notice] Command line: 'apache2 -D FOREGROUND'
[mpm_prefork:notice] caught SIGWINCH, shutting down gracefully
Environment
Platform: Unraid
Deployment: Docker container
Reverse proxy: (yes/no — specify if you use one)
Database: (MySQL/MariaDB — specify)
What I already tried
Verified container is running
Checked logs (no critical errors shown)
Adjusted file permissions in /appdata after update
Restarted container multiple times
Additional details
Before the update, everything was working correctly
After the update, the container starts but the WebUI is unreachable
No clear PHP or Apache fatal errors are shown in logs
Question
Could this be related to:
a change in internal container port?
a change in expected file permissions or user (UID/GID)?
or a known issue with the latest Docker image?
Any guidance on how to debug this further would be appreciated.
Describe the issue
After updating the Chevereto Docker container on Unraid, the WebUI is no longer reachable.
The container starts correctly and Apache appears to be running, but the web interface cannot be accessed from the browser ("Unable to reach the page").
Logs
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2
[mpm_prefork:notice] Apache/2.4.66 (Debian) OpenSSL/3.5.5 configured -- resuming normal operations
[core:notice] Command line: 'apache2 -D FOREGROUND'
[mpm_prefork:notice] caught SIGWINCH, shutting down gracefully
Environment
Platform: Unraid
Deployment: Docker container
Reverse proxy: (yes/no — specify if you use one)
Database: (MySQL/MariaDB — specify)
What I already tried
Verified container is running
Checked logs (no critical errors shown)
Adjusted file permissions in /appdata after update
Restarted container multiple times
Additional details
Before the update, everything was working correctly
After the update, the container starts but the WebUI is unreachable
No clear PHP or Apache fatal errors are shown in logs
Question
Could this be related to:
a change in internal container port?
a change in expected file permissions or user (UID/GID)?
or a known issue with the latest Docker image?
Any guidance on how to debug this further would be appreciated.