I get error when reauthorizing "something went wrong" or

EXPECTED_KEY_NOT_PRESENTAn Error Has Been Logged
4C375/1 ("EXPECTED_KEY_NOT_PRESENT") encountered by H****.net Just now and 6 other errors in the last day.

Are you using a Twitter v1.1 or v2 API key? If you are using a v2 API key, there are known issues that would be present here as our system is not yet compatible with it.

I have no idea. It has been working years, no it stopped. I cant link my account.

 

Edited June 27, 20231 yr by Owdy

Unfortunately, Twitter is changing a lot here recently (including blocking use of keys) so you will need to login to the Twitter developer website to find out. Plus see if your API key is still valid. 

Thanks Elon. I disable whole feature...

Now, if i login with username and password:

 

Oops!

 

The CSRF protection key did not match. This may indicate a plugin or theme is out of date. Please contact technical support for more information

4 minutes ago, Owdy said:

Now, if i login with username and password:

 

Oops!

 

The CSRF protection key did not match. This may indicate a plugin or theme is out of date. Please contact technical support for more information

Try logging in again, likely your CSRF key is off.

well it appears we are also having this issue. got to love when people change things that's are not broken... i do despise that guy but that's despite the point...

So i guess there isnt anything we can do to fix it? we just have a standard twitter account which we use to tweet random pages. 

Thanks

 

13 minutes ago, commandosqueak1 said:

So i guess there isnt anything we can do to fix it?

At this juncture there is nothing to fix, I'm afraid. 

6 minutes ago, Jim M said:

At this juncture there is nothing to fix, I'm afraid. 

thats what i thought. never mind. just means i can go put my feet up now