homarr
homarr copied to clipboard
Jackett status Offline
Environment
Docker
Version
v0.9.2
Describe the problem
When Jackett added the ping module return Offline - 500 when Uptime Kuma return 405 and online.
Additional info
Please tick the boxes
- [X] You've read the docs
- [X] You've checked for duplicate issues
- [X] You've tried to debug yourself
You should be able to configure what HTTP codes the ping module accepts in the advanced tab, add 405 there and it will show green
The 405 code is not in the list. Maybe is that why it return 500.
The code from Uptime Kuma : 405 - Method Not Allowed
The 405 code is not in the list. Maybe is that why it return 500.
The code from Uptime Kuma : 405 - Method Not Allowed
I'll look to add it in the supported responses
The 405 code is not in the list. Maybe is that why it return 500.
The code from Uptime Kuma : 405 - Method Not Allowed
Hi,
Did you find a solution?
I was having a similar issue, I have a portainer instance at https://192.168.10.100:9443, but the status just shows up as "RED"
Added the status code '500' as shown and now it shows as up, but doesn't change even when I shutdown the container..
The 405 code is not in the list. Maybe is that why it return 500. The code from Uptime Kuma : 405 - Method Not Allowed
Hi, Did you find a solution? I was having a similar issue, I have a portainer instance at https://192.168.10.100:9443, but the status just shows up as "RED"
Added the status code '500' as shown and now it shows as up, but doesn't change even when I shutdown the container..
Maybe using HTTP instead of HTTPS locally could help ? Also you need to make sure to use the "final" URL (the one after you open the link. Same thing for other services such as plex)
Also you need to make sure to use the "final" URL (the one after you open the link. Same thing for other services such as plex)
This worked for me (for both Plex and Portainer) @ajnart @ashadanver
I know this is closed, but I found another way to test. In the Service URL
I set it to the following URL to invoke a test of the service health, but set the On Click URL
to http://<serverurl>
:
http://<serverurl>/api/v2.0/indexers/all/results/torznab/test?apikey=<apikey>