Failing to login: Reason: Invalid credentials. Status code: 400. #223
Comments
|
I believe this may have been introduced with 7.2 upgrade. As the one login that failed for us was a password that contains a special character in this case "!". This wasn't present with v7.1. |
|
I was having this same issue with v7.2 |
|
I can confirm that removing all special characters from my password allowed me to successfully log in. |
|
Thanks for filing this issue. I can also reproduce this when my password contains special characters. However, I don't think it is specifically a v7.2 issue as nothing was changed with the way passwords are handled. Just to confirm, does your password with special characters work when you manually input it into the site
@babehboi in v7.1, I get a traceback saying something like: @davidkassa by commenting out the line from #140 which encodes the passwords, my login works successfully with special characters in my password. It's possible that Southwest changed the way passwords are handled to fix the discrepancy between their main site and mobile site. If you revert your change in #140 (remove the quote_plus function call), are you able to still successfully log in or do you get the issue you had before your PR? |
|
Yes, they seem to have fixed the issue and my password with the |
|
Thanks for testing @davidkassa. Reverted #140 which fixes the issue. Tested with the password |
|
I am running the 7.2 Development branch outside of Docker on RockyLinux 9. I haven't had a flight in several weeks since upgrading. Got the 400 Error on a flight from BNA to Cancun today. My password has always been alphanumeric and it works on mobile.southwest.com Only know I get the 400 error cause of Notifications to Pushover. I checked the logs in the folder, and this is all I see. auto-southwest-check-in.log |
|
the particular scenario that didn't work (but now does) was a password that
looked like a urlencoded password '%80' - just random luck.
…On Fri, Feb 23, 2024 at 12:31 PM Tony Holloway ***@***.***> wrote:
I am running the 7.2 Development branch outside of Docker on RockyLinux 9.
I haven't had a flight in several weeks since upgrading. Got the 400 Error
on a flight from BNA to Cancun today. My password has always been
alphanumeric and it works on mobile.southwest.com
Only know I get the 400 error cause of Notifications to Pushover. I
checked the logs in the folder, and this is all I see.
auto-southwest-check-in.log
2024-02-18 11:05:00 DEBUG MainProcess[log:23]: Initialized the application
2024-02-18 11:05:00 DEBUG MainProcess[main:112]: Auto-Southwest Check-In
v7.2
2024-02-18 11:05:00 DEBUG MainProcess[main:113]: Called with 1 arguments
2024-02-18 11:05:00 DEBUG MainProcess[config:108]: Initializing
configuration file
2024-02-18 11:05:00 DEBUG MainProcess[config:137]: Reading the
configuration file
2024-02-18 11:05:00 DEBUG MainProcess[config:151]: Reading configuration
from environment variables
2024-02-18 11:05:00 DEBUG MainProcess[config:54]: Setting check fares to
True
2024-02-18 11:05:00 DEBUG MainProcess[config:68]: Setting notification
level to <NotificationLevel.INFO: 1>
2024-02-18 11:05:00 DEBUG MainProcess[config:81]: Using 1 notification
services
2024-02-18 11:05:00 DEBUG MainProcess[config:85]: Setting retrieval
interval to 24 hours
2024-02-18 11:05:00 DEBUG MainProcess[config:120]: Creating configurations
for 1 accounts
2024-02-18 11:05:00 INFO MainProcess[main:85]: Sending test notifications
to 1 sources
—
Reply to this email directly, view it on GitHub
<#223 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGG6ALQP4PCEMDCLKKL3TDYVDN6NAVCNFSM6AAAAABDG63P2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRHAYDGOBSGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
My password is very simple in the over scheme of things. very alphanumeric. Did not run into this issue until upgrading to 7.2 development branch. Things were find when I was running 7.1 standard branch. I had 4 flights successfully check in with that version |
@netwavetech I'm not sure why the logs aren't being written. Are there any other log files (e.g. ending in
Version 7.2 did not change the way passwords were handled. All it did was report the correct error instead of crashing. Most likely, you are getting the errors due to changes made by Southwest on their website (which there have been a few). Are you on the latest commit of the develop branch? |
|
There are other logs, but they report the same. i.e. log.1 Here is the out put from git on my server. root@automation: |
|
Also just got a 500 Error - Fail Login to account with username XXXXXXXX, so guess that Southwest might have made another change .... |
|
@netwavetech are you still getting a 500 error? |
Unfortunately I am in Cancun until Sunday, have not gotten anything with Pushover since I got here yesterday, but do I not have remove access to the computer running the script til I get home |
|
I did get just get this error via Pushover... Failed to check in to Flight xxxxxxx for XXXXXXXX XXXXXXXX. Reason Bad Request 400. Check in at this url: https://mobile.southwest.com/check-in |
|
@netwavetech the issue is now being tracked in #235. |
Version
v7.2
Browser Version
121.0.6167.85
Description
Failed to log in to account with username . Reason: Invalid credentials. Status code: 400.
To Reproduce
I am running the script in a docker container within Unraid. The script successfully checked in for a flight on Saturday for a flight that was on Sunday. Since then, no credential changes have been made, but the script is now no longer able to successfully logged in. I previously set up credentials in environment variables. I migrated the credentials over to the configuration file to see if it would fix the issue, but no luck.
I can otherwise confirm that I am able to use the same credentials to login on the southwest site
Expected Behavior
No response
Relevant logs and program output
Additional context
No response
The text was updated successfully, but these errors were encountered: