[Twitter Bridge] Error 403 Unexpected response from upstream. cUrl error: (0) PHP error:

[floriegl]

Describe the bug
The TwitterBridge returns the following error when trying to create or few an already existing RSS feed. The feed format does not matter.
[php7:notice] [pid 28] [client 192.168.0.14:52984] Exception: Unexpected response from upstream.\ncUrl error: (0)\nPHP error: in /app/lib/error.php:24\nStack trace:\n#0 /app/lib/contents.php(207): returnError()\n#1 /app/bridges/TwitterBridge.php(588): getContents()\n#2 /app/bridges/TwitterBridge.php(594): TwitterBridge->getApiContents()\n#3 /app/bridges/TwitterBridge.php(221): TwitterBridge->getRestId()\n#4 /app/bridges/TwitterBridge.php(241): TwitterBridge->getApiURI()\n#5 /app/actions/DisplayAction.php(135): TwitterBridge->collectData()\n#6 /app/index.php(38): DisplayAction->execute()\n#7 {main}, referer: http://192.168.0.107:3000/?action=display&bridge=Twitter&context=By+username&u=ici2cc&_cache_timeout=55&format=Html

To Reproduce
Steps to reproduce the behavior:

1. Install the newest version of rss-bridge (12ff697)
   (2. Allow custom cache timeouts in config)
2. Try to create any Twitter feed (nether account nor keyword works)
3. See error from screenshot

Expected behavior
I expected to see the RSS feed

Screenshots

Desktop:

• OS: Windows 10 19044.1415
• Browser: Brave
• Version: Version 1.33.106 Chromium: 96.0.4664.110

rss-bridge:latest (12ff697) running on Docker version 20.10.7, build 20.10.7-0ubuntu5~20.04.2

Additional context
The problem only appeared today a few hours ago, and I even tried it with a different public IP address

[ddeimeke]

Same behavior here. Existing feeds in my feedreader have the problem as well.

Server side: Ubuntu 20.04 LTS (recent patch level), Apache 2.4.41, PHP 7.4.3

RSS-Bridge installed from Git under a custom domain.

[ddeimeke]

It seems that Twitter had a problem, it works again for me.

[floriegl]

Looks like it. I now have the guest token issue again which normally fixes itself after a few retries. I posted this as an issue because the Twitter API status page didn't display anything regarding an outage. From what I have seen the TwitterBridge is not really reliable as the paid versions from example IFTTT or rss.app. Maybe we still want to make it more resilient. If I had any experience working with the Twitter API I would have offered to take a look. If it is not a serious concern to the project please just close this issue.

[em92]

Just pushed latest changes to TwitterBridge. Please update your instance and check if error happens after 3 hours.

[arokettu]

I'm experiencing Could not parse guest token. Is it related or a separate issue? (I'm using 3cef35a)

[em92]

I'm experiencing Could not parse guest token. Is it related or a separate issue? (I'm using 3cef35a)

Did you wait 3 hours after updating RSS-Bridge? 3 hours is required to invalidate cache with old api keys.
Another option - cleaning up cache directory.

[arokettu]

@em92 neither helps

[em92]

I suggested workaround here:
#2438

[dvikan]

#2379