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

- YouTube failed with error 403 (can our server's IP be blocked?) #2187

Closed
tio-trom opened this issue Jun 24, 2021 · 9 comments
Closed

- YouTube failed with error 403 (can our server's IP be blocked?) #2187

tio-trom opened this issue Jun 24, 2021 · 9 comments

Comments

@tio-trom
Copy link

Error message: Unexpected response from upstream. cUrl error: (0) PHP error:
Query string: action=display&bridge=Youtube&context=By+username&u=physicswoman&duration_min=&duration_max=&format=Mrss
Version: dev.2021-04-25

This is our instance https://rss.trom.tf/ - it used to work like a charm for months. We did no change, and suddenly no youtube account works.

A friend has the same rss bridge version at https://rss.alexio.tf/ and it works on that instance.

That leads me to think that our server got banned by youtube. Is that possible?

@em92
Copy link
Contributor

em92 commented Jul 1, 2021

@dhuschde
Copy link
Contributor

I don't think that the IP would be a Problem, as it is working on Snopyta too.
And Snopyta runs one of the most famous Invidious Instances, and therefore their IP is blocked all the time...

And it should be on the same IP, as Nitter and the Twitter Bridge seeming to be blocked at the same time.

@tio-trom
Copy link
Author

Yah it started to work again not sure why....I can close this issue. As a side note, I too run lots of instances: invidious, nitter, and so forth at https://trom.tf/ so who knows maybe my server IP got temporarily blocked.

@tio-trom
Copy link
Author

tio-trom commented Aug 3, 2021

I would like to re-open the issue since it started to not work anymore. One day works, one day it does not. I would like to know how RSS Bridge fetches the youtube rss and if it is possible that youtube can ban the server IP for fetching too many (requesting too many).

Check https://rss.trom.tf/?action=display&bridge=Youtube&context=By+channel+id&c=UCvBqzzvUBLCs8Y7Axb-jZew+&duration_min=&duration_max=&format=Html as an example. Error is:

 - YouTube was unable to receive or process the remote website's content!
Error message: `Unexpected response from upstream.
cUrl error: (0)
PHP error: `
Query string: `action=display&bridge=Youtube&context=By+channel+id&c=UCvBqzzvUBLCs8Y7Axb-jZew+&duration_min=&duration_max=&format=Html`
Version: `dev.2021-04-25`

    Press Return to check your input parameters
    Press F5 to retry
    Check if this issue was already reported on GitHub (give it a thumbs-up)
    Open a GitHub Issue if this error persists

@tio-trom tio-trom reopened this Aug 3, 2021
@em92
Copy link
Contributor

em92 commented Aug 15, 2021

I cannot reproduce it. Maybe you have error.log with this error?

If you don't want errors to appear in feed, maybe following config is enough?

[error]
output = "http"

@tio-trom
Copy link
Author

What error.log file should I check? I see none in the main rss-bridge folder or var/log. But the issue is that I cannot create a youtube RSS feed as you can see in the link I provided above. It does not work. And I wonder why.

@em92
Copy link
Contributor

em92 commented Aug 16, 2021

What error.log file should I check? I see none in the main rss-bridge folder or var/log

That one that your server generates. If you are using nginx, that is probably /var/log/nginx/error.log

But the issue is that I cannot create a youtube RSS feed as you can see in the link I provided above. It does not work. And I wonder why.

At the moment it is related to issue #2113. I remember, that yesterday night (YEKT) it was working.

@dvikan dvikan closed this as completed Mar 26, 2022
@dvikan
Copy link
Contributor

dvikan commented Mar 26, 2022

@tio-trom The youtube feeds fails sometimes and this is normal. If I were to guess it's when they deploy to prod or something.

@dvikan dvikan reopened this Mar 26, 2022
@yamanq
Copy link
Contributor

yamanq commented May 11, 2022

This seems to be an intermittent error, so it is probably be fixed by #2692

@dvikan dvikan closed this as completed Jul 21, 2023
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

5 participants