Hi, I'm using v1.16.2 Enterprise Edition.
Last week I enabled monitoring for my reccources.
One day after, I recognized, that my services are not reachable anymore. Especially Nextcloud.
I tested everything and checked log files but found no errors and no solution.
This morning I remembered that I enabled the monitoring. I turned it of, forced a change in my reccource (changed port and back) and tadaa. It's working again.
create ressource for nextcloud
http:8001
it works.
enable health monitoring in ressource same http:8001
shows "no available server"
disable health monitoring
it works.
Expected Behavior
fix the bux
Originally created by @mkoenig4182 on GitHub (Mar 23, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2694
### Describe the Bug
Hi, I'm using v1.16.2 Enterprise Edition.
Last week I enabled monitoring for my reccources.
One day after, I recognized, that my services are not reachable anymore. Especially Nextcloud.
I tested everything and checked log files but found no errors and no solution.
This morning I remembered that I enabled the monitoring. I turned it of, forced a change in my reccource (changed port and back) and tadaa. It's working again.
### Environment
- OS Type & Version: Ubuntu 22.04
- Pangolin Version: latest -- 1.16.2 Enterprise Edition
- Gerbil Version: latest --
- Traefik Version: latest -- 3.6.11
- Newt Version: latest -- 1.10.3
- Olm Version: (if applicable)
### To Reproduce
create ressource for nextcloud
http:8001
it works.
enable health monitoring in ressource same http:8001
shows "no available server"
disable health monitoring
it works.
### Expected Behavior
fix the bux
@LaurenceJJones commented on GitHub (Mar 23, 2026):
Expected Behavior
fix the bux
robux or just bux? 😆 jokes aside, can you check Newt logs for the healthcheck ping and as well inform us what settings you using for the healthcheck? (your description is rather lacking context a image of the setting will suffice)
As its most likely the healthcheck is actually failing rather than being a bug for us to fix.
<!-- gh-comment-id:4109327683 -->
@LaurenceJJones commented on GitHub (Mar 23, 2026):
> Expected Behavior
> fix the bux
robux or just bux? 😆 jokes aside, can you check Newt logs for the healthcheck ping and as well inform us what settings you using for the healthcheck? (your description is rather lacking context a image of the setting will suffice)
As its most likely the healthcheck is actually failing rather than being a bug for us to fix.
Oh, for sure. I also recognized that this issue is not to all monitorings.
Is "no available server" the pangolin feedback of the health check? then I think that the routing goes to the health check result.
I recognized, that this issue is not to all ressources.
Maybe a ping refuse from system tells pangolin, that no service is running and reroute to the check result?!
Here the settings of my NC ressource:
Here the Monitoring:
<!-- gh-comment-id:4109406619 -->
@mkoenig4182 commented on GitHub (Mar 23, 2026):
Oh, for sure. I also recognized that this issue is not to all monitorings.
Is "no available server" the pangolin feedback of the health check? then I think that the routing goes to the health check result.
I recognized, that this issue is not to all ressources.
Maybe a ping refuse from system tells pangolin, that no service is running and reroute to the check result?!
Here the settings of my NC ressource:
<img width="1246" height="889" alt="Image" src="https://github.com/user-attachments/assets/f5f54d6e-c9c1-49db-a9ef-ffaac2138b4a" />
Here the Monitoring:
<img width="543" height="731" alt="Image" src="https://github.com/user-attachments/assets/ff022825-c499-4e73-bf6c-2ec1a1eb97c2" />
I don't know if this is the problem here, but you have to take care that the health-check endpoint (in your case http://192.168.178.137:8001/) returns an http status code between 200 and 300 (I assume it have to start with a "2"). So if this endpoint here e.g. returns a 302 to redirect you to maybe /login then for pangolin the health check failed.
To see what the endpoint returns I think you can go to the newt client (if it's in a container go into that container) and e.g. use curl to see what's returned. For example you can use curl -v http://192.168.178.137:8001/ and look at the results, esp. the http return code.
<!-- gh-comment-id:4162121303 -->
@cgoIT commented on GitHub (Mar 31, 2026):
I don't know if this is the problem here, but you have to take care that the health-check endpoint (in your case http://192.168.178.137:8001/) returns an http status code between 200 and 300 (I assume it have to start with a "2"). So if this endpoint here e.g. returns a 302 to redirect you to maybe /login then for pangolin the health check failed.
To see what the endpoint returns I think you can go to the newt client (if it's in a container go into that container) and e.g. use curl to see what's returned. For example you can use `curl -v http://192.168.178.137:8001/` and look at the results, esp. the http return code.
@LaurenceJJones commented on GitHub (Apr 7, 2026):
Marking as complete, as seems to be a none issue, as the feature described if healthcheck fails the target is removed and if there is a single target traefik by default will return a "no server available" message.
<!-- gh-comment-id:4198578285 -->
@LaurenceJJones commented on GitHub (Apr 7, 2026):
Marking as complete, as seems to be a none issue, as the feature described if healthcheck fails the target is removed and if there is a single target traefik by default will return a "no server available" message.
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 @mkoenig4182 on GitHub (Mar 23, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2694
Describe the Bug
Hi, I'm using v1.16.2 Enterprise Edition.
Last week I enabled monitoring for my reccources.
One day after, I recognized, that my services are not reachable anymore. Especially Nextcloud.
I tested everything and checked log files but found no errors and no solution.
This morning I remembered that I enabled the monitoring. I turned it of, forced a change in my reccource (changed port and back) and tadaa. It's working again.
Environment
To Reproduce
create ressource for nextcloud
http:8001
it works.
enable health monitoring in ressource same http:8001
shows "no available server"
disable health monitoring
it works.
Expected Behavior
fix the bux
@LaurenceJJones commented on GitHub (Mar 23, 2026):
robux or just bux? 😆 jokes aside, can you check Newt logs for the healthcheck ping and as well inform us what settings you using for the healthcheck? (your description is rather lacking context a image of the setting will suffice)
As its most likely the healthcheck is actually failing rather than being a bug for us to fix.
@mkoenig4182 commented on GitHub (Mar 23, 2026):
Oh, for sure. I also recognized that this issue is not to all monitorings.
Is "no available server" the pangolin feedback of the health check? then I think that the routing goes to the health check result.
I recognized, that this issue is not to all ressources.
Maybe a ping refuse from system tells pangolin, that no service is running and reroute to the check result?!
Here the settings of my NC ressource:
Here the Monitoring:
@cgoIT commented on GitHub (Mar 31, 2026):
I don't know if this is the problem here, but you have to take care that the health-check endpoint (in your case http://192.168.178.137:8001/) returns an http status code between 200 and 300 (I assume it have to start with a "2"). So if this endpoint here e.g. returns a 302 to redirect you to maybe /login then for pangolin the health check failed.
To see what the endpoint returns I think you can go to the newt client (if it's in a container go into that container) and e.g. use curl to see what's returned. For example you can use
curl -v http://192.168.178.137:8001/and look at the results, esp. the http return code.@LaurenceJJones commented on GitHub (Apr 7, 2026):
Marking as complete, as seems to be a none issue, as the feature described if healthcheck fails the target is removed and if there is a single target traefik by default will return a "no server available" message.