Emby Server with uptimerobot

[RameshRA 1]

My emby server is running in windows 11 machine and cloudflare tunnel for access it from outside. I use uptimerobot for server status which works fine for other services including jellyfin. But status of emby server is always down. Is there any internal settings needs to be adjusted. 

[Luke 42077]

Hi, what url are you having it check?

[RameshRA 1]

i have a own domain. "emby.example.com"

[seanbuff 1315]

I've seen this discussed elsewhere:

Might be something Emby specific. There are other monitoring alternatives you could also try @RameshRA

[Luke 42077]

You could try /system/ping

[RameshRA 1]

5 hours ago, seanbuff said:

I've seen this discussed elsewhere:

Might be something Emby specific. There are other monitoring alternatives you could also try @RameshRA

Yes its emby specific i guess. Everyone says uptime kuma works fine but i did't tried yet

[RameshRA 1]

4 hours ago, Luke said:

You could try /system/ping

can u elobrate what it is!

[Luke 42077]

29 minutes ago, RameshRA said:

can u elobrate what it is!

It’s just a URL that doesn’t do any work so it’s a good one if all you want to do is see if the server is available

[RameshRA 1]

5 hours ago, Luke said:

It’s just a URL that doesn’t do any work so it’s a good one if all you want to do is see if the server is available

C:\Users\rames>ping 192.168.1.2
Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\rames>ping emby.example.com

Pinging emby.example.com [xxx.xx.xxx.xxx] with 32 bytes of data:
Reply from xxx.xx.xxx.xxx: bytes=32 time=34ms TTL=57
Reply from xxx.xx.xxx.xxx: bytes=32 time=34ms TTL=57
Reply from xxx.xx.xxx.xxx: bytes=32 time=34ms TTL=57
Reply from xxx.xx.xxx.xxx: bytes=32 time=33ms TTL=57

Ping statistics for xxx.xx.xxx.xxx:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 34ms, Average = 33ms

[Happy2Play 9780]

I believe he was talking about the api endpoint

http://localhost:8096/emby/System/Ping?api_key=yourapikey

 

[NikeSwe 122]

I use https://emby.example.com/system/ping as ping target in UptimeRobot. Seem to be working. 

[acid 0]

I can also say, that for me uptimerobot does not work with emby. But I would guess this is rather an uptimerobot issue, though I would not know how it could happen.

I am using an HAproxy relay for IPv6 to IPv4 and Nginx Reverse Proxy for the SSL offloading an service redirection to the Emby VM.

This is working fine, just the monitoring is not working. Also here Uptime Kuma is working fine.

[acid 0]

Hi guys,
I just found out the problem.

Emby does reply with a 404 on HEAD requests to any URL.

Uptimerobot with the free user limits is only able to send HEAD requests ...

@Luke

[NikeSwe 122]

I'm on the Free 50-plan that doesn't really exist. Only for old users before they changed the plans.
I used ping before for Emby but I have changed to look for the absence of the keyword "Emby Server" but that's still available in the free plan? 
The URL I use: https://emby.example.com/system/ping

I also use the free plan over at Cronitor that allows me to enter comments and react to issues it detects. UptimeMonitor requires a higher plan for that.

Edited October 10, 2024 by NikeSwe

[Luke 42077]

11 hours ago, acid said:

Hi guys,
I just found out the problem.

Emby does reply with a 404 on HEAD requests to any URL.

Uptimerobot with the free user limits is only able to send HEAD requests ...

@Luke

We'll add HEAD support to system/ping. Thanks.

[Conroy 0]

On 11/10/2024 at 06:49, Luke said:

We'll add HEAD support to system/ping. Thanks.

Did this ever get added - seeing this issue occur now?

[seanbuff 1315]

1 hour ago, Conroy said:

Did this ever get added - seeing this issue occur now?

Yes, it's been added to the latest stable release 4.8.11.0

[acid 0]

@seanbuff
 

I did a test on my 4.8.11.0 Windows Installation without success. Still getting the old 500 internal error on the curl request:

curl --location --head 'http://10.0.20.127:8096/system/ping'

[seanbuff 1315]

27 minutes ago, acid said:

Still getting the old 500 internal error on the curl request:

Don't have access to a stable version right now, but it's definitely working on my beta server. 

Responding with a 200 OK

[NikeSwe 122]

I use Cronitor with Method: HEAD. Works fine. 200 OK (but also on beta so that's maybe not relevant)

Edited September 30, 2025 by NikeSwe