Twitter Connected Services - Error 500

I am trying to set up Twitter as a connected service to my pod. I have been approved for a Twitter developer account and have tried using key/secret pairs from

  • Projects & Apps -> Project -> {my-project} -> Consumer Keys
  • Projects & Apps -> Project -> {my-project} -> Authentication Tokens -> Access token & secret
  • Projects & Apps -> Standalone -> {my-project-v1} -> Consumer Keys -> API key & secret

Each time I have copy/pasted and verified the key and secret values to my diaspora.yml file and restarted diaspora using RAILS_ENV=production bin/eye restart web. I would then refresh my diaspora web page and click the option to connect Twitter to my account. Each time I get the “We’re sorry…” 500 error page.

log/production.log has the following relevant lines:

[2020-12-20T06:34:07] INFO  PID-740 TID-70328303516020 Rails: Started GET "/auth/twitter" for at 2020-12-20 06:34:07 +0000
[2020-12-20T06:34:07] FATAL PID-740 TID-70328303516020 Rails:
[2020-12-20T06:34:07] FATAL PID-740 TID-70328303516020 Rails: OAuth::Unauthorized (401 Authorization Required):
[2020-12-20T06:34:07] FATAL PID-740 TID-70328303516020 Rails:
[2020-12-20T06:34:07] FATAL PID-740 TID-70328303516020 Rails: vendor/bundle/ruby/2.6.0/gems/oauth-0.5.4/lib/oauth/consumer.rb:236:in `token_request'
vendor/bundle/ruby/2.6.0/gems/oauth-0.5.4/lib/oauth/consumer.rb:155:in `get_request_token'
vendor/bundle/ruby/2.6.0/gems/omniauth-oauth-1.1.0/lib/omniauth/strategies/oauth.rb:28:in `request_phase'
vendor/bundle/ruby/2.6.0/gems/omniauth-twitter-1.4.0/lib/omniauth/strategies/twitter.rb:61:in `request_phase'

Which keys should I be using? Should I be using the v1.1 “standalone” credentials or the V2 “project” credentials? I have read the instructions on the wiki, but there is a warning they may be out of date and the Twitter instructions do not match the current processes for setting up API access.

2 posts were merged into an existing topic: Connected Services - Error 500