[Bug]: Instance Domain no longer accessible after .380 update

[adamboof]

Error Message and Logs

Just upgraded to the latest update and the instance took longer than normal to boot back up. Upon further investigation I found the Coolify instance was still accessible via the IP:Port but not through the instance domain (that worked fine before the update).

Steps to Reproduce

1. Be on v4-beta.379 with a correctly set up instance domain
2. Upgrade to .380
3. Instance no longer accessible through the domain

Example Repository URL

No response

Coolify Version

v4.0.0-beta.380

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 22.04

Additional Information

No response

[shantanugoel]

I seem to be unable to access it via IP:Port as well. The container seems to be running but shows up as "unhealthy". There are no errors in the docker logs for the container, but I receive a connection reset by peer message when I try to do curl ip:8000

ghcr.io/coollabsio/coolify:latest           "docker-php-serversi…"   30 hours ago   Up 7 minutes (unhealthy)   8000/tcp, 8080/tcp, 8443/tcp, 9000/tcp, 0.0.0.0:8000->80/tcp, [::]:8000->80/tcp   

[shantanugoel]

Looking at this change, I think the issue is that 8000 should now map to 8080 instead of 80.

https://github.com/coollabsio/coolify/pull/4608/files

[shantanugoel]

Ok, confirmed that this was the problem and my issue is fixed by manually updating the port configuration

[ikramhasan]

I'm facing the same issue. Can you tell how you updated the port configuration? @shantanugoel

[shantanugoel]

@ikramhasan I updated it in /data/coolify/source/docker-compose.prod.yml. Just in case updating it directly doesn't work, run ./upgrade.sh (present in the same directory). That should bring in the new compose file as well as make it take effect.

[ikramhasan]

Thanks man. For now I just downgraded my instance but will try your solution later today.

[peaklabs-dev]

The Coolify container may be unhealthy due to the following bug #4601. We have changed the port to 8080 to fix the bug mentioned in the linked issues. You should not need to change anything, it should just work out of the box. If you have anything running on port 8080 this will conflict ofc.

If your instance is not reachable through your domain name, check if the Coolify proxy is still running with docker ps.

I will close this issue for now, if you have any additional information please let me know.