How to Band-aid Fix Seerr “Movie Not Found” Error
My Seerr started acting up after the migration. In the web UI, it threw “Movie Not Found” errors — not on everything, but, evidently, only on some of the movies in the library and some of the entries in trending. Both LAN and WAN were working fine. The errors weren’t persistent. They came and went, and the number of films affected kept changing.
In my case, the metadata DB test passed (Settings > Metadata Providers), so the connection itself wasn’t the problem. My gut feeling pointed to an IPv4 and IPv6 conflict, for reasons I’ll get to in the tangent. In Settings > Network, check “Force IPv4 Resolution First”. It requires a restart, so restart Seerr. The option is still experimental; it may behave differently in future versions.
I live in South Korea, where landline ISPs normally don’t offer IPv6. v6 is mostly reserved for newer networks, such as mobile. A home lab on default settings, routed through a Korean ISP, hits the usual local quirks. Nothing extraordinary. Things start to stutter when you add systems that are IPv6-capable but never get working IPv6 connectivity.
I’m in a bind when it comes to IPv6, where the hardware sold and the software available both default to IPv6. Mesh routers. Docker containers. Even ISPs offer IPv6 for new ‘accounts’. This isn’t a problem easily solved by calling customer support. It’s a corporate policy not to pursue a residential IPv6 offering. So this is one of those occasions where I end up applying ‘legacy support mode’.
Comments will be automatically closed after 30 days.