Invalid default port mappings about plausible_on_dokku HOT 5 CLOSED

Mmmh, I had done some tests and Dokku managed to get the right port automatically with the EXPOSE instruction in the Dockerfile.

• With which version of Dokku this happened?
• Did the application already have the proxy configured by a previous deployment? (or fresh app)

from plausible_on_dokku.

I did an app:destroy before, so I believe I started from scratch completely, unless dokku keeps some mapping (but even then, I never used port 5000, and it does seem to be the default)

running dokku version 0.24.2

from plausible_on_dokku.

So, I re-tested with the latest version of Dokku (0.24.7) with a new fresh app and it seems to succeed in retrieving the port coming from the EXPOSE statement of the Dockerfile (see screen below), I will try to re-test with version 0.24.2 of Dokku and for Letsencrypt (443 mapping) when I have time.

from plausible_on_dokku.

I must have messed up somewhere then, or have default config from other apps.

Thanks for investigating, I'll close, seems to be related to me

from plausible_on_dokku.

I know it's been a while but I found the cause that prevents Dokku from auto-detecting the correct port...
While doing another project (uptime_kuma_on_dokku) I noticed that configuring the domain before the first deployment defaults to port 5000 and prevents auto-detection of the port from the Dockerfile.
So for now in the installation guide I have moved the domain configuration to the end, I will do more testing and maybe change the port in the container to port 5000 instead of 80.

from plausible_on_dokku.