FOLLOWLIKER error code 400

lavalamp

Regular Member
Joined
Jan 22, 2016
Messages
234
Reaction score
61
I'm having this error "code:400 bad request was received from twitter" on all of my account. checked account manually and its fine

anyone using FL (twitter) also having this kind of issue?
 
Thanks for the reply. but what does that mean? my account was not aggressively doing actions.
this issue does not occur on my massplanner account

was it on my twitter account or the bot itself?
curious how much activity your doing on both tools/account
 
Thanks for the reply. but what does that mean? my account was not aggressively doing actions.
this issue does not occur on my massplanner account

was it on my twitter account or the bot itself?
The bot uses the API, i assume. It's an API limit. When you're logging in and using Twitter via browser, you aren't using the API, hence it's working fine.
 
Jarvee followliker shite sorry.
Change your bot to something better then see the results .
 
Hi Bro,
I'm having the same issue as you on FL. Just reported to the guys yesterday. I believe an update in necessary.
Send them a support email as well.
I'm a FL user for about 10 years and it never failed me :)
 
Last edited:
Hi Bro,
I'm having the same issue as you on FL. Just reported to the guys yesterday. I believe an update in necessary.
Send them a support email as well.
I'm a FL user for about 10 years and it never failed me :)
Me too...noticed this appearing over the last 24 hours and stopped everything on both of our FL Instals. I know there is a lot of anti FL shite doing the rounds...I can only say from my perspective like some others, I've been a regular user of FL for around 10 years now and it has never failed me either so expecting an update shortly I guess?
 
I'm having this error "code:400 bad request was received from twitter
" on all of my account. checked account manually and its fine
anyone using FL (twitter) also having this kind of issue?

It seems like your being blocked because of over usage.
 
Received a reply to my ticket request stating that they are looking into it...read working on an update
 
You have to cooooool down. The usual 24 hours and you are safe safe.
 
You have to cooooool down. The usual 24 hours and you are safe safe.
No this time it's a bit more serious...I shut down all operations over 36 hours ago and just fired up one instal and we're getting the same issues so an update is needed or else the IP/proxy ban is longer this time?
 
No this time it's a bit more serious...I shut down all operations over 36 hours ago and just fired up one instal and we're getting the same issues so an update is needed or else the IP/proxy ban is longer this time?
Yes that does not sound good. And proxies are working and all?
 
Yes that does not sound good. And proxies are working and all?
Proxies are working everywhere else and when I log in manually to Twitter accounts (we manage loads) they are fine but via FL...nothing happening at all so think there is something at the Bot end of things. I'm sure an update will resolve things...just when? Thats where one of our other Bots we use are so hot. We also use TSupremacy and literally if I flag an issue with their bot then usually there is an update roilled out within about 24 hours or max...sometimes sooner
 
Proxies are working everywhere else and when I log in manually to Twitter accounts (we manage loads) they are fine but via FL...nothing happening at all so think there is something at the Bot end of things. I'm sure an update will resolve things...just when? Thats where one of our other Bots we use are so hot. We also use TSupremacy and literally if I flag an issue with their bot then usually there is an update roilled out within about 24 hours or max...sometimes sooner
The bot uses the API, i assume. It's an API limit. When you're logging in and using Twitter via browser, you aren't using the API, hence it's working fine.
This is what is wrong as @HoNeYBiRD says. He knows what he is taking about had some software for Twitter himself if I am not mistsken.
 
This is what is wrong as @HoNeYBiRD says. He knows what he is taking about had some software for Twitter himself if I am not mistsken.
I would have thought not actually as Twitter came down very heavily on those using it's API sometime ago like ManageFlitter and a few others and they literally went outy of business overnight but FL kept on going so they might not be using the API as, as I said, if they were Twitter with one flick could have shut them down. But then I am no Tekkie so could well be wrong.
 
I would have thought not actually as Twitter came down very heavily on those using it's API sometime ago like ManageFlitter and a few others and they literally went outy of business overnight but FL kept on going so they might not be using the API as, as I said, if they were Twitter with one flick could have shut them down. But then I am no Tekkie so could well be wrong.
Well, the 400 bad request error code is a Twitter API http status code:
"The request was invalid or cannot be otherwise served. An accompanying error message will explain further. Requests without authentication are considered invalid and will yield this response."
https://developer.twitter.com/en/docs/response-codes
It's either a rate limit or if it effects many or all users of the tool, probably Twitter made some changes and the bot requires an update.
 
Back
Top