Can't connect Twitter with oauth1 or oauth2

[dunoxx]

I’m trying for so long to connect Twitter in N8N, i did it with oauth1 but when i try to post a tweet i get this error. Booth, HTTP request and Twitter Node get the same error.

OAUTH1 Error:

{"status":"rejected","reason":{"message":"401 - \"{\\n  \\\"title\\\": \\\"Unauthorized\\\",\\n  \\\"type\\\": \\\"about:blank\\\",\\n  \\\"status\\\": 401,\\n  \\\"detail\\\": \\\"Unauthorized\\\"\\n}\"","name":"Error","stack":"Error: 401 - \"{\\n  \\\"title\\\": \\\"Unauthorized\\\",\\n  \\\"type\\\": \\\"about:blank\\\",\\n  \\\"status\\\": 401,\\n  \\\"detail\\\": \\\"Unauthorized\\\"\\n}\"\n    at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12)\n    at RedirectableRequest.handleResponse (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:238:9)\n    at RedirectableRequest.emit (node:events:525:35)\n    at RedirectableRequest.emit (node:domain:489:12)\n    at RedirectableRequest._processResponse (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:356:10)\n    at ClientRequest.RedirectableRequest._onNativeResponse (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:62:10)\n    at Object.onceWrapper (node:events:628:26)\n    at ClientRequest.emit (node:events:525:35)\n    at ClientRequest.emit (node:domain:489:12)\n    at HTTPParser.parserOnIncomingClient (node:_http_client:693:27)\n    at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)\n    at TLSSocket.socketOnData (node:_http_client:534:22)\n    at TLSSocket.emit (node:events:513:28)\n    at TLSSocket.emit (node:domain:489:12)\n    at addChunk (node:internal/streams/readable:315:12)\n    at readableAddChunk (node:internal/streams/readable:289:9)\n    at TLSSocket.Readable.push (node:internal/streams/readable:228:10)\n    at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)"}}

OAUTH2
I also tryded to connect by oauth2. I can see the conection screen, but when i try to connect i get a error message.

[MutedJam]

Hi @dunoxx, I am so sorry for the trouble. The n8n Twitter node and the credentials it uses are in urgent need of an update, but unfortunately I do not have any ETA for this right now.

I tried connecting with OAuth1 which previously worked for me (described here), but this now also fails. So I think with the recent changes at Twitter and the overdue updates on our side I don’t have any great suggestion.

It might still be worth re-testing this from time to time though and playing with your exact parameters. @hrsdimitrov appears to have had some success with the generic authentication overe here (so pretty much the thing now failing for me):

I successfully set up a generic Twitter OAuth1 credential, but I still get a 401 error

Hi, @EmeraldHerald. Thank you for the fast reply. I actually managed to get it working with an HTTP node. Turns out I wasn’t passing the data property correctly and that for some reason was returning a Unauthenticated HTTP code. My final solution ended up looking like that: [1] [2] I hope that helps other people having a similar issue. Have a nice day.

[dunoxx]

Hi Muted, thaks for your reply.

I’ll w8 for the upgrade. Hope it comes ASAP

Best

[Fran_Palokaj]

@MutedJam, I’m very new to this whole space, and I’m having a similar issue with connecting to Twitter, although I’m getting a different error message. When I try to authorise the app, it says that ‘local host refuses to connect’.

Do you know if this is because of the same issue? Or do I have to change something else in my settings?

Cheers

[MutedJam]

Hi @Fran_Palokaj, welcome to the community. This looks like your n8n instance isn’t listening on localhost port 5678. Are you running your n8n instance locally? If not, you might need to provide the correct URL to n8n via the WEBHOOK_URL environment variable. If your n8n instance is listening under https://n8n.franpalokaj.com for example, you’d need to set WEBHOOK_URL=https://n8n.franpalokaj.com/ .

[Fran_Palokaj]

Thanks for the reply! I’m running my N8N via the Railway app. I’ll play around with the WEBHOOK_URL to see if I can fix it =)

[Fran_Palokaj]

@MutedJam I’ve tried adding the environment variable to my deployment on Railway.app. Afterwars, I tried connecting the Gmail API, but it said that I didn’t comply with the OAUTH rules Google has set.

When I removed the variable I no longer got this error, but I once again got the “couldn’t connect” error, that I got last time. Do you have any idea what I should change?

I added the variable in the following format

WEBHOOK_URL=n8n-production-59fe.up.railway.app

[MutedJam]

Unfortunately I am not familiar with railway. Is it perhaps serving n8n via an insecure (http) connection rather than https? Quite a few services require https for everything other than localhost, so this might be why Google complains.

As for the WEBHOOK_URL variable, make sure to include the protocol, so something like WEBHOOK_URL=https://n8n-production-59fe.up.railway.app/

Please do let me know if you’re still having any trouble after looking into these points

[bartv]

Is there any news about the Twitter node update? I’m running into this issue now as well…

[Jon]

Hey @bartv,

There are a couple of issues in this thread which one are you seeing?

[bartv]

Whoops! I jumped to a reply as soon as I saw my own issue - sorry I’m having trouble setting up the oAuth connection and I’m getting the 401 response.

[Jon]

Ah we have seen that one a bunch, is it a newly made Twitter app and how are you running n8n at the moment?

[bartv]

I suspect I didn’t set something up on Twitter correctly as I can’t get my credentials to work on make.com either. I’ll look into fixing that first!

[Fran_Palokaj]

@MutedJam

WEBHOOK_URL=https://n8n-production-59fe.up.railway.app/

I played around for an hour, and finally figured out the solution. There were multiple variables that needed to be changed, and I found them in this blog article: Hosting n8n for Free with Railway

Also attached a screenshot with the most important info:

[bartv]

So I checked my settings and I think my Twitter app setup is correct. I regenerated the client secret but still get the 401 error when trying to connect the account.

@Jon

How are you running n8n at the moment?

I’m not sure what you mean, but I run a docker instance. Is that what you need to know?