Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring Remote Home Assistant #4366

Closed
2 tasks done
Lockie85 opened this issue Jan 13, 2024 · 4 comments
Closed
2 tasks done

Monitoring Remote Home Assistant #4366

Lockie85 opened this issue Jan 13, 2024 · 4 comments
Labels
area:deployment related to how uptime kuma can be deployed area:monitor Everything related to monitors help

Comments

@Lockie85
Copy link

Lockie85 commented Jan 13, 2024

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Hey,

I've tried to search and figure out the correct setup for this monitor but I can't figure it out. Help would be appreciated.

I've two remote servers. On server 1 I've Ubuntu with Docker running Uptime Kuma. On server 2 I've Home Assistant which I access via a domain e.g. https://myhassserver.uk/ (example domain not the real one)

I want to create a monitor in Uptime Kuma for the Home Assistant server via the domain but I'm failing to figure out how to do this.

What I've tried is a monitor type of HTTP(s) with the domain but I get a 403 error, Forbidden response.

Can anyone help me on how I'm meant to setup a monitor like this?

Many Thanks

📝 Error Message(s) or Log

403 forbidden response.

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

Ubuntu

🌐 Browser

Chrome

🐋 Docker Version

CE 2.19.4

🟩 NodeJS Version

No response

@Lockie85 Lockie85 added the help label Jan 13, 2024
@CommanderStorm
Copy link
Collaborator

403 forbidden usually means you are not allowed to access this site because the credentials you provided are not valid ,(assuming correct usage by HA)
https://en.wikipedia.org/wiki/HTTP_403

@CommanderStorm CommanderStorm added the area:monitor Everything related to monitors label Jan 13, 2024
@Lockie85
Copy link
Author

Lockie85 commented Jan 13, 2024

Yep that bit I get, but I'm not trying to access it/login (I'd assume). I'm only trying to check the page loads, in this case the login page. Would it need access/login to get a 200?

If I go to my domain I don't get a 403, I get the login page.

Worth noting I tried adding a monitor for a site like:
https://www.cloudflare.com
and it works fine. Which to me confirms Uptime Kuma can access the internet okay.

@CommanderStorm
Copy link
Collaborator

Please make sure that you have your ip banning configured correctly.
See https://community.home-assistant.io/t/solved-out-of-the-blue-now-i-get-403-forbidden/324107

See https://github.com/louislam/uptime-kuma/wiki/Troubleshooting#uptime-kuma-reports-down-but-the-service-can-be-accessed
=> please try to reproduce this behaviour and see what the endpoint is really responding with

Would it need access/login to get a 200

It seems to require correct credentials.
I don't have a HA instance to test on, it also depends on what endpoint you are using.
To be on the same page: you are using "System Health" to get the status?

@Lockie85
Copy link
Author

Argh! I've found the issue. I forgot my Cloudflare setup blocked IPs which weren't based in a specific country. Which my server is NOT! So I've had to allow the IP on cloudflare and now it works. Totally forgot I did that! Oops.

@CommanderStorm CommanderStorm added the area:deployment related to how uptime kuma can be deployed label Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:deployment related to how uptime kuma can be deployed area:monitor Everything related to monitors help
Projects
None yet
Development

No branches or pull requests

2 participants