Closed miclgael closed 1 week ago
I don't know what to make of this but if I have two conflicting scenarios I thought might be of interest:
When I access invidious via IP e.g. http://<local-ip-address>:<port>, then I:
http://<local-ip-address>:<port>
1) Can log in 2) Cannot play videos within Invidious UI
When I access invidious via Pi-Hole local DNS, e.g. http://some-host.local:<port>, then I:
http://some-host.local:<port>
1) Cannot log in 2) Can play videos within Invidious UI
Could local DNS be a solution to YT blocking, or maybe I'm just lucky?
Hello, this sounds like a configuration issue on your side.
As maintainers, we do not have a lot of free time so you should ask your question on our matrix channel or IRC.
I don't know what to make of this but if I have two conflicting scenarios I thought might be of interest:
When I access invidious via IP e.g.
http://<local-ip-address>:<port>
, then I:1) Can log in 2) Cannot play videos within Invidious UI
When I access invidious via Pi-Hole local DNS, e.g.
http://some-host.local:<port>
, then I:1) Cannot log in 2) Can play videos within Invidious UI
Could local DNS be a solution to YT blocking, or maybe I'm just lucky?