siteMonitor shows error but curl GET works inside the container #4660

heathen711 · 2025-01-26T06:05:53Z

heathen711
Jan 26, 2025

Description

Problem: siteMonitor worked perfectly fine for me when completely internal, moved to behind SWAG and nginx, and now the siteMonitor (with an internal bound IP address) only shows ERROR.

Read the docs and it says that siteMonitor uses a HEAD or a GET request.

Installed curl within the container.

HEAD -> 401 -> Okay, that failed
GET -> 200 w/ form html page

Why is the GET request not showing status?

homepage version

v0.10.9 (b5f4daa, Jan 6, 2025)

Installation method

Docker

Configuration

- homepage.siteMonitor=http://192.168.7.106:65471/sonarr

Container Logs

/homepage$ docker compose up
[+] Running 1/1
 ✔ Container homepage  Created                                                                                                                      0.0s 
Attaching to homepage
homepage  | Listening on port 3000
homepage  | [2025-01-26T15:44:57.589Z] error: <plexProxyHandler> HTTP 404 communicating with Plex. Data: <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>
homepage  | [2025-01-26T15:44:58.199Z] error: <plexProxyHandler> HTTP 404 communicating with Plex. Data: <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>
homepage  | [2025-01-26T15:45:02.884Z] error: <plexProxyHandler> HTTP 404 communicating with Plex. Data: <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>
homepage  | [2025-01-26T15:45:07.935Z] error: <plexProxyHandler> HTTP 404 communicating with Plex. Data: <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>
homepage  | [2025-01-26T15:45:12.985Z] error: <plexProxyHandler> HTTP 404 communicating with Plex. Data: <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>
homepage  | [2025-01-26T15:45:18.090Z] error: <plexProxyHandler> HTTP 404 communicating with Plex. Data: <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>
homepage  | [2025-01-26T15:45:23.198Z] error: <plexProxyHandler> HTTP 404 communicating with Plex. Data: <html><head><title>Not Found</title></head><body><h1>404 Not Found</h1></body></html>

Browser Logs

No response

Troubleshooting

/homepage$ docker exec homepage curl --head http://192.168.7.106:65471/sonarr
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0HTTP/1.1 401 Unauthorized
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
Date: Sun, 26 Jan 2025 05:50:17 GMT
Server: Kestrel

/homepage$ docker exec homepage curl -X GET http://192.168.7.106:65471/sonarr
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0<!doctype html><html lang="en">....

Answered by heathen711

Jan 26, 2025

Okay, I figured it out, your tooltip shows the 401, while mine says error. Soo I went and check the swag config and sure enough siteMonitor wasn't being forwarded...

so the frontend doesn't log an error or show a meaningful error when an /api/* isn't reachable. Worth a fix?

View full answer

shamoon · 2025-01-26T06:56:42Z

shamoon
Jan 26, 2025
Maintainer

Container Logs

No response

Please check them

14 replies

shamoon Jan 26, 2025
Maintainer

status 401 seems rather clear, presumably something on the receiving end

heathen711 Jan 26, 2025
Author

status 401 seems rather clear, presumably something on the receiving end

Read the docs and it says that siteMonitor uses a HEAD or a GET request.

Installed curl within the container.

HEAD -> 401 -> Okay, that failed
GET -> 200 w/ form html page

Yes, but the doc says it uses a head or a get request, so shouldn't it try both and report if one succeeds?

shamoon Jan 26, 2025
Maintainer

Ok, reminding myself of how this works

homepage/src/pages/api/siteMonitor.js

Line 35 in dc33824

if (status > 403) {

its only retried for > 403 because we accept 401/403 as 'up' for site monitor

so testing this locally

      - homepage.siteMonitor=http://localhost:8080/some/path?x-set-response-status-code=401

{"status":401,"latency":9.58779200000572}

Looks fine:

So Im nt sure what's going on for you

heathen711 Jan 26, 2025
Author

Okay, I figured it out, your tooltip shows the 401, while mine says error. Soo I went and check the swag config and sure enough siteMonitor wasn't being forwarded...

so the frontend doesn't log an error or show a meaningful error when an /api/* isn't reachable. Worth a fix?

Answer selected by heathen711

shamoon Jan 26, 2025
Maintainer

Sorry, what do you mean?

heathen711 Jan 26, 2025
Author

Assumptions here:
The JS in the main page is calling http://localhost:3000/api/siteMonitor?groupName=XXX&serviceName=XXX to populate the box.
When it fails to reach http://localhost:3000/api/siteMonitor it says HTTP status error maybe it could:

log an error to console for web inspection?
make the tooltip say "/api/siteMonitor" not reachable?
both?

shamoon Jan 26, 2025
Maintainer

I mean, there is literally an error reaching its own api endpoint, that sounds like an error to me. Most people do not have a setup so restrictive that its preventing this (because then you'd have to allow almost every single request homepage makes to itself)

2025-01-27T03:07:45Z

github-actions[bot]
bot Jan 27, 2025

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

siteMonitor shows error but curl GET works inside the container #4660

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 14 replies

{{title}}

Container Logs

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

siteMonitor shows error but curl GET works inside the container #4660

heathen711 Jan 26, 2025

Description

homepage version

Installation method

Configuration

Container Logs

Browser Logs

Troubleshooting

Replies: 2 comments · 14 replies

shamoon Jan 26, 2025 Maintainer

Container Logs

shamoon Jan 26, 2025 Maintainer

heathen711 Jan 26, 2025 Author

shamoon Jan 26, 2025 Maintainer

heathen711 Jan 26, 2025 Author

shamoon Jan 26, 2025 Maintainer

heathen711 Jan 26, 2025 Author

shamoon Jan 26, 2025 Maintainer

github-actions[bot] bot Jan 27, 2025

heathen711
Jan 26, 2025

Replies: 2 comments 14 replies

shamoon
Jan 26, 2025
Maintainer

shamoon Jan 26, 2025
Maintainer

heathen711 Jan 26, 2025
Author

shamoon Jan 26, 2025
Maintainer

heathen711 Jan 26, 2025
Author

shamoon Jan 26, 2025
Maintainer

heathen711 Jan 26, 2025
Author

shamoon Jan 26, 2025
Maintainer

github-actions[bot]
bot Jan 27, 2025