I’m trying to connect to Twitter, I followed the guide in the documentation.
Everything seems fine until the last step, after authenticating on Twitter and returning back to n8n on the OAuth Redirect URL (/rest/oauth1-credential/callback) I get the following error:
{"code":0,"message":"Unable to get access tokens!","hint":""}
Any idea on what I’m doing wrong? I can’t seem to find anything via Google or here.
It might be worth checking the nginx logs to make sure the callback url is being set correctly in the return so you don’t end up with it using the internal IP instead of the one you are telling it to use.
I am out of ideas, I can give mine a check later I am using nginx in front of mine as well so it is almost the same as your setup I have a few more options set for n8n and nginx though.
Are you using the Consumer Key and Consumer Secret, or are you using the API Key and Access Token? Also, can you let me know if you’re facing similar issues with other nodes?
I’m using the Consumer key and secret, when I try the Access token and secret I can not even open the authentication Twitter pop-up.
I then get this error
I actually thought I already tested the N8N_USE_DEPRECATED_REQUEST_LIB before but apparently something else was wrong then. Or maybe the result was cached, not sure.
I just tested this with an n8n.cloud instance and it worked fine. I was able to connect and perform queries using OAuth authentication on version 0.141.1.
@RicardoE105 can you test locally and see if it works fine for you? I don’t have it set up here. If it does, then maybe it could be something with nginx, although everything seems to be ok and considering it works on version 0.138.0, I hardly doubt so.
I’m getting the same error, but I’m using the OAuth1 credential type to connect to Garmin API.
I’m running n8n 0.152.0 in a VPS with docker (I used the recommended server install with docker compose). I also set N8N_USE_DEPRECATED_REQUEST_LIB to true.
Is there anything I can do to investigate this further?