Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Chrome version mismatch causes Too Many Requests #172

Closed
wrusry opened this issue Oct 10, 2023 · 7 comments
Closed

Chrome version mismatch causes Too Many Requests #172

wrusry opened this issue Oct 10, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@wrusry
Copy link

wrusry commented Oct 10, 2023

Version

Auto-Southwest Check-In v6.1

Description

Hello, I had the failure in v 6.0 of too many requests on my outbound checkin. So, I upgraded to version 6.1 to try to use it to check in for my return flight on my computer which doesn't go to sleep and has a UPS to it. It also failed for "too many requests". See the below image. Previously, I had used southwest.py successfully, but I had the issue of matching my chrome with your version, so in my last successful usage, I had to downgrade my Chrome browser in order to make it work. I was excited to see that the program was no longer dependent on the Chrome version. Please let me know if you need any more info from my for troubleshooting purposes.

image

To Reproduce

  1. Run Python southwest.py confirmationcode first_name last_name

Expected Behavior

I expected that it would check me in. Instead I got the error: Failed to check in for flight confirmationcode for first last. Reason: Too Many Requests 429.

You can see from my version that I am using v 6.1.

My coding skills are rough at best, so forgive any incorrect formatting of this bug report.

Relevant logs and program output

No response

Additional context

No response
@wrusry wrusry added the bug Something isn't working label Oct 10, 2023
@jdholtz
Copy link
Owner

jdholtz commented Oct 10, 2023

Hey, thanks for filing this issue. What is the Chrome version you are using?

I see that your flight is no longer valid to check in. Do you get a 429 error when you log in?

@wrusry
Copy link
Author

wrusry commented Oct 11, 2023

I am using Chrome version 117.0.X

This is what get when I log in.

image

@dmytrokoren
Copy link
Contributor

@wrusry I had the same issue. Make sure that you are not on VPN. Southwest is blocking VPN Ip's now, and throwing 429 error too much requests.

@wrusry
Copy link
Author

wrusry commented Oct 11, 2023

I'm not on a VPN. Thanks, though.

I just relaunched my Google Chrome browser and it updated to version 118 and I tried logging in and it appears to work. I don't know why. It downloaded chromedriver it appears.
image

@dmytrokoren
Copy link
Contributor

I'm not on a VPN. Thanks, though.

I just relaunched my Google Chrome browser and it updated to version 118 and I tried logging in and it appears to work. I don't know why. It downloaded chromedriver it appears.

image

Glad it's working now. Sometimes a restart/relaunch solves issues.

@jdholtz
Copy link
Owner

jdholtz commented Oct 11, 2023 •
edited
Loading

I just relaunched my Google Chrome browser and it updated to version 118 and I tried logging in and it appears to work. I don't know why. It downloaded chromedriver it appears

It may have been a version mismatch that ended up resulting in you being detected. SeleniumBase has an option to set the driver version to match the browser (by default it only matches the major version), but it is currently not working in undetected mode (it is still headed when headless is specified).

I filed an issue on the SB repository, so when that is fixed, I will specify that when initializing the driver in this script. Then, it should ensure a version mismatch is never a problem.

@jdholtz jdholtz changed the title Failed to check in: Too Many requests (v 6.1) Chrome version mismatch causes Too Many Requests Oct 11, 2023
jdholtz added a commit that referenced this issue Oct 12, 2023
@jdholtz
Ensure chromedriver version matches browser version
ca56bc6 
Fixes #172.

There was an issue with using `driver_version="browser"` in undetected
Chrome mode in SeleniumBase 4.20.0. SeleniumBase 4.20.1 fixes that.
Additionally, the Docker image no longer needs to explicitly download
the Chromedriver (there is no option to do `sbase get chromedriver
browser` yet). Instead, it will download the driver the first time
SeleniumBase initializes the driver.
@jdholtz
Copy link
Owner

jdholtz commented Oct 12, 2023

Fixed in the latest commit of the develop branch. Will be part of either v6.2 or v7.0

@jdholtz jdholtz closed this as completed Oct 12, 2023
@jdholtz jdholtz mentioned this issue Oct 18, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dmytrokoren @wrusry @jdholtz