You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I've been using the method you prescribed here in my fork of modem-scraper and it had been working for a very long time. It looks like on or after September 23rd my SB8200 received firmware AB01.02.053.05_051921_193.0A.NSH which seems to have changed some things. For one when I log in using the default password it prompts me to change it, it seems like the certificate is new, and it seems that your workaround here no longer works. The breakdown seems to be at stage 1 where you get the token from the status page -- it just returns the login page instead of the token.
I tried to validate with your software here but I don't have rust experience and the Docker build failed for me.
My question is whether you are able to validate this and if so whether you have any knowledge of a new workaround.
The text was updated successfully, but these errors were encountered:
They changed the way you pass authentication and it looks like now you need a session ID cookie in addition to the authentication token. I got it to work, but sometimes the server incorrectly returns a 401 error even though I have authenticated. Logging in and then logging out again through the web page fixes this so one of the other things the web client does might have a side effect.
It's definitely a bug in the modem. It turns out sometimes sending the exact same requests to the modem multiple times with no other requests in between yields different results.
Hello, I've been using the method you prescribed here in my fork of modem-scraper and it had been working for a very long time. It looks like on or after September 23rd my SB8200 received firmware AB01.02.053.05_051921_193.0A.NSH which seems to have changed some things. For one when I log in using the default password it prompts me to change it, it seems like the certificate is new, and it seems that your workaround here no longer works. The breakdown seems to be at stage 1 where you get the token from the status page -- it just returns the login page instead of the token.
I tried to validate with your software here but I don't have rust experience and the Docker build failed for me.
My question is whether you are able to validate this and if so whether you have any knowledge of a new workaround.
The text was updated successfully, but these errors were encountered: