Jump to content

Emby Server with uptimerobot


RameshRA
Go to solution Solved by Happy2Play,

Recommended Posts

RameshRA

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. 

Link to comment
Share on other sites

seanbuff

I've seen this discussed elsewhere:

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

Link to comment
Share on other sites

RameshRA
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

Link to comment
Share on other sites

RameshRA
4 hours ago, Luke said:

You could try /system/ping

can u elobrate what it is!

Link to comment
Share on other sites

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

Link to comment
Share on other sites

RameshRA
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

Link to comment
Share on other sites

  • Solution
Happy2Play

I believe he was talking about the api endpoint

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

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...