#Overseerr Migration Issues
1 messages Β· Page 1 of 1 (latest)
Just added everything, but forgot to do it as a reply.
Its okay
It is quire late here too so
Here ya go. Just curious, where does DNS come into play here? Just as an fyi, users access this via nginx proxy manager and a DNS subdomain. I would have thought DNS only comes into play only when someone want to get into Seerr? Not for Seerr to populate it's own info.
Thats a different dns.
The info doesnt come from seerr
It comes from tmdb
The images load directly from tmdb
Information too
On demand
ooooooh gotcha
Add the following into compose
dns:
- 9.9.9.9
- 8.8.8.8
- 1.1.1.1
In the service block. And redeploy
Just added that line, remove the docker, and re-composed with no luck unfortunately. Here is the new compose.yaml
No dice π
New logs pls
And we need to check browser logs
Press inspect
And go to network logs and send a screenshot
So get this, as I was going to inspect the browser, I had to reload the page to see the network logs for it right? And boom, it loaded everything. Maybe it was my Adguard extension? I removed adguard before inspecting to see if that was the cause but it did not fix the pages. After I ran the inspect refresh, to test the theory out I reinstalled adguard with all my filters and it still working... so who know what the hell was going on π€·ββοΈ