-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[BUG] Something is going on related to CORS and status checking #1690
Copy link
Copy link
Open
Labels
⚰️ Stale[ISSUE] [PR] No activity for over 1 month[ISSUE] [PR] No activity for over 1 month🐛 Bug[ISSUE] Ticket describing something that isn't working[ISSUE] Ticket describing something that isn't working👤 Awaiting Maintainer Response[ISSUE] Response from repo author is pending[ISSUE] Response from repo author is pending📌 Keep Open[ISSUE][PR] Prevent auto-closing[ISSUE][PR] Prevent auto-closing
Metadata
Metadata
Assignees
Labels
⚰️ Stale[ISSUE] [PR] No activity for over 1 month[ISSUE] [PR] No activity for over 1 month🐛 Bug[ISSUE] Ticket describing something that isn't working[ISSUE] Ticket describing something that isn't working👤 Awaiting Maintainer Response[ISSUE] Response from repo author is pending[ISSUE] Response from repo author is pending📌 Keep Open[ISSUE][PR] Prevent auto-closing[ISSUE][PR] Prevent auto-closing
Projects
Status
Awaiting Triage
Environment
Self-Hosted (Docker)
System
Rocky Linux 9.4, Podman 4.9.4-rhel
Version
3.1.1
Describe the problem
When enabling status checking, every service shows down with an
ETIMEDOUTerror. These services are all in fact running. When I manually query the status check endpoint, the same thing happens. This also happens when I go in my Docker container and query127.0.0.1/status-checkwith the right headers set. This error happens no matter what I pass to thestatus-checkendpoint. I've tried with and withouthttps://, I've tried sites like Google, I've tried the Dashy instance itself.Additionally, the
cors-proxyendpoint returnsETIMEDOUTfor everything in the same manner. I can't use the RSS feed widget with local checking, and I assume this is why, but I'm not sure if that's a separate issue.No errors show in the Dashy logs, and the errors in my browser console aren't very helpful, they tell me that
'unsafe-inline'doesn't appear in the CSP header, but I very explicitly set that header on my reverse proxy. I don't think that's related though because, like I said, it happens when Dashy queries itself too.Additional info
No response
Please tick the boxes