Did any of you ecnounter this error? It is working after I re-authenticate the credentials but after some time the connection seems to be dropping and I have to re-authenticate again.
Please try it with https://api.x.com/2/media/upload
1 Like
Imma try it for a day or sth. I will let you know, for now it’s working.
Same error tho
I had that error once too…
I basically just adjusted the URL (used “x” instead of “tweeter”) and added media_category and tweet_image to the body parameters.
1 Like
Unfortunately, I am still having issue with Cloudflare (((
Is it possible, that I am experiencing this issue, because I am using the self-hosted version of n8n?
I tried with n8n cloud and I’m having the exact same issue so it’s not related to self hosting.
I’m having the exact same issue. Did you find a solution?
It works fine when I use python or Node.JS locally. So probably due to the fact that Cloudflare blocks datacenter IPs
Ok. It wasn’t a credential or Cloudflare issue, actualy. I think n8n just couldn’t find correct explanation )))
So, @Philippe_Greenleaf , maybe you have the same issue. The problem for me was that I was mapping Image from the Google Drive. But somehow, that image had a wrong File Extention and naming. I added an edit Node to fix it. And it works )))
Sorry for the late answer but I didn’t investigate further and switched to a 3rd party app for posting on twitter. (upload-post.com)
hopefully some can help out here, I followed the instructions and it works fine when manually executing workflow it posts image to x no issues.
the problem is when this workflow triggered by a scheduler it fails with an error
“The connection to the server was closed unexpectedly, perhaps it is offline. You can retry the request immediately or wait and retry later.”
thank you
1 Like
I am facing the same issue. Kindly tell me how did you resolve it . I have successfully set my credentials and body but it is still giving me bad request error.
Thank you so much it really help me to resolve bad request error.
I have configured Twitter module which was working fine even without adding media_category and tweet_image to the body parameters but suddendly it start giving error. Now after adding media_category and tweet_image its working correctly.
I see you have still https://api.twitter.com/2/media/upload in your URL instance of https://api.x.com/2/media/upload.
And make sure to have
„media_category“ and „tweet_image“ in the body
Hmm, i’ve check the API v2 document and look like the media upload API only allow to upload image, not allow to upload video, so if some one who looking for how to upload video to X, maybe it’s not working now. I think we should wait, or we should try to use another 3rd party service.
Hi guys, I’m still facing the error “Forbidden - perhaps check your credentials?”
My connection says it’s ok, I created Body Parameters taking in consideration recommendations from this thread post.
Anyone can give some feedback on what i have wrong?
Make sure that in 𝕏 developer portal it is set to at least “read and write”. Preferably “read, write and direct message”
If it doesn’t stay selected (sometimes a bug), try this:
New Tokens on 𝕏
- Delete the app
- Create new app without “User authentication set up”
- Generate “Access Token and Secret”
- Set up the “User authentication set up” with “read & write” permission
- Regenerate every Token
I just did some texting and if I use the main X/twitter node to send a simple text tweet it works.
If I use the http request to insert the image as binary data, it gives me the “Forbidden - perhaps check your credentials?” and I’m using the same X OAuth2 API for both scenarios.
Also, I did validate and I already add the “User authentication set up” as "
Read and write and Direct message".