-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Jackett monitoring without using the /health
endpoint
#2292
Comments
Usually it is a network issue. Did you allow your Uptime Kuma LXC container to access your LAN (192.168.1.X)? |
I have Radarr, plex, and sonarr on the same Vm and its working fine with Kuma. Only Jackett refuses to work. |
I experience the same issue. |
Thanks. That worked for me also. |
Not 100% sure but it looks like Jacketts web server is setup weirdly. Found this issue, could be why (uptime-kume gets redirected to login, but doesnt save cookie, goes back to dashboard, then because no cookie, back to login, infinite loop? Not even sure if kuma supports cookies, so I could be wrong): Jackett/Jackett#12475 (comment) |
Having the same problem as above.. |
We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days. |
This issue was closed because it has been stalled for 2 days with no activity. |
This is still an issue |
@pkishino Please open an issue with more details than the current issue.
|
I have the same issue. Adding
In Uptime Kuma I'm requesting Same goes for NPM, I'm proxying to In new incognito browser tab I can see it sets only |
I used https://hub.docker.com/r/linuxserver/jackett/ and getting curl to cooperate was a bit harder: curl -v --cookie-jar -b cookiefile --junk-session-cookies --location http://localhost:9117 Resulting log
Extracted request flow
So the real request flow is super weird. Persising cookies during rediects is already tracked in #2309 => re-closing as resolved (due to |
/health
endpoint
🛡️ Security Policy
📝 Describe your problem
Hello,
I'm trying to monitor jackett instance which is running on windows vm in proxmox. Uptime-Kuma cannot detect it while I can open jackett web interface with no problem in chrome. My local path is http://192.168.1.36:9117/UI/Dashboard.
Maybe someone has experience with it?
🐻 Uptime-Kuma Version
1.18.5
💻 Operating System and Arch
Lroxmox lxc container
🌐 Browser
Chrome
🐋 Docker Version
No response
🟩 NodeJS Version
No response
The text was updated successfully, but these errors were encountered: