Encountered Too Many Requests Error #319
Comments
|
Try the develop branch |
|
Getting the same errors, even on the dev branch. SImilar setup to the OP, standalone windows PC running 8.1 and now 8.1 dev. |
|
I was able to successfully check in today using the |
|
still unresolved for me. tried fresh installs of both prod and dev branches over the weekend and again this morning.
|
|
Over the weekend one of the two accounts logged in one time, but not the other and since then it's been back to both failing. |
|
I'm currently seeing this error on dev and master |
|
docker pull dmytrokoren/auto-southwest-check-in:develop this one is working fine for me over 2 months. I have scheduled 1 account and fare check, been running 3 days without issue. |
Version
v8.1
Browser Version
130.0.6723.92
Description
Updated to v8.1, running locally on windows pc. I have a config monitoring 2 accounts, I am getting this at every run for each account. Help?
2024-11-10 11:59:34 DEBUG MainProcess[log:24]: Initialized the application
2024-11-10 11:59:34 DEBUG MainProcess[main:113]: Auto-Southwest Check-In v8.1
2024-11-10 11:59:34 DEBUG MainProcess[main:71]: Called with 0 arguments
2024-11-10 11:59:34 DEBUG MainProcess[config:143]: Initializing configuration file
2024-11-10 11:59:34 DEBUG MainProcess[config:172]: Reading the configuration file
2024-11-10 11:59:34 DEBUG MainProcess[config:185]: Reading configuration from environment variables
2024-11-10 11:59:34 DEBUG MainProcess[config:73]: Setting check fares to <CheckFaresOption.SAME_FLIGHT: 'same_flight'>
2024-11-10 11:59:34 DEBUG MainProcess[config:81]: A Healthchecks URL has been provided
2024-11-10 11:59:34 DEBUG MainProcess[config:85]: Setting retrieval interval to 4 hours
2024-11-10 11:59:34 DEBUG MainProcess[config:120]: Setting notification level to <NotificationLevel.NOTICE: 1>
2024-11-10 11:59:34 DEBUG MainProcess[config:155]: Creating configurations for 3 accounts
2024-11-10 11:59:34 DEBUG MainProcess[config:133]: Using 1 notification services
2024-11-10 11:59:34 DEBUG MainProcess[config:133]: Using 1 notification services
2024-11-10 11:59:34 DEBUG MainProcess[config:133]: Using 1 notification services
2024-11-10 11:59:34 INFO MainProcess[main:97]: Monitoring 3 accounts and 0 reservations
2024-11-10 11:59:35 DEBUG Process-3[reservation_monitor:65]: Acquiring lock...
2024-11-10 11:59:35 DEBUG Process-1[reservation_monitor:67]: Lock acquired
2024-11-10 11:59:35 DEBUG Process-1[reservation_monitor:205]: Retrieving reservations for account
2024-11-10 11:59:35 DEBUG Process-1[webdriver:130]: Starting webdriver for current session
2024-11-10 11:59:44 DEBUG Process-1[webdriver:152]: Using browser version: 130.0.6723.92
2024-11-10 11:59:44 DEBUG Process-1[webdriver:156]: Loading Southwest home page (this may take a moment)
2024-11-10 11:59:48 DEBUG Process-1[webdriver:104]: Logging into account to get a list of reservations and valid headers
2024-11-10 11:59:53 DEBUG Process-1[webdriver:187]: Waiting for headers_set to be set (timeout: 180 seconds)
2024-11-10 11:59:53 DEBUG Process-1[webdriver:201]: headers_set set successfully
2024-11-10 11:59:54 DEBUG Process-1[webdriver:187]: Waiting for login_request_id to be set (timeout: 180 seconds)
2024-11-10 11:59:54 DEBUG Process-1[webdriver:179]: Login response has been received
2024-11-10 11:59:55 DEBUG Process-1[webdriver:201]: login_request_id set successfully
2024-11-10 11:59:57 DEBUG Process-1[webdriver:257]: Logging in failed for an unknown reason
2024-11-10 11:59:57 DEBUG Process-1[reservation_monitor:220]: Encountered a Too Many Requests error while logging in. Skipping reservation retrieval
2024-11-10 12:00:00 DEBUG Process-1[reservation_monitor:78]: Lock released
2024-11-10 12:00:00 DEBUG Process-2[reservation_monitor:67]: Lock acquired
To Reproduce
Run the script with 3 accounts being monitored.
Expected Behavior
No response
Relevant logs and program output
Additional context
No response
The text was updated successfully, but these errors were encountered: