Stuck at 🔥 Starting Apache...

[C-Fu]

Good day,

After so long (I think last I was using v1.x) I updated to the latest version on my container, but everything is stuck at the Starting Apache... line.

WARN[0000] /root/filerise/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
filerise  | 🚀 Running start.sh...
filerise  | [startup] Normalizing ownership on uploads/metadata...
filerise  | [startup] VIRUS_SCAN_ENABLED=true
filerise  | [startup] Using virus scanner command: clamscan
filerise  | 🔄 Updating config.php from env vars...
filerise  | 🔄 Setting PHP upload limits to 10G
filerise  | [startup] Updating ClamAV signatures via freshclam...
filerise  | 🔄 Setting Apache LimitRequestBody to 10737418240 bytes
filerise  | [startup] Scanning uploads directory to build metadata...
filerise  | Done. Created 0 entries, pruned 0.
filerise  | 🔥 Starting Apache...

I've tried the latest (3 hours ago), v3.0.0, v2.12 all displays the same problem.

my compose:

version: "3.9"


services:
  filerise:
    image: error311/filerise-docker:v2.12.0
    container_name: filerise
    ports:
      - "8888:80"
    environment:
      TIMEZONE: "Asia/Kuala_Lumpur"
      TOTAL_UPLOAD_SIZE: "10G"
      SECURE: "false"
      PERSISTENT_TOKENS_KEY: "xxxxxxxxxxxxxx"
      SERVER_NAME: "xxx.xxx.com.my"
      SHARE_URL: "https://xxx.xxx.com.my"
      SCAN_ON_START: "true"   # auto-index existing files on startup
      CHOWN_ON_START: "true"  # fix permissions on uploads/users/metadata on startup
      VIRUS_SCAN_ENABLED: "true"
      CLAMAV_AUTO_UPDATE: "true"
      PUID: "99"
      PGID: "100"
      LOG_STREAM: "both"
#      FR_TRUSTED_PROXIES: "192.168.0.1/23"
    volumes:
      - ./uploads:/var/www/uploads:z
      - ./users:/var/www/users:z
      - ./metadata:/var/www/metadata:z

with or without :z, PUID:PGID to 99/100 (as per the www-data id in the container) or 0:0, it's all the same.

Thanks in advance!

[error311]

That “Starting Apache…” line is the handoff to Apache running in the foreground, so it’s expected to be the last startup line. If the container is still running, FileRise should be up. I will add in next release as last line before LOG_STREAM [startup] FileRise startup complete. Any further output will be Apache logs (errors by default).. This should help be more clear FileRise is running. I think that will close this out but please continue to provide details so we can solve your issue.

With LOG_STREAM=both, you’ll only see logs once a request hits it or if Apache errors. Try opening http://:8888/ — you should see an access log entry when it’s hit.

If it’s still unreachable, can you share:

• docker ps output (to confirm the container is running)
• docker logs --tail=200 filerise
• result of curl -I http://localhost:8888 from the host

[C-Fu]

This is what I got with http://IP:8888

This is what I got with https://filerise.mydomain.com.my

If I hard refresh Ctrl+Shift+R,

My Nginx Proxy Manager custom config:

Thanks in advance!!

[error311]

Hi @C-Fu, thanks for the screenshots.

If you’re proxying HTTPS > FileRise, set:

• SECURE="true"

From your screenshots, the issue is your reverse proxy / SSL, not FileRise startup:

1) TLS cert is invalid
Your browser shows NET::ERR_CERT_DATE_INVALID. Renew/fix the cert in Nginx Proxy Manager (and confirm server time is correct).

2) NPM is timing out app assets (504)
DevTools shows 504s for normal assets (/js/basePath.js, /js/version.js, vendor CSS/fonts).
This means NPM can’t reach the upstream.

In NPM > Proxy Host > Details, make sure the Forward Host/Port points to the real FileRise upstream:

• If NPM is on the same Docker network: Forward Host = filerise (container name), Port = 80
• If NPM is on a different host: Forward Host = <LAN IP>, Port = 8888
  Don’t use localhost (inside NPM) and don’t point upstream to the public domain (proxy loop).

3) Remove the custom CSP override for now
Temporarily remove/comment:

proxy_hide_header Content-Security-Policy;
add_header Content-Security-Policy "...";

Quick test
From the NPM host: curl -I http://<upstream>:8888/
And from your browser: https://filerise.mydomain.com.my/js/version.js (should be 200, not 504)

If you share a screenshot of the NPM Proxy Host “Details” tab (Forward Host/Port + scheme), I can tell you exactly what to change.

[C-Fu]

I can confirm that the issue is with NPM. Something went wrong that it couldn't renew/reissue the certificate.
Current latest (I think v2.13.6) works! Sorry for the confusion