-
-
Notifications
You must be signed in to change notification settings - Fork 114
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Environment
Services flapping
Bug Description
Reporting seems not to work correctly for some reason, service reports up, and then on next check down as timeout.
Wanted to migrate from uptime kuma, same docker host, so network is not an issue.
Container logs are lacking of any useful information that can help with diagnostics.
(And not it's not related to CF global outage that takes place right now, those are internal services)
Steps to Reproduce
As above
Expected Behavior
To see services reporting up and with correct ms delay.
Screenshots or Videos
No response
Logs
2025/11/18 14:50:08 🚀 Starting on port 8091
2025/11/18 14:50:08 ✓Backend integration enabled at http://localhost:8090
2025/11/18 14:50:08 ✓Service monitoring enabled with regional agent support
2025/11/18 14:50:08 ✓SSL notification monitoring enabled with Telegram support
2025/11/18 14:50:08 ✓Server monitoring enabled with notification support
2025/11/18 14:50:08 ✓Uptime monitoring enabled with notification support
2025/11/18 14:50:08 ✓Supported operations: ping, dns, tcp, http, ssl
2025/11/18 14:50:08 ✓Default Regional monitor started for region: Default (Agent ID: 1)
2025/11/18 14:50:08 Starting monitor for service: Portainer (http)Checklist
- I have searched existing issues to avoid creating duplicates.
- I have provided sufficient information to reproduce the issue.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working