After upgrading to v1.18.0 (enterprise edition) from v1.17.1, the status of resources are not displayed as they should. They are detected as healthy but shown as unknown.
However, if I create a new resource, healthcheck status is shown as it should. It only affects already created resources.
Environment
OS Type & Version: Debian 13 (trixie)
Pangolin Version: ee-1.18.0
Gerbil Version: 1.3.1
Traefik Version: 3.6.14
Newt Version: 1.11.0
To Reproduce
Update from ee-1.17.1 to ee-1.18.0 with public resources already created with healthchecks.
Expected Behavior
The UI should display the health status instead of unknown (when it is, indeed, known).
Originally created by @evoke0 on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2930
### Describe the Bug
After upgrading to v1.18.0 (enterprise edition) from v1.17.1, the status of resources are not displayed as they should. They are detected as healthy but shown as unknown.
However, if I create a new resource, healthcheck status is shown as it should. It only affects already created resources.
<img width="422" height="283" alt="Image" src="https://github.com/user-attachments/assets/b3cff3ba-1705-4c07-9bc1-2e94282d1ecf" />
<img width="900" height="111" alt="Image" src="https://github.com/user-attachments/assets/f9904f7f-18a0-4967-82ea-d72023d729b9" />
### Environment
- OS Type & Version: Debian 13 (trixie)
- Pangolin Version: ee-1.18.0
- Gerbil Version: 1.3.1
- Traefik Version: 3.6.14
- Newt Version: 1.11.0
### To Reproduce
Update from ee-1.17.1 to ee-1.18.0 with public resources already created with healthchecks.
### Expected Behavior
The UI should display the health status instead of unknown (when it is, indeed, known).
Furthermore, as one can see on the first picture of the original post, the uptime tracking bar is empty, but I'm guessing this is because tracking started on the same day, but if you see the uptime tracking bar from Sites, a green bar is shown for the previous day (which tracking wasn't on as it was still on ee-1.17.1). Let me know if you need a new issue to keep track of this.
<!-- gh-comment-id:4346360728 -->
@evoke0 commented on GitHub (Apr 29, 2026):
Furthermore, as one can see on the first picture of the original post, the uptime tracking bar is empty, but I'm guessing this is because tracking started on the same day, but if you see the uptime tracking bar from Sites, a green bar is shown for the previous day (which tracking wasn't on as it was still on ee-1.17.1). Let me know if you need a new issue to keep track of this.
<img width="376" height="99" alt="Image" src="https://github.com/user-attachments/assets/aaf1d215-e514-4c16-ad37-1d5f96400f05" />
@oschwartz10612 commented on GitHub (Apr 29, 2026):
@evoke0 this is a known part of the migration. We will see if we can adjust but if you bounce your sites (restart newt) then it should report the correct status for the resource.
The bar for the resource is actually correct in its "unknown" state the bars will show as gray.
<!-- gh-comment-id:4346513840 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
@evoke0 this is a known part of the migration. We will see if we can adjust but if you bounce your sites (restart newt) then it should report the correct status for the resource.
The bar for the resource is actually correct in its "unknown" state the bars will show as gray.
@oschwartz10612 commented on GitHub (Apr 29, 2026):
I will see if I can update the migration to pull the target health check status to enter the first resource status correctly.
<!-- gh-comment-id:4346536510 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
I will see if I can update the migration to pull the target health check status to enter the first resource status correctly.
if you bounce your sites (restart newt) then it should report the correct status for the resource.
Yes, I confirm this solves the issue. I'll keep this open until you close it with the commit if you feel it's worth it. Thanks!
<!-- gh-comment-id:4347496986 -->
@evoke0 commented on GitHub (Apr 29, 2026):
> if you bounce your sites (restart newt) then it should report the correct status for the resource.
Yes, I confirm this solves the issue. I'll keep this open until you close it with the commit if you feel it's worth it. Thanks!
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 @evoke0 on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2930
Describe the Bug
After upgrading to v1.18.0 (enterprise edition) from v1.17.1, the status of resources are not displayed as they should. They are detected as healthy but shown as unknown.
However, if I create a new resource, healthcheck status is shown as it should. It only affects already created resources.
Environment
To Reproduce
Update from ee-1.17.1 to ee-1.18.0 with public resources already created with healthchecks.
Expected Behavior
The UI should display the health status instead of unknown (when it is, indeed, known).
@evoke0 commented on GitHub (Apr 29, 2026):
Furthermore, as one can see on the first picture of the original post, the uptime tracking bar is empty, but I'm guessing this is because tracking started on the same day, but if you see the uptime tracking bar from Sites, a green bar is shown for the previous day (which tracking wasn't on as it was still on ee-1.17.1). Let me know if you need a new issue to keep track of this.
@oschwartz10612 commented on GitHub (Apr 29, 2026):
@evoke0 this is a known part of the migration. We will see if we can adjust but if you bounce your sites (restart newt) then it should report the correct status for the resource.
The bar for the resource is actually correct in its "unknown" state the bars will show as gray.
@oschwartz10612 commented on GitHub (Apr 29, 2026):
I will see if I can update the migration to pull the target health check status to enter the first resource status correctly.
@evoke0 commented on GitHub (Apr 29, 2026):
Yes, I confirm this solves the issue. I'll keep this open until you close it with the commit if you feel it's worth it. Thanks!