Failed to create interstitial state

The iTSec plugin code responsible for triggering that error is located in the core/lib/login-interstitial/class-itsec-login-interstitial-session.php file, and looks like this:

if ( ! $mid = add_user_meta( $user->ID, self::META_KEY, $data ) ) {
	$error = new WP_Error( 'itsec-lib-login-interstitial-save-failed', esc_html__( 'Failed to create interstitial state.', 'better-wp-security' ) );
	ITSEC_Log::add_process_stop( $log, $error );

	return $error;
}

Is basically means if the WordPress core add_user_meta( $user_id, $meta_key, $meta_value, $unique = false ) function returns false, the in this topic reported error is returned.

So obviously the call to the add_user_meta() function seems to fail and thus returning false.

Next step is to figure out why the WordPress core add_user_meta() function fails.

+++++ To prevent any confusion, I’m not iThemes +++++

Hi @sbct,

If you need any further assistance please let me know.

Thanks @nlpro!
Sorry for the delay in answering but I got a little bit busy =)

I’ve tried to find out what was wrong but I’ve switched security plugin as it was becoming a little hard to find out the culprit and now I don’t get any error.

Thanks so much for your help!

Ok, no problem.

Even though we didn’t get to a solution, please do mark the issue as “resolved”. That way the community can focus more easily on the topics that do require further assistance/attention.

Hello @nlpro..I am also facing the same issue’ failed to create interstitial state’
I am not able to access my dashboard either..
If you could please help me with steps to solve the error..

As a workaround (to be able to login) try adding the line below right before the

/* That’s all, stop editing! Happy publishing. */

line in the wp-config.php file:

define( 'ITSEC_DISABLE_MODULES', true );

This way you can keep the iTSec plugin activated.

Experimental:

Once logged in remove the added line from the wp-config.php file.
It would be interesting to hear whether the WordPress Dashboard keeps functioning properly after removing the line from the wp-config.php file (Just prefix the line with // to make it a comment).

• This reply was modified 3 years, 6 months ago by nlpro.

@nlpro you seem to know about this issue well..

I would suggest if you would create a youtube video,or a long blog on this topic it will help a lot of people facing this issue.

I didnt get the steps that I am supposed to follow to solve this issue…

Could you please make it easier..on any way?

Thanks for your help

Hi dtr09,

Let’s try and do this step by step.

Have you ever logged (or are you able to log) into your hosting provider control panel from a browser ?

If yes, after logging in simply navigate to the File Manager.

(If not, find someone who is able to follow my instructions. Perhaps your hosting provider is willing to assist).

In the File Manager go to the httpdocs folder. Usually (but not always) this is the WordPress root folder and you should see WordPress folders like wp-admin, wp-content and wp-includes.

In this very same (root) folder you’ll find a file named wp-config.php

That’s the file that needs editing.

To be continued …

Turns out when this error occurs you are actually logged in …

In order to reproduce the error, I successfully tested 1 possible scenario. And despite the error occurring, simply going to the (https://www.domain.com/)wp-admin page on another tab within the same browser allowed me into the WordPress Dashboard …

So there is no need to edit the wp-config.php file.

When the error occurs simply open a new tab in the same browser and visit the address below:

https://www.domain.com/wp-admin

where www.domain.com should be substituted with your domain.

Note this is not a solution for the issue, just a workaround to get in.

• This reply was modified 3 years, 6 months ago by nlpro.
• This reply was modified 3 years, 6 months ago by nlpro.

Hi dtr09,

It would be great if you could confirm the last workaround in your WordPress env.