Skip to content
New issue

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

Using Phoenix servers causing YouTube to make viewers login #627

Open
jkemp814 opened this issue Sep 18, 2024 · 5 comments
Open

Using Phoenix servers causing YouTube to make viewers login #627

jkemp814 opened this issue Sep 18, 2024 · 5 comments
Assignees

Comments

@jkemp814
Copy link

As of late, YouTube have starting asking me to log in to verify I'm a human and keep the service. This may not be a problem for the Linux client, but more of heavy usage coming from Phoenix?

If I switch to Los Angeles, or Salt Lake City, this doesn't happen. Where would I report this issue if this isn't the place?

@abud7eem
Copy link

I wanna report the same issue YouTube consider nord server bots and require us to login, not only the USA server but cross multiple countries, this is deal breaker and hope nord team find solution.
Screenshot from 2024-09-18 22-30-09

@jkemp814
Copy link
Author

That's exactly what I'm experiencing. I have to switch to another city. I tried restarting the connection from Phoenix, and no matter what server I get from Phoenix, I get asked to log in. This may very well be Google trying to get viewers to log in to identify them. Why Phoenix so consistently is what's concerning.

@devzbysiu devzbysiu self-assigned this Sep 20, 2024
@devzbysiu
Copy link
Contributor

Hi, thank you for reporting this. We are checking what can be wrong there. I'll come back to you when I'll know more

@jkemp814
Copy link
Author

Excellent.

@devzbysiu
Copy link
Contributor

Hi, quick update. We have a suspicion what may be happening, but it's not confirmed yet. I'll let you know when we'll find a solution. In the meantime, switching to different city, as you mentioned, would be a quickest way to avoid the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants