Darren Sisson
Darren Sisson
this will be either a network issue related to your host location or an issue with the cdn you see from your host location, either way this isn't a bug...
@0-BSCode can you try changing the node version in your dockerfile to 20/22 or 24
@0-BSCode can you add :9000 ```https://portainer.example.com:9000``` to the end of the domain you have given in coolify project page and restart, i think this container exposes multiple ports, so you...
you need to restart your portainer service also for things that can access your server directly, do not post the urls unless they are behind some form of auth its...
@luckydonald a bug was just fixed regarding parsing healthchecks, looking at it, it turns out when fixing this bug, old code was uncommented, which shouldn't be there https://github.com/coollabsio/coolify/blob/6c17d45c400449f9136c5f428caa0554b9652da9/app/Models/Application.php#L1545-L1546
fyi you can also do this by creating this file here ```/data/coolify/source/docker-compose.custom.yml``` with the contents: ```yaml services: coolify: ports: !override - "1234:8080" ``` this is useful if you need to...
@Cinzya 8080 is for traefik dashboard all 3 ports are only required when the proxy is down (6001, 6002, 8000) so having them open all the time is not required...
@SrJooJ if possible can you paste link to the site
@SrJooJ please note, coolify has nothing to do with certificate generation. if you have turned on cloudflare proxy dns, then you can no longer generate certificates using the default method....
it could also have been a clock error