We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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>
When I access invidious via Pi-Hole local DNS, e.g. http://some-host.local:<port>, then I:
http://some-host.local:<port>
Could local DNS be a solution to YT blocking, or maybe I'm just lucky?
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
No branches or pull requests
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:When I access invidious via Pi-Hole local DNS, e.g.
http://some-host.local:<port>
, then I:Could local DNS be a solution to YT blocking, or maybe I'm just lucky?
The text was updated successfully, but these errors were encountered: