You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a scenario where I have a power outage and all my systems shutdown, when the power comes back and they start up again I find that uptime kuma comes up before my router/DNS. This causes the Cloudflare tunnel to be stopped under the Reverse Proxy section.
Is there a way to have it retry a few times before giving up? I found the command to run to bring up the tunnel by looking at the process under the pm2-pi.service but I don't know how to manually start the cloudflared process that way.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.14
💻 Operating System and Arch
Raspberry Pi 2 - Raspbian 12
🌐 Browser
Chrome 130.0.6723.117
🖥️ Deployment Environment
Runtime: nodejs 18.19.0
Database: sqlite/embedded
Filesystem used to store the database on: ext4
number of monitors: 103
The text was updated successfully, but these errors were encountered:
🛡️ Security Policy
📝 Describe your problem
In a scenario where I have a power outage and all my systems shutdown, when the power comes back and they start up again I find that uptime kuma comes up before my router/DNS. This causes the Cloudflare tunnel to be stopped under the Reverse Proxy section.
Is there a way to have it retry a few times before giving up? I found the command to run to bring up the tunnel by looking at the process under the pm2-pi.service but I don't know how to manually start the cloudflared process that way.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.14
💻 Operating System and Arch
Raspberry Pi 2 - Raspbian 12
🌐 Browser
Chrome 130.0.6723.117
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: