Skip to content
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

Closed
alepouna opened this issue Jan 13, 2025 · 6 comments · Fixed by #4926
Closed

[Bug]: no available server when using HTTPS #4812

alepouna opened this issue Jan 13, 2025 · 6 comments · Fixed by #4926

Comments

@alepouna
Copy link
Contributor

Error Message and Logs

No errors from Coolify, Authentik server container works fine for HTTP addresses.

Steps to Reproduce

  1. Add a new resource
  2. Add a premade authentik service
  3. Hit deploy
  4. Access using the default auto-gen domain - WORKS
  5. 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

@alepouna alepouna added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 13, 2025
@maietta
Copy link

maietta commented Jan 23, 2025

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".

@peaklabs-dev peaklabs-dev changed the title [Bug]: Authentik template results in a 'no available server' when using HTTPS [Bug]: no available server when using HTTPS Jan 23, 2025
@peaklabs-dev peaklabs-dev removed the 🔍 Triage Issues that need assessment and prioritization. label Jan 23, 2025
@peaklabs-dev
Copy link
Member

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.

@peaklabs-dev peaklabs-dev self-assigned this Jan 23, 2025
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Jan 23, 2025
@peaklabs-dev peaklabs-dev added the ✅ Done Issues that are fixed and a PR is ready to be merged. label Jan 23, 2025
@github-actions github-actions bot removed 🐛 Bug Reported issues that need to be reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged. labels Jan 23, 2025
@maietta
Copy link

maietta commented Jan 23, 2025

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.

@alepouna
Copy link
Contributor Author

alepouna commented Jan 24, 2025

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?

@peaklabs-dev
Copy link
Member

The fixed version is already live, so you should be fine to just update Coolify.

@alepouna
Copy link
Contributor Author

Ah yeah! Cheers, all perfect now 👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants