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

Heroku: Twitter @GonLamperouge failed with error 500 #1734

Closed
gradha opened this issue Sep 7, 2020 · 6 comments
Closed

Heroku: Twitter @GonLamperouge failed with error 500 #1734

gradha opened this issue Sep 7, 2020 · 6 comments
Labels
Bug-Report Confirmed bug report

Comments

@gradha
Copy link

gradha commented Sep 7, 2020

Describe the bug
Can't make work the twitter bridge with usernames.

To Reproduce
Steps to reproduce the behavior:

  1. Go to a freshly installed heroku deployment.
  2. Search for twitter bridge and click "show more"
  3. Select the username bridge and fill username, then press html.
  4. See error:

Error message: Could not parse guest token
Query string: action=display&bridge=Twitter&context=By+username&u=GonLamperouge&format=Html
Version: dev.2020-02-26

Expected behavior
Some html with the user's tweets.

Desktop (please complete the following information):
Info displayed by heroku after pushing:

remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> PHP app detected
remote: -----> Bootstrapping...
remote: -----> Installing platform packages...
remote:        - php (7.4.9)
remote:        - ext-mbstring (bundled with php)
remote:        - apache (2.4.46)
remote:        - nginx (1.18.0)
remote: -----> Installing dependencies...
remote:        Composer version 1.10.10 2020-08-03 11:35:19
remote:        Loading composer repositories with package information
remote:        Installing dependencies from lock file
remote:        Nothing to install or update
remote:        Generating optimized autoload files
remote: -----> Preparing runtime environment...
remote:        NOTICE: No Procfile, using 'web: heroku-php-apache2'.
remote: -----> Checking for additional extensions to install...
remote: -----> Discovering process types
remote:        Procfile declares types -> web
remote: 
remote: -----> Compressing...
remote:        Done: 14.6M
remote: -----> Launching...
remote:        Released v8
remote:        https://toomanyfeeds.herokuapp.com/ deployed to Heroku
remote: 
remote: Verifying deploy... done.

Maybe there is something else that has to be done for heroku deployments other than just pushing? Like cleaning some stale cache/database?

@gradha gradha added the Bug-Report Confirmed bug report label Sep 7, 2020
@em92
Copy link
Contributor

em92 commented Sep 7, 2020

@em92 em92 closed this as completed Sep 7, 2020
@gradha
Copy link
Author

gradha commented Sep 7, 2020

According to Heroku deploy logs I'm on commit 747bb6a, but why does it not work though?

@gradha
Copy link
Author

gradha commented Sep 7, 2020

I tried changing one of the JSON files to verify that deployments work:

$ git diff upstream_master..master
diff --git a/app.json b/app.json
index f184799..a249b42 100644
--- a/app.json
+++ b/app.json
@@ -3,6 +3,6 @@
   "name": "RSS-Bridge",
   "description": "RSS-Bridge is a PHP project capable of generating RSS and Atom feeds for websites which don't have one.",
   "repository": "https://github.com/RSS-Bridge/rss-bridge",
-  "keywords": ["php", "rss-bridge", "rss"]
+  "keywords": ["php", "rss-bridge", "rss", "test deploy 747bb6ad9ca1b0d2d03b6d93a5ea99af5830e1c7" ]
 }

The change can be seen, but the twitter bridge still returns 500.

@em92 em92 reopened this Sep 8, 2020
@em92 em92 changed the title Twitter @GonLamperouge failed with error 500 Heroku: Twitter @GonLamperouge failed with error 500 Sep 8, 2020
@em92
Copy link
Contributor

em92 commented Sep 8, 2020

FYI, we don't have active maintainer for Twitter bridge.

@jNullj
Copy link
Contributor

jNullj commented Jan 3, 2022

i got http 500 multiple time now for some nasa feeds on twitter, like @NASAPersevere
im using docker with latest image

@em92
Copy link
Contributor

em92 commented Jan 17, 2022

Should be fixed after #2414

@em92 em92 closed this as completed Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug-Report Confirmed bug report
Projects
None yet
Development

No branches or pull requests

3 participants