-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: penpot: "server not available" #4957
Comments
@OliverSpeir @peaklabs-dev is it working for you? |
I haven't tried the new dependson config I just manually applied the new health checks when I was testing my PR I'll try tonight and let you know |
Yes, it works for me. Another user also had exactly 1 service that did not work. Not really sure what is going on. |
I am seeing the same failure, brand new install of coolify and penpot.
There are no errors in the backend logs as far as I can see, just the java service starting up.
My penpot frontend never responds and there are no logs unless I comment out the health check, then I get:
I did see an issue in the penpot repo penpot/penpot#5430 that spoke of changes to the ports for the frontend in the images in the 2.4.0 and 2.4.1, not sure if those have been accounted for in the coolify current compose file. |
I had the same issue with the frontend container being unhealthy, I was able to fix it by updating the health check in the compose file to use port 8080 instead of 80 |
…s per Penpot 2.4.* changes
Looks like there's some action on this https://github.com/penpot/penpot/releases/tag/2.5.0-RC1 |
I've removed all healthchecks for frontend but I cantt start penpot frontend because shows me this
Someone can help me? please |
I suggested that the Penpot community officially support Coolify here. |
@SebasGDEV The main issue is that the Coolify compose file expects Penpot on port 80, you need to make it proxy to port 8080 instead as the newer versions of Penpot have changed, I have it working smoothly. This is from memory but I think the main changes were to change the frontend health check to port 8080 and to add the environment variable SERVICE_FQDN_FRONTEND_8080, which I set to $SERVICE_FQDN_FRONTEND:8080. |
Hmm this is a good catch but even if I set this I am still not able to get a fresh install to work. I am using Cloudflare Tunnel with my hostname btw. |
Hi guys, can you please try the following docker-compose to see if it works
|
In url add ':8080', worked for me. I also have changed port in healthcheck for 8080. |
@SebasGDEV did you have to change the ports yourself? |
@stewnight yes, I have changed ports by myself, when I changed port from compose didn't happen |
@stewnight I can confirm the steps here also do the trick for me. Adding a port number after URL also aligns with my other Coolify-hosted services tho, so this is no surprise to me. |
Error Message and Logs
I had penpot working for a while. Recently Coolify said "latest configuration was not applied", so I restarted it. Now it just gives me "server not available" when accessing.
Tried syncing the compose file with the latest version, no luck.
Completely deleted penpot and set it up again, same result.
All containers show as healthy except front end. All containers seem to have good logs, front end shows no logs. Something about the health checks and "depends" settings seems to not be working.
Coolify Version
v4.0.0-beta.389
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24
The text was updated successfully, but these errors were encountered: