Suddenly getting 403 errors for almost every serivce. #1651
Replies: 5 comments 1 reply
-
|
If your ISP changed did your server's IP (at home)? https://gethomepage.dev/en/more/troubleshooting/#service-widget-errors |
Beta Was this translation helpful? Give feedback.
-
|
Yes but there is nothing that explicitly references my WAN IP address. It's
either LAN ips or my domain name.
…On Mon, 3 July 2023, 1:15 am shamoon, ***@***.***> wrote:
If your ISP changed did your server's IP (at home)?
https://gethomepage.dev/en/more/troubleshooting/#service-widget-errors
—
Reply to this email directly, view it on GitHub
<#1651 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAP7FG4JH2HXRYH72ZQX5C3XOGGBHANCNFSM6AAAAAAZ3KPPRY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Domain names essentially just point to an IP, and yours probably changed. A lot of tools and OSes cache DNS so the issue may lie there somewhere. you mentioned authentik etc is broken too so presumably anything going through it (including homepage service widgets) won’t work either |
Beta Was this translation helpful? Give feedback.
-
|
I created a completely new stack with only Homepage, Sonarr and NPM to
test, and I still have the same error.
I use CloudFlare and a container that keeps my IP updated via API l, but I
tried disabling CF as well. Still have the same issue. My next step will be
to spin up the stack on another OS in case it is the server, but it's had
Ubuntu Server running stable forever and hasn't skipped a beat in the past.
…On Mon, 3 July 2023, 5:49 am shamoon, ***@***.***> wrote:
Domain names essentially just point to an IP, and yours probably changed.
A lot of tools and OSes cache DNS so the issue may lie there somewhere.
you mentioned authentik etc is broken too so presumably anything going
through it (including homepage service widgets) won’t work either
—
Reply to this email directly, view it on GitHub
<#1651 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAP7FG2NNFGYLT47PJ4AVUTXOHGFLANCNFSM6AAAAAAZ3KPPRY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been automatically closed due to inactivity. |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
I'm not sure why this has happened. I have not changed my setup in weeks and everything has been working flawlessly, other than changing ISP.
All my widgets are giving me 403 Errors
Browser shows
[2023-07-02T09:09:54.297Z] error: <credentialedProxyHandler> HTTP Error 403 calling http://overseerr.my.domain/api/v1/request/countfor every widget that accesses an API in some what, but for some reason, Plex still works.I have spent hours trying to debug it, but because I haven't actually changed anything, be it in Docker or Traefik or anything else, I have no idea what it could be.
Anyone have an ideas? For what it's worth, my Authentik LDAP Outpost docker container has stopped working at the same time, but it's not causing this, more likely what is causing this is affecting it.
All my services still work fine if I expose a port an access them from :, but anything through my domain is broken.
Beta Was this translation helpful? Give feedback.
All reactions