Unable to log in. State did not change error

[jasii]

After upgrading to 20.2 I haven't been unable to log in. It was working after the first docker fix, but then after 20.1 or 20.2 it's been giving me a state did not change error.

In my config folder I just have my config.yml file

Here's the error

[gatlinnewhouse]

Got the same issue here, same logs as well

[zachowj]

Try stopping the container for 24 hours, then start it up again.

[gatlinnewhouse]

Mine happened when I ran the container for the first time

[jasii]

I stopped the container for about 30 hours and when I started it again I am still getting the same error.

[JoeDaddy7105]

I got the same error on initial startup. I got a 2FA text as soon as it started up but I do not see how I can enter the code so I am assuming this does not support 2FA accounts.

[jasii]

I've had the container running for the past month with it constantly failing. There would be few times it would actually update, but it would be about once a week between updates in usage. Then starting today on a new usage reset cycle it seems to be updating consistently.

Is it working again for anybody else here in this issue thread?

[jaredbarranco]

Just dropping a note here that it isn't working for me. Same error as noted above. My account is 2FA and I would guess that this isn't supported based on the below screenshot. Fails after entering password with a "Shouldn't be here, starting over" message.

If I have time, I'll try and get a PR together. Shouldn't be too difficult to have branching logic based on 2FA code window

[gatlinnewhouse]

I've had the container running for the past month with it constantly failing. There would be few times it would actually update, but it would be about once a week between updates in usage. Then starting today on a new usage reset cycle it seems to be updating consistently.

Is it working again for anybody else here in this issue thread?

Still not working for me, even when I restart the container.

EDIT: Okay, so I went into the CLI for the container, ran npm i and yarn and was trying to just run it from there. Then I restarted it, and it worked? It might be because I signed in to my Xfinity account from my browser at home from the same IP?

[raptor464]

It was working sporadically for me up until a week ago. I have the container running on a windows machine and a raspberry pi and both refuse to connect. Raspberry Pi:

Windows:

It used to work every once and a while on both machines.

[Vendo232]

it stopped working for me as well

Error: State did not change for 3 tries. Last state: UsernameEntered. Next update at 12:20:21 PM

@zachowj

[derp90]

I am also getting this issue, first time running as well,

[gatlinnewhouse]

Can you try logging in to the website from a computer on the same network and then restarting the container?

[derp90]

Can you try logging in to the website from a computer on the same network and then restarting the container?

I tried that and had the same result

[derp90]

Here is a log from letting it sit for a while

[derp90]

I'm still not getting consistent results.

Just letting it run gets the data usage once every 1-5 days

[Vendo232]

I'm still not getting consistent results.

Just letting it run gets the data usage once every 1-5 days

what is your login frequency?

[derp90]

interval: 60 pageTimeout: 300

[derp90]

I think that pageTimeout is not being used. No matter what value I set this to, it will instantly fail the 3 tries within a few seconds. Currently set to 9999, I tried 600, and a few others with no difference. @zachowj

[derp90]

Is it possible to expose a port to access chromium so I can try logging in directly into the container. Something like this https://hub.docker.com/r/linuxserver/chromium

[zachowj]

It should be fixed in the latest release, v0.23.0.