• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

docker image 4.5.3 won't start

Version
4.5.3
PHP version
8.2.31
Database driver
MariaDB
Database version
11.3.2
Web browser
Firefox

bjoern.busch

Chevereto Member
Hi there,

I'm running the dockerized version of chevereto on a synology NAS. Currently I have 4.4.1 running like a charm, no issues at all, super happy. I build the docker image myself in gitlab from https://github.com/chevereto/docker.git from the 4.5. branch with make image in a gitlab pipeline. I had tried 4.5.2 but the image would not start. I didn't have time to report it and now tried 4.5.3 and I see the same issue that the container image won't start:

AH00015: Unable to open logs
no listening sockets available, shutting down
(13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:443
(13)Permission denied: AH00072: make_sock: could not bind to address [::]:443
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using fd00::5. Set the 'ServerName' directive globally to suppress this message

Has anybody seen this as well? Did something change? I haven't consulated Copilot yet.
 
ok, so Claude said that it is due to the port change and the dockerfile would need an additional sed line:

&& sed -i 's/Listen 80/Listen 8080/' /etc/apache2/ports.conf \
++&& sed -i '/Listen 443/d' /etc/apache2/ports.conf \
&& sed -i 's/<VirtualHost \*:80>/<VirtualHost *:8080>/' /etc/apache2/sites-available/000-default.conf \

when manually patching that, the container starts nicely again.
 
Yes, I saw that the port changed from 80 to 8080, but somehow compared to 4.4.1 the Listen 443 seams to be causing issues in my environment. When I remove the 443 lines, it's working fine.
 
Back
Top