Uptime Kuma Monitoring Issue with Cloudflare Proxy

[arshsahzad]

I've encountered an issue with Uptime Kuma monitoring in conjunction with Cloudflare proxy settings and I'm seeking some advice or insights to solve this issue.

Here's the scenario: I'm currently utilizing Uptime Kuma for monitoring my services/apps and using Cloudflare for DNS management. When the proxy is enabled in Cloudflare, Uptime Kuma operates as expected and monitors the services effectively. However, if I disable the proxy for certain services/apps like GitLab, Uptime Kuma ceases to watch them and shows as down.

Has anyone else encountered a similar issue or found a workaround for this situation? Your insights and suggestions would be greatly appreciated.

[BrutalBirdie]

huh? This sounds super strange since its the exact opposite way I would expect problems.
So lets get this straight:

• WITH Cloudflare Proxy, no problem
• WITHOUT Cloudflare Proxy, problem

---

Are you monitoring via http/s calls or port?
More in depth settings of your uptime kuma would be interesting.

[arshsahzad]

I'm using http/s calls for the monitoring

CF Proxy is Off for GitLab

GitLab is down in Uptime Kuma due to CF Proxy Off

[girish]

@arshsahzad said in Uptime Kuma Monitoring Issue with Cloudflare Proxy:

I've noticed that disabling the Cloudflare proxy is necessary for the GitLab SSH clone to function as intended.

This is expected. Cloudflare only proxies http and https traffic. SSH is a different protocol and won't be proxied. You can git clone via HTTPS instead if you want to keep it behind Cloudflare.

[arshsahzad]

Hi @girish,

Just to clarify from my end, the issue is not with SSH (git clone). The problem lies with Uptime Kuma. When Cloudflare proxy is enabled, Uptime Kuma monitors the services effectively. However, if the Cloudflare proxy is disabled, Uptime Kuma stops monitoring the services.

[girish]

@arshsahzad Uptime Kuma cannot monitor GIT SSH which is behind Cloudflare. The service is not reachable when Cloudflare proxying is enabled . You can test this yourself, try to git ssh clone when proxying is enabled - it won't work.