Skip to content

Running the platform

Troubleshooting

No emails arrive

  1. Is the worker running? Without it emails wait in the queue. GET /api/v1/health reports a queue that has waited 15 minutes or more.
  2. SEND_EMAIL=1 and a real MAILER_DSN (not null://null).
  3. The provider's logs: a sender address not verified with the provider is the most common reason.

Photos do not show

  • Local storage: public/uploads must be writable and served by the web server.
  • S3: check bucket, region, keys and the endpoint in Settings, Storage; the bucket (or a CDN in front of it) must allow public reads; set the CDN address as the public URL.
  • Photos uploaded before an update that added a size: run php bin/console app:images:variants (bin/update does it automatically).

Health check answers 503

data.checks in the answer says which part failed: database (connection or credentials), queue (the worker is stopped or stuck; restart it), storage (storage settings incomplete).

Uploads fail with "too large"

Raise upload_max_filesize (at least 12M) and post_max_size (at least 64M) in PHP, and the web server's body size limit (nginx client_max_body_size).

"Continue with Facebook" fails

The Facebook app must be live, have the email permission, and list https://your-domain/login/check-facebook as a valid OAuth redirect. People who refuse to share their email cannot sign up through Facebook; the login page says so.

Phone verification is missing

It appears only when an SMS provider is chosen in Settings, SMS with its keys filled in.

Changes in the admin do not show

A saved setting shows on the next page; the worker (emails, push) picks it up within five minutes. After changing a theme or the assets, rebuild them (npm run build or a new Docker image) and clear the cache (php bin/console cache:clear).

An update stopped half way

app:update runs each database change in order and stops at the first problem with a message. Fix the cause it names and run bin/update again; finished steps are not repeated. If the site has to go back, restore the backup taken by bin/update and deploy the previous version.

Found a mistake? Tell us.