Keeeps loosing SSL to Nexcloud and get "no available server"
Since updating to v.1.14.1 my main service are randomly going down, varies from days to hours.
And can in the NC compose logs se # [22/Jan/2026:13:51:01 +0000] "\x16\x03\x01\x05\xc2\x01" 400 524 "-" "-" #
This indicates bad TLS handshake.
As I see there is no way for me to re issue a cert via the interface.
Setup:
Pangolin running dockerized in VPS1
Installed a "Site" to VPS2 with newt running as a service in the host direct so i can route as localhost:port to the docker services I have running on that host. "and this works mostly"
journalctl -u newt :
newt[97897]: WARN: 2026/01/23 07:28:23 Target 23: health check failed with status code 503 "
I can reboot, restart. enable and disable, nothing change the state. But IF I remove the Nextcloud resources. Then after 5 to 10 min re-add it, it starts working again, sometimes days, other times hours.
Now i re-added while writing this report. ONLY change I did was remove and add the resource.
Environment
OS Type & Version: (e.g., Ubuntu 22.04) Ubuntu 24.04.3 LTS
Pangolin Version:1.14.1
Gerbil Version: 1.3.0
Traefik Version: latest as of 22.Jan v3.6.7
Newt Version: Newt version 1.8.1
Olm Version: (if applicable)
To Reproduce
Don`t know
Expected Behavior
For it to work stable
Originally created by @Hawolex on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2307
### Describe the Bug
Keeeps loosing SSL to Nexcloud and get "no available server"
Since updating to v.1.14.1 my main service are randomly going down, varies from days to hours.
And can in the NC compose logs se # [22/Jan/2026:13:51:01 +0000] "\x16\x03\x01\x05\xc2\x01" 400 524 "-" "-" #
This indicates bad TLS handshake.
As I see there is no way for me to re issue a cert via the interface.
Setup:
Pangolin running dockerized in VPS1
Installed a "Site" to VPS2 with newt running as a service in the host direct so i can route as localhost:port to the docker services I have running on that host. "and this works mostly"
journalctl -u newt :
newt[97897]: WARN: 2026/01/23 07:28:23 Target 23: health check failed with status code 503 "
<img width="1174" height="60" alt="Image" src="https://github.com/user-attachments/assets/cc197f63-da63-41db-8699-796736096d7d" />
<img width="639" height="54" alt="Image" src="https://github.com/user-attachments/assets/3818c8ca-6285-473a-bc2f-381046097fb2" />
<img width="1037" height="503" alt="Image" src="https://github.com/user-attachments/assets/0d620689-d91e-4939-9e86-ea210d0f087c" />
I can reboot, restart. enable and disable, nothing change the state. But IF I remove the Nextcloud resources. Then after 5 to 10 min re-add it, it starts working again, sometimes days, other times hours.
<img width="861" height="153" alt="Image" src="https://github.com/user-attachments/assets/07085565-ba73-4a09-83df-339d83dc1659" />
Now i re-added while writing this report. ONLY change I did was remove and add the resource.
### Environment
- OS Type & Version: (e.g., Ubuntu 22.04) Ubuntu 24.04.3 LTS
- Pangolin Version:1.14.1
- Gerbil Version: 1.3.0
- Traefik Version: latest as of 22.Jan v3.6.7
- Newt Version: Newt version 1.8.1
- Olm Version: (if applicable)
### To Reproduce
Don`t know
### Expected Behavior
For it to work stable
As I can see, you got 2 different protocols on the first image (http/https).
How do you run NC? Does it respond to http://ip:87 or https://ip:87?
It could also be how the health check is configured. If it is wrongly configured, it may say unhealthy and offline all the time.
<!-- gh-comment-id:3800812618 -->
@Zyfax commented on GitHub (Jan 26, 2026):
As I can see, you got 2 different protocols on the first image (http/https).
How do you run NC? Does it respond to http://ip:87 or https://ip:87?
It could also be how the health check is configured. If it is wrongly configured, it may say unhealthy and offline all the time.
@github-actions[bot] commented on GitHub (Feb 10, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3874671967 -->
@github-actions[bot] commented on GitHub (Feb 10, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Feb 25, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
<!-- gh-comment-id:3955620849 -->
@github-actions[bot] commented on GitHub (Feb 25, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Hawolex on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2307
Describe the Bug
Keeeps loosing SSL to Nexcloud and get "no available server"
Since updating to v.1.14.1 my main service are randomly going down, varies from days to hours.
And can in the NC compose logs se # [22/Jan/2026:13:51:01 +0000] "\x16\x03\x01\x05\xc2\x01" 400 524 "-" "-" #
This indicates bad TLS handshake.
As I see there is no way for me to re issue a cert via the interface.
Setup:
Pangolin running dockerized in VPS1
Installed a "Site" to VPS2 with newt running as a service in the host direct so i can route as localhost:port to the docker services I have running on that host. "and this works mostly"
journalctl -u newt :
newt[97897]: WARN: 2026/01/23 07:28:23 Target 23: health check failed with status code 503 "
I can reboot, restart. enable and disable, nothing change the state. But IF I remove the Nextcloud resources. Then after 5 to 10 min re-add it, it starts working again, sometimes days, other times hours.
Now i re-added while writing this report. ONLY change I did was remove and add the resource.
Environment
To Reproduce
Don`t know
Expected Behavior
For it to work stable
@Zyfax commented on GitHub (Jan 26, 2026):
As I can see, you got 2 different protocols on the first image (http/https).
How do you run NC? Does it respond to http://ip:87 or https://ip:87?
It could also be how the health check is configured. If it is wrongly configured, it may say unhealthy and offline all the time.
@github-actions[bot] commented on GitHub (Feb 10, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Feb 25, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.