A filtering resolver can block a hostname used for media, guide data or authentication. That may be intentional policy or a classification issue. Diagnose the specific blocked resource without disabling all household protections or assuming the service is unavailable.
Check the filter's own evidence
If you administer the filtering system, inspect its documented activity log for the failure time. A blocked domain elsewhere in the log may be unrelated. Compare the actual app operation and avoid exposing account URLs in screenshots.
Use a targeted review
Ask the network administrator or filtering provider about a suspected false positive. A narrowly justified allow rule is different from turning filtering off for every device. Consider who else relies on the protection.
Keep alternative causes open
A service outage, typo or unsupported player can produce similar symptoms. If the log shows no relevant block, continue ordinary troubleshooting. Do not declare censorship or deliberate interference from one unsuccessful request.
