coollabsio
[Bug]: Authentik preset `no available server` when using HTTPS
Error Message and Logs
No errors from Coolify, Authentik server container works fine for HTTP addresses.
Steps to Reproduce
- Add a new resource
- Add a premade authentik service
- Hit deploy
- Access using the default auto-gen domain - WORKS
- Set your own domain that has https:// (cloudflare, self cert, doesnt matter, as long as its https on the url for domain on coolify)
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)
No response
Additional Information
No response
Okay, I started running into this today. SSL's are also no longer getting issued as well and on one of my servers, Docker networking foobar'ed itself, but don't think that is related.
All deployments requiring SSL's is now broken with "no available servers".
Sorry about that. We Introduced a bug in one of the last releases that broke some things with labels. A fix for this has been implemented and will be available in the next release. Thanks for your patience.
There is a temporary fix (will have to be reverted after the next release): https://discord.com/channels/459365938081431553/1331647210902786231/1331971443247943763
IMPORTANT: If you follow this fix, once v4.0.0-beta.389 is live, you will need to re-check readonly-label labels (rest labels if possible - should not be necessary though). Why?:
- readonly-labels checked (true): means the editor is in read-only mode and Coolify will automatically generate all labels.
- readonly-labels unchecked (false): means the editor is in editable mode and Coolify will not touch your labels.
I've just tested this fix and yes, I can confirm I have deployments again on the server I still have that still function.
Thank you very much for the quick turnaround on this.
Confirmed working here on my end as well with the fix on Discord on another application I was having an issue with, thanks! However, I don't see any labels and such for a Service Stack however? What would be the best way (other than waiting for the release) to fix this there?
The fixed version is already live, so you should be fine to just update Coolify.
HELP! I suddenly ran into this again in v4.0.0-beta.390.
I initially deployed a WordPress website working just fine with the SSL issued, but then a restart suddenly shows "no server available".
HELP! I suddenly ran into this again in v4.0.0-beta.390.
I initially deployed a WordPress website working just fine with the SSL issued, but then a restart suddenly shows "no server available".
also experiencing this issue in v4.0.0-beta.390
Okay, so for whatever reason, it's working again. I fully shut down the service and redeployed it. No idea what's going on yet.
seeing this in the 4.0.0-beta.394 today with several out of the box resources, like browserless and convertx
seeing this in the 4.0.0-beta.394 today with several out of the box resources, like browserless and convertx
Double check that the app isn't constantly restarting. That was an issue I did come across after the fixes provided in previous versions. Let us know,.
I have this issue on v4.0.0-beta.395 for a specific domain. If i use my main domain, it fails, if i generate a domain - it works.
Using v4.0.0-beta.397, I initially got the same error when changed the domain to my custom one. After I restarted my services, the problem is gone.
I have been receiving this issue for the last few days on v4.0.0-beta.397 as well unfortunately. However restarting or redeploying my services does not reliably help.
Please note that the issues you are experiencing are different from the specific one I had with Authentik. Please create a new issue with your conditions or ask for help on Discord.
My service was working fine, re-deployed and started to give me this error "no available server" I have another identical (same github repo just different dns and env) service that is working after my last changes. I tried everything, restarted everything, even changed the DNS and it seems coolify can't issue a new certificate.
Yeah, after 2 days digging it was my fault. If anyone had this problem may be useful: check if your healthcheck is enabled, if yes check if the path is correctly configured :P
same on latest version if I use custom dns + ssl and I enter with https://mydomain.com
