-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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]: no available server
when using HTTPS
#4812
Comments
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". |
no available server
when using HTTPS
Sorry about that. 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).
|
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. |
Ah yeah! Cheers, all perfect now 👌 |
Error Message and Logs
No errors from Coolify, Authentik server container works fine for HTTP addresses.
Steps to Reproduce
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
The text was updated successfully, but these errors were encountered: