Internal Server Error with v1.15.0-20200620-143251-752

[sylvaindd]

Hi,

I'm having an internal server error when I try to access the website after upgrading to v1.15.0-20200620-143251-752.

Rolling back to v1.15.0-20200618-123207-243 solves the problem.

There is no error in the default output (DEBUG is enabled), and I couldn't find any in the container logs (maybe I didn't find the right log file) :

Compressing... done
Compressed 20 block(s) from 102 template(s) for 0 context(s).
You have requested to collect static files at the destination
location as specified in your settings:
/healthchecks/static-collected
This will overwrite existing files!
Are you sure you want to do this?
Type 'yes' to continue, or 'no' to cancel:
309 static files copied to '/healthchecks/static-collected'.
Correcting config file permissions ...
Migrating database ...
Operations to perform:
Apply all migrations: accounts, admin, api, auth, contenttypes, payments, sessions
Running migrations:
No migrations to apply.
2020-06-20 22:26:20,642 INFO supervisord started with pid 1
2020-06-20 22:26:21,647 INFO spawned: 'nginx' with pid 16
2020-06-20 22:26:21,651 INFO spawned: 'smtpd' with pid 17
2020-06-20 22:26:21,656 INFO spawned: 'gunicorn' with pid 18
2020-06-20 22:26:21,667 INFO spawned: 'sendalerts' with pid 19
2020-06-20 22:26:23,506 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-06-20 22:26:23,506 INFO success: smtpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-06-20 22:26:23,506 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-06-20 22:26:23,507 INFO success: sendalerts entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

[galexrt]

@sylvaindd Check inside the container in the /var/log/ directory (see https://github.com/galexrt/docker-healthchecks/blob/master/includes/supervisor/supervisord.conf#L12 and the other stdout_logfile and stderr_logfile file paths).

[sylvaindd]

Well it seems the problem is between my reverse proxy (traefik) and the app.
I guess it's because you added another port in the EXPOSE clause.

I added the container target port in traefik conf and it's working again.

Thank you