Open jdholtz opened 1 week ago
Macbook M1 no docker 1 account, ~30 reservations
'Too Many Requests' error only with logins, not reservations (see https://github.com/jdholtz/auto-southwest-check-in/issues/277#issuecomment-2201695743)
Hey @natecodes, could you follow the guidelines to posting in this thread. It will help make these issues easier to understand and help fix.
Using the thread below, people can report if they are or aren't seeing these errors as well as the environment they're using (Docker, laptop, server, etc.) and how many accounts/reservations are being monitored.
Pasting all logs are fine, but please use a collapsed section in order to not clutter the main thread.
Hey @natecodes, could you follow the guidelines to posting in this thread. It will help make these issues easier to understand and help fix.
Using the thread below, people can report if they are or aren't seeing these errors as well as the environment they're using (Docker, laptop, server, etc.) and how many accounts/reservations are being monitored.
Pasting all logs are fine, but please use a collapsed section in order to not clutter the main thread.
Sure, let me edit my original post. Sorry about that
I am using the latest develop for several upcoming flights and I have noticed the following on startup scheduling the checkin...
Will post updates when checkin time comes
Error I get from the docker image is...
auto-southwest | 2024-07-02 01:34:13 DEBUG Process-6[reservation_monitor:86]: Scheduling flight check-ins for 1 reservations
auto-southwest | 2024-07-02 01:34:13 DEBUG Process-6[checkin_scheduler:79]: Retrieving reservation information
auto-southwest | 2024-07-02 01:34:28 DEBUG Process-6[utils:58]: Failed to make request after 20 attempts: Forbidden 403
auto-southwest | 2024-07-02 01:34:28 DEBUG Process-6[utils:60]: Response body: {
auto-southwest | "code": 403050700
auto-southwest | }
@mickgiles the logs for the develop image should show Request error on attempt ... Sleeping for ... seconds until next attempt
multiple times before failing completely. Could you make sure you've pulled the latest develop image (just run docker pull jdholtz/auto-southwest-check-in:develop
again)?
Macbook M1 no docker 1 account, ~30 reservations
@natecodes do the reservations also eventually run into 403s and/or 429s?
Macbook M1 no docker 1 account, ~30 reservations
@natecodes do the reservations also eventually run into 403s and/or 429s?
Not sure as I can't even get it to log in. This is happening on both master and develop.
2024-07-01 19:14:02 DEBUG Process-1[webdriver:177]: Waiting for headers_set to be set
2024-07-01 19:14:02 DEBUG Process-1[webdriver:181]: headers_set set successfully
2024-07-01 19:14:02 DEBUG Process-1[webdriver:177]: Waiting for login_request_id to be set
2024-07-01 19:14:02 DEBUG Process-1[webdriver:169]: Login response has been received
2024-07-01 19:14:02 DEBUG Process-1[webdriver:181]: login_request_id set successfully
2024-07-01 19:14:03 DEBUG Process-1[webdriver:237]: Logging in failed for an unknown reason
2024-07-01 19:14:03 WARNING Process-1[reservation_monitor:201]: Encountered a Too Many Requests error while logging in. Skipping reservation retrieval```
@natecodes you can try with just a confirmation number and name to skip logging in altogether.
@mickgiles the logs for the develop image should show
Request error on attempt ... Sleeping for ... seconds until next attempt
multiple times before failing completely. Could you make sure you've pulled the latest develop image (just rundocker pull jdholtz/auto-southwest-check-in:develop
again)?
using this image most succeeded but 1 reservation failed with the following logs
@natecodes you can try with just a confirmation number and name to skip logging in altogether.
On develop
using this image most succeeded but 1 reservation failed with the following logs
@mickgiles it looks like you typed in the wrong confirmation number (the debug logs say it must be six characters long). Double check the info you put in to make sure it is correct.
@natecodes great, it looks like the only issue is the log in but not checking in. I'll edit your original comment to note that
using this image most succeeded but 1 reservation failed with the following logs
@mickgiles it looks like you typed in the wrong confirmation number (the debug logs say it must be six characters long). Double check the info you put in to make sure it is correct.
It works fine running on bare metal with the same config A second start of the same container didn't yield that error but the reservations worked but the accounts failed with this error
Note that this is happening on both master and dev
On Mon, Jul 1, 2024 at 7:41 PM Mick Giles @.***> wrote:
using this image most succeeded but 1 reservation failed with the following logs
@mickgiles https://github.com/mickgiles it looks like you typed in the wrong confirmation number (the debug logs say it must be six characters long). Double check the info you put in to make sure it is correct.
It works fine running on bare metal with the same config A second start of the same container didn't yield that error but the reservations worked but the accounts failed with this error
auto-southwest | 2024-07-02 02:38:06 DEBUG Process-1[webdriver:177]: Waiting for trips_request_id to be set auto-southwest | 2024-07-02 02:38:06 DEBUG Process-1[webdriver:181]: trips_request_id set successfully auto-southwest | 2024-07-02 02:38:06 DEBUG Process-1[reservation_monitor:211]: Successfully retrieved 2 reservations auto-southwest | 2024-07-02 02:38:06 DEBUG Process-1[reservation_monitor:86]: Scheduling flight check-ins for 2 reservations auto-southwest | 2024-07-02 02:38:06 DEBUG Process-1[checkin_scheduler:79]: Retrieving reservation information auto-southwest | 2024-07-02 02:38:06 DEBUG Process-1[utils:68]: Request error on attempt 1: Forbidden 403. Sleeping for 2.51 seconds until next attempt auto-southwest | 2024-07-02 02:38:09 DEBUG Process-1[utils:68]: Request error on attempt 2: Forbidden 403. Sleeping for 2.18 seconds until next attempt auto-southwest | 2024-07-02 02:38:11 DEBUG Process-1[utils:68]: Request error on attempt 3: Forbidden 403. Sleeping for 2.60 seconds until next attempt auto-southwest | 2024-07-02 02:38:14 DEBUG Process-1[utils:68]: Request error on attempt 4: Forbidden 403. Sleeping for 1.57 seconds until next attempt auto-southwest | 2024-07-02 02:38:16 DEBUG Process-1[utils:68]: Request error on attempt 5: Forbidden 403. Sleeping for 1.15 seconds until next attempt auto-southwest | 2024-07-02 02:38:18 DEBUG Process-1[utils:68]: Request error on attempt 6: Forbidden 403. Sleeping for 2.13 seconds until next attempt auto-southwest | 2024-07-02 02:38:20 DEBUG Process-1[utils:68]: Request error on attempt 7: Forbidden 403. Sleeping for 2.23 seconds until next attempt auto-southwest | 2024-07-02 02:38:22 DEBUG Process-1[utils:68]: Request error on attempt 8: Forbidden 403. Sleeping for 1.63 seconds until next attempt auto-southwest | 2024-07-02 02:38:24 DEBUG Process-1[utils:68]: Request error on attempt 9: Forbidden 403. Sleeping for 3.00 seconds until next attempt auto-southwest | 2024-07-02 02:38:28 DEBUG Process-1[utils:68]: Request error on attempt 10: Forbidden 403. Sleeping for 1.57 seconds until next attempt auto-southwest | 2024-07-02 02:38:29 DEBUG Process-1[utils:68]: Request error on attempt 11: Forbidden 403. Sleeping for 2.33 seconds until next attempt auto-southwest | 2024-07-02 02:38:32 DEBUG Process-1[utils:68]: Request error on attempt 12: Forbidden 403. Sleeping for 1.04 seconds until next attempt auto-southwest | 2024-07-02 02:38:33 DEBUG Process-1[utils:68]: Request error on attempt 13: Forbidden 403. Sleeping for 1.59 seconds until next attempt auto-southwest | 2024-07-02 02:38:35 DEBUG Process-1[utils:68]: Request error on attempt 14: Forbidden 403. Sleeping for 1.63 seconds until next attempt auto-southwest | 2024-07-02 02:38:37 DEBUG Process-1[utils:68]: Request error on attempt 15: Forbidden 403. Sleeping for 2.46 seconds until next attempt auto-southwest | 2024-07-02 02:38:40 DEBUG Process-1[utils:68]: Request error on attempt 16: Forbidden 403. Sleeping for 1.00 seconds until next attempt auto-southwest | 2024-07-02 02:38:41 DEBUG Process-1[utils:68]: Request error on attempt 17: Forbidden 403. Sleeping for 2.20 seconds until next attempt auto-southwest | 2024-07-02 02:38:43 DEBUG Process-1[utils:68]: Request error on attempt 18: Forbidden 403. Sleeping for 2.54 seconds until next attempt auto-southwest | 2024-07-02 02:38:46 DEBUG Process-1[utils:68]: Request error on attempt 19: Forbidden 403. Sleeping for 2.71 seconds until next attempt auto-southwest | 2024-07-02 02:38:49 DEBUG Process-1[utils:68]: Request error on attempt 20: Forbidden 403. Sleeping for 2.34 seconds until next attempt auto-southwest | 2024-07-02 02:38:51 DEBUG Process-1[utils:74]: Failed to make request after 20 attempts: Forbidden 403 auto-southwest | 2024-07-02 02:38:51 DEBUG Process-1[utils:75]: Response body: { auto-southwest | "code": 403050700 auto-southwest | } auto-southwest | 2024-07-02 02:38:51 DEBUG Process-1[checkin_scheduler:85]: Failed to retrieve reservation info. Error: Forbidden 403. Exiting auto-southwest | 2024-07-02 02:38:51 DEBUG Process-1[notification_handler:80]: Sending failed reservation retrieval notification...
— Reply to this email directly, view it on GitHub https://github.com/jdholtz/auto-southwest-check-in/issues/277#issuecomment-2201721635, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI5RD6ZANLXKEAFE7NZIVMLZKIHOLAVCNFSM6AAAAABKDWBMYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBRG4ZDCNRTGU . You are receiving this because you were mentioned.Message ID: @.***>
So as of right now is the login functionality not supposed to work at all?
So as of right now is the login functionality not supposed to work at all?
No, it’s supposed to and has been working for me. Not sure at the moment why you are having issues.
So as of right now is the login functionality not supposed to work at all?
Do you have any special characters in your account password? If so, try removing them first.
I'm trying to run this against two reservations. One works, the other consistently yields this. Latest develop
.
2024-07-04 04:14:40 DEBUG Process-1[webdriver:147]: Loading Southwest home page (this may take a moment)
2024-07-04 04:14:48 DEBUG Process-1[webdriver:84]: Waiting for valid headers
2024-07-04 04:14:48 DEBUG Process-1[webdriver:178]: Waiting for headers_set to be set
2024-07-04 04:14:48 DEBUG Process-1[webdriver:182]: headers_set set successfully
2024-07-04 04:14:48 DEBUG Process-1[reservation_monitor:86]: Scheduling flight check-ins for 1 reservations
2024-07-04 04:14:48 DEBUG Process-1[checkin_scheduler:79]: Retrieving reservation information
2024-07-04 04:14:49 DEBUG Process-1[utils:68]: Request error on attempt 1: Forbidden 403. Sleeping for 2.69 seconds until next attempt
2024-07-04 04:14:53 DEBUG Process-1[utils:68]: Request error on attempt 2: Forbidden 403. Sleeping for 2.29 seconds until next attempt
2024-07-04 04:14:56 DEBUG Process-1[utils:68]: Request error on attempt 3: Forbidden 403. Sleeping for 2.39 seconds until next attempt
2024-07-04 04:15:00 DEBUG Process-1[utils:68]: Request error on attempt 4: Bad Request 400. Sleeping for 2.76 seconds until next attempt
2024-07-04 04:15:04 DEBUG Process-1[utils:68]: Request error on attempt 5: Forbidden 403. Sleeping for 2.74 seconds until next attempt
2024-07-04 04:15:08 DEBUG Process-1[utils:68]: Request error on attempt 6: Forbidden 403. Sleeping for 1.56 seconds until next attempt
2024-07-04 04:15:11 DEBUG Process-1[utils:68]: Request error on attempt 7: Forbidden 403. Sleeping for 2.50 seconds until next attempt
2024-07-04 04:15:14 DEBUG Process-1[utils:68]: Request error on attempt 8: Forbidden 403. Sleeping for 2.25 seconds until next attempt
2024-07-04 04:15:18 DEBUG Process-1[utils:68]: Request error on attempt 9: Bad Request 400. Sleeping for 2.87 seconds until next attempt
2024-07-04 04:15:22 DEBUG Process-1[utils:68]: Request error on attempt 10: Forbidden 403. Sleeping for 2.80 seconds until next attempt
2024-07-04 04:15:26 DEBUG Process-1[utils:68]: Request error on attempt 11: Bad Request 400. Sleeping for 1.62 seconds until next attempt
2024-07-04 04:15:29 DEBUG Process-1[utils:68]: Request error on attempt 12: Forbidden 403. Sleeping for 1.77 seconds until next attempt
2024-07-04 04:15:32 DEBUG Process-1[utils:68]: Request error on attempt 13: Bad Request 400. Sleeping for 1.44 seconds until next attempt
2024-07-04 04:15:35 DEBUG Process-1[utils:68]: Request error on attempt 14: Bad Request 400. Sleeping for 2.16 seconds until next attempt
2024-07-04 04:15:38 DEBUG Process-1[utils:68]: Request error on attempt 15: Forbidden 403. Sleeping for 1.28 seconds until next attempt
2024-07-04 04:15:41 DEBUG Process-1[utils:68]: Request error on attempt 16: Bad Request 400. Sleeping for 1.15 seconds until next attempt
2024-07-04 04:15:43 DEBUG Process-1[utils:68]: Request error on attempt 17: Forbidden 403. Sleeping for 2.23 seconds until next attempt
2024-07-04 04:15:46 DEBUG Process-1[utils:68]: Request error on attempt 18: Forbidden 403. Sleeping for 1.84 seconds until next attempt
2024-07-04 04:15:49 DEBUG Process-1[utils:68]: Request error on attempt 19: Forbidden 403. Sleeping for 2.48 seconds until next attempt
2024-07-04 04:15:53 DEBUG Process-1[utils:68]: Request error on attempt 20: Forbidden 403. Sleeping for 1.67 seconds until next attempt
2024-07-04 04:15:55 DEBUG Process-1[utils:74]: Failed to make request after 20 attempts: Forbidden 403
UPDATE: the login method DOES seem to work for the broken one.
Reservation one: login works, confirmation doesn't Reservation two: confirmation works, login doesn't
@dmytrokoren, do you think adding a random delay before clicking the first link (js_click after open) will help lower login detection errors? I unfortunately can't reproduce this (and not sure if you can either), so I can't test this.
If anyone else is running into this issue and wants to try the above suggestion, you can add the following on line 152 of lib/webdriver.py
. Make sure you are on the latest develop commit:
self._take_debug_screenshot(driver, "after_page_load.png")
+ time.sleep(random_sleep_duration(3, 8))
driver.js_click("(//div[@data-qa='placement-link'])[2]")
Anyone try this image, see if it helps: docker pull dmytrokoren/auto-southwest-check-in:develop
Still getting a Too Many Requests error
on the latest version of develop
. Will try the docker image
Still getting a
Too Many Requests error
on the latest version ofdevelop
. Will try the docker image
It most likely due to your IP address. I had the same issue, I turned off my VPN and it started working. (this applied to running locally or docker).
I just had a successful check in - Position A39
I just had a successful check in - Position A39
Have you had any successful logins? I haven't been able to login successfully for the past 10 commits on develop.
I just had a successful check in - Position A39
Have you had any successful logins? I haven't been able to login successfully for the past 10 commits on develop.
I just had a successful check-in this morning from development. A28. Using dev commit from about 5 days ago. I only use confirmations, no log ins.
I just had a successful check in - Position A39
Have you had any successful logins? I haven't been able to login successfully for the past 10 commits on develop.
I have upcoming flights and haven't had any login issues with the latest develop however worth noting I updated my Dockerfile to use FROM python:3.13-rc-alpine3.20. I can't say specifically why but after I did I stopped having login problems.
Version
v7.5 (develop branch)
Browser Version
N/A
Description
With the merge of #274 on the
develop
branch, 403 and 429 errors are being handled much better (or not even seen). I want to consolidate the #201 and #230 threads into one. Using the thread below, people can report if they are or aren't seeing these errors as well as the environment they're using (Docker, laptop, server, etc.) and how many accounts/reservations are being monitored.To Reproduce
--verbose
flag or the log files which will have more information on any failed attempts)Expected Behavior
It is not expected that you never see 403 or 429 errors again. However, with the recent changes you should still eventually have successful attempts at logging in, scheduling check ins, fare checking, and checking in. The goal is to have no attempts too many times to the point they are not retried (the corresponding log message:
Failed to make request after ... attempts: ...
)Relevant logs and program output
No response
Additional context
For the most part, only logs like the following are helpful.
Request error on attempt ... Sleeping for 1.98 seconds until next attempt
Pasting all logs are fine, but please use a collapsed section in order to not clutter the main thread.
To get the latest changes, you can either use Docker or the
develop
branch locally.Docker:
docker pull jdholtz/auto-southwest-check-in:develop
Local:git pull && git checkout develop