Troubleshooting cors-proxy HTTP 500 #827
Unanswered
tmeuze
asked this question in
Help and Support
Replies: 1 comment
-
Usually just setting If you're still having issues, check the troubleshooting docs, specifically Fixing Widget CORS Errors. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
I am having the hardest time with certain widgets - specifically of self-hosted services - and cors-proxy. In the logs, I'm getting a very generic HTTP 500 error on client-side, and no logs for the container.
Aside the 500 error, I'm hit with endless timeout errors. I feel that might just be a side-effect of the issue.
I am using Traefik. I have CORS middleware set up as such:
CORS Proxy is on by default:
widgetsAlwaysUseProxy: true
It should be noted that I'm using an "internal-only" Traefik instance; the FQDN is not publicly addressable. I use a self-signed TLS certificate that clients blindly trust. However, I briefly routed a public FQDN to it, and also tried via direct IP, to no avail. Internet APIs like Weather, News, and Public IP work, while self-hosted service widgets like Healthchecks, Glances, and AdGuard - no matter if through Traefik or direct IP.
Any advice would be greatly appreciated. Thank you.
Beta Was this translation helpful? Give feedback.
All reactions