403 and 429 Errors Thread

[jdholtz]

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

1. Run either the Docker image or the local Python installation
2. See if any requests fail (using either the --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

[natecodes]

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)

LOG

```2024-07-01 12:12:44 DEBUG MainProcess[log:24]: Initialized the application 2024-07-01 12:12:44 DEBUG MainProcess[main:113]: Auto-Southwest Check-In v7.5 2024-07-01 12:12:44 DEBUG MainProcess[main:71]: Called with 0 arguments 2024-07-01 12:12:44 DEBUG MainProcess[config:132]: Initializing configuration file 2024-07-01 12:12:44 DEBUG MainProcess[config:161]: Reading the configuration file 2024-07-01 12:12:44 DEBUG MainProcess[config:174]: Reading configuration from environment variables 2024-07-01 12:12:44 DEBUG MainProcess[config:60]: Setting check fares to True 2024-07-01 12:12:44 DEBUG MainProcess[config:75]: Setting retrieval interval to 24 hours 2024-07-01 12:12:44 DEBUG MainProcess[config:109]: Setting notification level to 2024-07-01 12:12:44 DEBUG MainProcess[config:122]: Using 0 notification services 2024-07-01 12:12:44 DEBUG MainProcess[config:144]: Creating configurations for 1 accounts 2024-07-01 12:12:44 DEBUG MainProcess[config:151]: Creating configurations for 0 reservations 2024-07-01 12:12:44 INFO MainProcess[main:97]: Monitoring 1 account and 0 reservations 2024-07-01 12:12:44 DEBUG Process-1[reservation_monitor:168]: Acquiring lock... 2024-07-01 12:12:44 DEBUG Process-1[reservation_monitor:170]: Lock acquired 2024-07-01 12:12:44 DEBUG Process-1[reservation_monitor:192]: Retrieving reservations for account 2024-07-01 12:12:44 DEBUG Process-1[webdriver:126]: Starting webdriver for current session 2024-07-01 12:12:45 DEBUG Process-1[webdriver:143]: Using browser version: 126.0.6478.127 2024-07-01 12:12:45 DEBUG Process-1[webdriver:147]: Loading Southwest home page (this may take a moment) 2024-07-01 12:12:52 DEBUG Process-1[webdriver:100]: Logging into account to get a list of reservations and valid headers 2024-07-01 12:12:54 DEBUG Process-1[webdriver:177]: Waiting for headers_set to be set 2024-07-01 12:12:54 DEBUG Process-1[webdriver:181]: headers_set set successfully 2024-07-01 12:12:55 DEBUG Process-1[webdriver:177]: Waiting for login_request_id to be set 2024-07-01 12:12:55 DEBUG Process-1[webdriver:169]: Login response has been received 2024-07-01 12:12:56 DEBUG Process-1[webdriver:181]: login_request_id set successfully 2024-07-01 12:12:56 DEBUG Process-1[webdriver:237]: Logging in failed for an unknown reason 2024-07-01 12:12:56 WARNING Process-1[reservation_monitor:201]: Encountered a Too Many Requests error while logging in. Skipping reservation retrieval 2024-07-01 12:12:56 DEBUG Process-1[reservation_monitor:181]: Lock released 2024-07-01 12:12:56 DEBUG Process-1[reservation_monitor:130]: Sleeping for 86387 seconds ^C2024-07-01 12:12:58 INFO MainProcess[main:122]: Ctrl+C pressed. Stopping all check-ins

[jdholtz]

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.

[natecodes]

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

[mickgiles]

I am using the latest develop for several upcoming flights and I have noticed the following on startup scheduling the checkin...

1. Using Docker with the image jdholtz/auto-southwest-check-in I get 403 failures on both accounts and reservations
2. Using Docker building from the Dockerfile in develop I do not get any errors
3. Running the script on bare metal (Ubuntu) I get no errors

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 | }

[jdholtz]

@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)?

[jdholtz]

Macbook M1 no docker 1 account, ~30 reservations

@natecodes do the reservations also eventually run into 403s and/or 429s?

[natecodes]

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```

[jdholtz]

@natecodes you can try with just a confirmation number and name to skip logging in altogether.

[mickgiles]

@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)?

using this image most succeeded but 1 reservation failed with the following logs

Logs

auto-southwest | 2024-07-02 02:18:39 DEBUG Process-7[checkin_scheduler:79]: Retrieving reservation information auto-southwest | 2024-07-02 02:18:40 DEBUG Process-7[utils:68]: Request error on attempt 1: Bad Request 400. Sleeping for 2.87 seconds until next attempt auto-southwest | 2024-07-02 02:18:43 DEBUG Process-7[utils:68]: Request error on attempt 2: Bad Request 400. Sleeping for 2.41 seconds until next attempt auto-southwest | 2024-07-02 02:18:46 DEBUG Process-7[utils:68]: Request error on attempt 3: Forbidden 403. Sleeping for 1.53 seconds until next attempt auto-southwest | 2024-07-02 02:18:48 DEBUG Process-7[utils:68]: Request error on attempt 4: Bad Request 400. Sleeping for 2.96 seconds until next attempt auto-southwest | 2024-07-02 02:18:51 DEBUG Process-7[utils:68]: Request error on attempt 5: Bad Request 400. Sleeping for 1.91 seconds until next attempt auto-southwest | 2024-07-02 02:18:53 DEBUG Process-7[utils:68]: Request error on attempt 6: Bad Request 400. Sleeping for 2.95 seconds until next attempt auto-southwest | 2024-07-02 02:18:56 DEBUG Process-7[utils:68]: Request error on attempt 7: Bad Request 400. Sleeping for 2.56 seconds until next attempt auto-southwest | 2024-07-02 02:18:59 DEBUG Process-7[utils:68]: Request error on attempt 8: Forbidden 403. Sleeping for 2.50 seconds until next attempt auto-southwest | 2024-07-02 02:19:02 DEBUG Process-7[utils:68]: Request error on attempt 9: Bad Request 400. Sleeping for 2.64 seconds until next attempt auto-southwest | 2024-07-02 02:19:05 DEBUG Process-7[utils:68]: Request error on attempt 10: Forbidden 403. Sleeping for 2.30 seconds until next attempt auto-southwest | 2024-07-02 02:19:08 DEBUG Process-7[utils:68]: Request error on attempt 11: Bad Request 400. Sleeping for 1.20 seconds until next attempt auto-southwest | 2024-07-02 02:19:09 DEBUG Process-7[utils:68]: Request error on attempt 12: Bad Request 400. Sleeping for 2.45 seconds until next attempt auto-southwest | 2024-07-02 02:19:12 DEBUG Process-7[utils:68]: Request error on attempt 13: Forbidden 403. Sleeping for 1.99 seconds until next attempt auto-southwest | 2024-07-02 02:19:14 DEBUG Process-7[utils:68]: Request error on attempt 14: Bad Request 400. Sleeping for 1.05 seconds until next attempt auto-southwest | 2024-07-02 02:19:16 DEBUG Process-7[utils:68]: Request error on attempt 15: Bad Request 400. Sleeping for 2.38 seconds until next attempt auto-southwest | 2024-07-02 02:19:19 DEBUG Process-7[utils:68]: Request error on attempt 16: Bad Request 400. Sleeping for 1.42 seconds until next attempt auto-southwest | 2024-07-02 02:19:21 DEBUG Process-7[utils:68]: Request error on attempt 17: Bad Request 400. Sleeping for 1.86 seconds until next attempt auto-southwest | 2024-07-02 02:19:23 DEBUG Process-7[utils:68]: Request error on attempt 18: Bad Request 400. Sleeping for 1.72 seconds until next attempt auto-southwest | 2024-07-02 02:19:25 DEBUG Process-7[utils:68]: Request error on attempt 19: Bad Request 400. Sleeping for 1.64 seconds until next attempt auto-southwest | 2024-07-02 02:19:27 DEBUG Process-7[utils:68]: Request error on attempt 20: Bad Request 400. Sleeping for 1.79 seconds until next attempt auto-southwest | 2024-07-02 02:19:29 DEBUG Process-7[utils:74]: Failed to make request after 20 attempts: Bad Request 400 auto-southwest | 2024-07-02 02:19:29 DEBUG Process-7[utils:75]: Response body: {"code":400310456,"message":"Record Locator must have six characters","messageKey":"VALIDATION__AIR_RESERVATION__RECORD_LOCATOR__LENGTH","header":null,"httpStatusCode":"BAD_REQUEST","requestId":"no-exp-id:0.c417dd17.1719886767.5a4520fe:mweb","infoList":[{"key":"recordLocator","value":"Record Locator must have six characters"}]} auto-southwest | 2024-07-02 02:19:29 DEBUG Process-7[checkin_scheduler:85]: Failed to retrieve reservation info. Error: Bad Request 400. Exiting auto-southwest | 2024-07-02 02:19:29 DEBUG Process-7[notification_handler:80]: Sending failed reservation retrieval notification... auto-southwest | Failed to retrieve reservation for -u southwest.py with confirmation number python3. Reason: Bad Request 400. auto-southwest | Make sure the reservation information is correct and try again.

[natecodes]

@natecodes you can try with just a confirmation number and name to skip logging in altogether.

On develop

``` (southwest-venv) ➜ auto-southwest-check-in git:(develop) ✗ python3 southwest.py CONFCODE FIRST LAST --verbose 2024-07-01 19:22:15 DEBUG MainProcess[log:24]: Initialized the application 2024-07-01 19:22:15 DEBUG MainProcess[main:113]: Auto-Southwest Check-In v7.5 2024-07-01 19:22:15 DEBUG MainProcess[main:71]: Called with 3 arguments 2024-07-01 19:22:15 DEBUG MainProcess[config:132]: Initializing configuration file 2024-07-01 19:22:15 DEBUG MainProcess[config:161]: Reading the configuration file 2024-07-01 19:22:15 DEBUG MainProcess[config:174]: Reading configuration from environment variables 2024-07-01 19:22:15 DEBUG MainProcess[config:60]: Setting check fares to True 2024-07-01 19:22:15 DEBUG MainProcess[config:75]: Setting retrieval interval to 24 hours 2024-07-01 19:22:15 DEBUG MainProcess[config:109]: Setting notification level to 2024-07-01 19:22:15 DEBUG MainProcess[config:122]: Using 0 notification services 2024-07-01 19:22:15 DEBUG MainProcess[config:144]: Creating configurations for 1 accounts 2024-07-01 19:22:15 DEBUG MainProcess[config:151]: Creating configurations for 0 reservations 2024-07-01 19:22:15 DEBUG MainProcess[main:84]: Adding reservation through CLI arguments 2024-07-01 19:22:15 DEBUG MainProcess[config:151]: Creating configurations for 1 reservations 2024-07-01 19:22:15 INFO MainProcess[main:97]: Monitoring 1 account and 1 reservation 2024-07-01 19:22:15 DEBUG Process-1[reservation_monitor:168]: Acquiring lock... 2024-07-01 19:22:15 DEBUG Process-1[reservation_monitor:170]: Lock acquired 2024-07-01 19:22:15 DEBUG Process-1[reservation_monitor:192]: Retrieving reservations for account 2024-07-01 19:22:15 DEBUG Process-1[webdriver:126]: Starting webdriver for current session 2024-07-01 19:22:15 DEBUG Process-2[reservation_monitor:62]: Acquiring lock... 2024-07-01 19:22:16 DEBUG Process-1[webdriver:143]: Using browser version: 126.0.6478.127 2024-07-01 19:22:17 DEBUG Process-1[webdriver:147]: Loading Southwest home page (this may take a moment) 2024-07-01 19:22:22 DEBUG Process-1[webdriver:100]: Logging into account to get a list of reservations and valid headers 2024-07-01 19:22:26 DEBUG Process-1[webdriver:177]: Waiting for headers_set to be set 2024-07-01 19:22:26 DEBUG Process-1[webdriver:181]: headers_set set successfully 2024-07-01 19:22:26 DEBUG Process-1[webdriver:177]: Waiting for login_request_id to be set 2024-07-01 19:22:27 DEBUG Process-1[webdriver:169]: Login response has been received 2024-07-01 19:22:27 DEBUG Process-1[webdriver:181]: login_request_id set successfully 2024-07-01 19:22:27 DEBUG Process-1[webdriver:237]: Logging in failed for an unknown reason 2024-07-01 19:22:27 WARNING Process-1[reservation_monitor:201]: Encountered a Too Many Requests error while logging in. Skipping reservation retrieval 2024-07-01 19:22:27 DEBUG Process-1[reservation_monitor:181]: Lock released 2024-07-01 19:22:27 DEBUG Process-2[reservation_monitor:64]: Lock acquired 2024-07-01 19:22:27 DEBUG Process-2[checkin_scheduler:51]: Refreshing headers for current session 2024-07-01 19:22:27 DEBUG Process-2[webdriver:126]: Starting webdriver for current session 2024-07-01 19:22:27 DEBUG Process-1[reservation_monitor:130]: Sleeping for 86388 seconds 2024-07-01 19:22:28 DEBUG Process-2[webdriver:143]: Using browser version: 126.0.6478.127 2024-07-01 19:22:28 DEBUG Process-2[webdriver:147]: Loading Southwest home page (this may take a moment) 2024-07-01 19:22:33 DEBUG Process-2[webdriver:84]: Waiting for valid headers 2024-07-01 19:22:33 DEBUG Process-2[webdriver:177]: Waiting for headers_set to be set 2024-07-01 19:22:33 DEBUG Process-2[webdriver:181]: headers_set set successfully 2024-07-01 19:22:33 DEBUG Process-2[reservation_monitor:86]: Scheduling flight check-ins for 1 reservations 2024-07-01 19:22:33 DEBUG Process-2[checkin_scheduler:79]: Retrieving reservation information 2024-07-01 19:22:37 DEBUG Process-2[utils:50]: Successfully made request after 1 attempts 2024-07-01 19:22:37 DEBUG Process-2[checkin_scheduler:92]: Successfully retrieved reservation information 2024-07-01 19:22:37 DEBUG Process-2[checkin_scheduler:58]: 1 flights found under current reservation 2024-07-01 19:22:37 DEBUG Process-2[checkin_scheduler:44]: 1 total flights were found 2024-07-01 19:22:37 DEBUG Process-2[checkin_scheduler:110]: 1 new flights found 2024-07-01 19:22:37 DEBUG Process-2[checkin_scheduler:114]: Scheduling 1 flights for check-in 2024-07-01 19:22:37 DEBUG Process-2[checkin_handler:47]: Scheduling check-in for current flight 2024-07-01 19:22:37 DEBUG Process-2[notification_handler:71]: Sending new flights notification Successfully scheduled the following flights to check in for FIRST LAST: Flight from Long Beach to San Jose on 2024-07-02 1:00 PM PDT 2024-07-01 19:22:37 DEBUG Process-2[checkin_scheduler:126]: 1 flights are currently scheduled. Removing old flights 2024-07-01 19:22:37 DEBUG Process-2[checkin_scheduler:145]: Successfully removed old flights. 1 flights are now scheduled 2024-07-01 19:22:37 DEBUG Process-2[reservation_monitor:95]: Checking fares for 1 flights 2024-07-01 19:22:37 DEBUG Process-2[fare_checker:30]: Checking current price for flight 2024-07-01 19:22:37 DEBUG Process-2[fare_checker:88]: Retrieving reservation information 2024-07-01 19:22:37 DEBUG Process-2:1[checkin_handler:87]: Check-in time has passed. Going straight to check-in Checking in to flight from 'Long Beach' to 'San Jose' for FIRST LAST 2024-07-01 19:22:37 DEBUG Process-2:1[checkin_handler:155]: Attempting to check in 2024-07-01 19:22:37 DEBUG Process-2:1[checkin_handler:188]: Making GET request to check in 2024-07-01 19:22:38 DEBUG Process-2:1[utils:50]: Successfully made request after 1 attempts 2024-07-01 19:22:38 DEBUG Process-2:1[checkin_handler:194]: Making POST request to check in 2024-07-01 19:22:40 DEBUG Process-2:1[utils:50]: Successfully made request after 1 attempts 2024-07-01 19:22:40 DEBUG Process-2[utils:50]: Successfully made request after 1 attempts 2024-07-01 19:22:40 DEBUG Process-2:1[checkin_handler:165]: Successfully checked in after 1 attempts 2024-07-01 19:22:40 DEBUG Process-2:1[notification_handler:105]: Sending successful check-in notification... Successfully checked in to flight from 'Long Beach' to 'San Jose' for FIRST LAST! FIRST LAST got A55! 2024-07-01 19:22:40 DEBUG Process-2[fare_checker:103]: Retrieving search information for the current flight 2024-07-01 19:22:41 DEBUG Process-2[utils:50]: Successfully made request after 1 attempts 2024-07-01 19:22:41 DEBUG Process-2[fare_checker:82]: Retrieving matching flights 2024-07-01 19:22:45 DEBUG Process-2[utils:50]: Successfully made request after 1 attempts 2024-07-01 19:22:45 DEBUG Process-2[fare_checker:50]: Found 26 matching flights 2024-07-01 19:22:45 DEBUG Process-2[fare_checker:37]: Flight price change found for +214 USD 2024-07-01 19:22:45 DEBUG Process-2[reservation_monitor:82]: Lock released 2024-07-01 19:22:45 DEBUG Process-2[reservation_monitor:130]: Sleeping for 86370 seconds

[jdholtz]

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.

[jdholtz]

@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

[mickgiles]

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

Logs

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...

[natecodes]

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: @.***>

[natecodes]

So as of right now is the login functionality not supposed to work at all?

[jdholtz]

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.

[hildebrau]

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.

[astrostl]

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

[jdholtz]

@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]")

[natecodes]

Log

(southwest-venv) ➜ auto-southwest-check-in git:(develop) ✗ python3 southwest.py --verbose 2024-07-09 20:16:58 DEBUG MainProcess[log:24]: Initialized the application 2024-07-09 20:16:58 DEBUG MainProcess[main:113]: Auto-Southwest Check-In v7.5 2024-07-09 20:16:58 DEBUG MainProcess[main:71]: Called with 0 arguments 2024-07-09 20:16:58 DEBUG MainProcess[config:132]: Initializing configuration file 2024-07-09 20:16:58 DEBUG MainProcess[config:161]: Reading the configuration file 2024-07-09 20:16:58 DEBUG MainProcess[config:174]: Reading configuration from environment variables 2024-07-09 20:16:58 DEBUG MainProcess[config:60]: Setting check fares to True 2024-07-09 20:16:58 DEBUG MainProcess[config:75]: Setting retrieval interval to 24 hours 2024-07-09 20:16:58 DEBUG MainProcess[config:109]: Setting notification level to 2024-07-09 20:16:58 DEBUG MainProcess[config:122]: Using 0 notification services 2024-07-09 20:16:58 DEBUG MainProcess[config:144]: Creating configurations for 1 accounts 2024-07-09 20:16:58 DEBUG MainProcess[config:151]: Creating configurations for 0 reservations 2024-07-09 20:16:58 INFO MainProcess[main:97]: Monitoring 1 account and 0 reservations 2024-07-09 20:16:58 DEBUG Process-1[reservation_monitor:58]: Acquiring lock... 2024-07-09 20:16:58 DEBUG Process-1[reservation_monitor:60]: Lock acquired 2024-07-09 20:16:58 DEBUG Process-1[reservation_monitor:198]: Retrieving reservations for account 2024-07-09 20:16:58 DEBUG Process-1[webdriver:128]: Starting webdriver for current session 2024-07-09 20:16:59 DEBUG Process-1[webdriver:145]: Using browser version: 126.0.6478.127 2024-07-09 20:16:59 DEBUG Process-1[webdriver:149]: Loading Southwest home page (this may take a moment) 2024-07-09 20:17:03 DEBUG Process-1[webdriver:102]: Logging into account to get a list of reservations and valid headers Process Process-1: Traceback (most recent call last): File "/opt/homebrew/Cellar/python@3.9/3.9.18/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap self.run() File "/opt/homebrew/Cellar/python@3.9/3.9.18/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/Users/nathan/Desktop/auto-southwest-check-in/lib/reservation_monitor.py", line 44, in monitor self._monitor() File "/Users/nathan/Desktop/auto-southwest-check-in/lib/reservation_monitor.py", line 62, in _monitor should_exit = self._perform_check() File "/Users/nathan/Desktop/auto-southwest-check-in/lib/reservation_monitor.py", line 180, in _perform_check reservations, skip_scheduling = self._get_reservations() File "/Users/nathan/Desktop/auto-southwest-check-in/lib/reservation_monitor.py", line 202, in _get_reservations reservations = webdriver.get_reservations(self) File "/Users/nathan/Desktop/auto-southwest-check-in/lib/webdriver.py", line 108, in get_reservations driver.click(".login-button--box") File "/Users/nathan/Desktop/auto-southwest-check-in/southwest-venv/lib/python3.9/site-packages/seleniumbase/core/sb_driver.py", line 59, in click page_actions.click(self.driver, *args, **kwargs) File "/Users/nathan/Desktop/auto-southwest-check-in/southwest-venv/lib/python3.9/site-packages/seleniumbase/fixtures/page_actions.py", line 1510, in click element.click() File "/Users/nathan/Desktop/auto-southwest-check-in/southwest-venv/lib/python3.9/site-packages/selenium/webdriver/remote/webelement.py", line 94, in click self._execute(Command.CLICK_ELEMENT) File "/Users/nathan/Desktop/auto-southwest-check-in/southwest-venv/lib/python3.9/site-packages/selenium/webdriver/remote/webelement.py", line 395, in _execute return self._parent.execute(command, params) File "/Users/nathan/Desktop/auto-southwest-check-in/southwest-venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 347, in execute self.error_handler.check_response(response) File "/Users/nathan/Desktop/auto-southwest-check-in/southwest-venv/lib/python3.9/site-packages/selenium/webdriver/remote/errorhandler.py", line 229, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.ElementClickInterceptedException: Message: element click intercepted: Element ... is not clickable at point (336, 27). Other element would receive the click:

(Session info: chrome=126.0.6478.127) Stacktrace: 0 uc_driver 0x0000000100d5c0e8 uc_driver + 5169384 1 uc_driver 0x0000000100d53fba uc_driver + 5136314 2 uc_driver 0x00000001008d036c uc_driver + 402284 3 uc_driver 0x00000001009246b6 uc_driver + 747190 4 uc_driver 0x00000001009224e8 uc_driver + 738536 5 uc_driver 0x000000010091fef7 uc_driver + 728823 6 uc_driver 0x000000010091ed12 uc_driver + 724242 7 uc_driver 0x0000000100912562 uc_driver + 673122 8 uc_driver 0x0000000100940ab2 uc_driver + 862898 9 uc_driver 0x0000000100911ed8 uc_driver + 671448 10 uc_driver 0x0000000100940c6e uc_driver + 863342 11 uc_driver 0x000000010095ff57 uc_driver + 991063 12 uc_driver 0x0000000100940853 uc_driver + 862291 13 uc_driver 0x00000001009105c6 uc_driver + 665030 14 uc_driver 0x0000000100910e4e uc_driver + 667214 15 uc_driver 0x0000000100d1ed00 uc_driver + 4918528 16 uc_driver 0x0000000100d23cfd uc_driver + 4939005 17 uc_driver 0x0000000100d243d5 uc_driver + 4940757 18 uc_driver 0x0000000100cffde4 uc_driver + 4791780 19 uc_driver 0x0000000100d246c9 uc_driver + 4941513 20 uc_driver 0x0000000100cf15b4 uc_driver + 4732340 21 uc_driver 0x0000000100d44898 uc_driver + 5073048 22 uc_driver 0x0000000100d44a57 uc_driver + 5073495 23 uc_driver 0x0000000100d53b6e uc_driver + 5135214 24 libsystem_pthread.dylib 0x00007ff80745818b _pthread_start + 99 25 libsystem_pthread.dylib 0x00007ff807453ae3 thread_start + 15

[dmytrokoren]

Anyone try this image, see if it helps: docker pull dmytrokoren/auto-southwest-check-in:develop

[natecodes]

Still getting a Too Many Requests error on the latest version of develop. Will try the docker image

[dmytrokoren]

Still getting a Too Many Requests error on the latest version of develop. 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).

[dmytrokoren]

I just had a successful check in - Position A39

[natecodes]

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.

[crbarahona]

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.

[mickgiles]

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.

[dmytrokoren]

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.

This is interesting thanks @mickgiles

[dmytrokoren]

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.

@natecodes that was successful checking through login. I didn't have any issue with login - no 429. Maybe once it slips through (docker on Synology)

All I can think of is your IP address somehow SW doesn't like.

Try @mickgiles suggestion: Dockerfile to use FROM python:3.13-rc-alpine3.20

[dmytrokoren]

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.

@natecodes try docker pull dmytrokoren/auto-southwest-check-in:develop again. Hope it helps.

[mickgiles]

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.

@natecodes try docker pull dmytrokoren/auto-southwest-check-in:develop again. Hope it helps.

I just tried this image and got 403s logging in. I am also getting them with the newer alpine image.

[dmytrokoren]

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.

@natecodes try docker pull dmytrokoren/auto-southwest-check-in:develop again. Hope it helps.

I just tried this image and got 403s logging in. I am also getting them with the newer alpine image.

@mickgiles I've updated once again :develop tag can you try and see if you still get 429 on login?

[mickgiles]

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.

@natecodes try docker pull dmytrokoren/auto-southwest-check-in:develop again. Hope it helps.

I just tried this image and got 403s logging in. I am also getting them with the newer alpine image.

@mickgiles I've updated once again :develop tag can you try and see if you still get 429 on login?

I tried this image and was still getting a 403 (not 429). It retried the maximum times and then failed

[dmytrokoren]

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.

@natecodes try docker pull dmytrokoren/auto-southwest-check-in:develop again. Hope it helps.

I just tried this image and got 403s logging in. I am also getting them with the newer alpine image.

@mickgiles I've updated once again :develop tag can you try and see if you still get 429 on login?

I tried this image and was still getting a 403 (not 429). It retried the maximum times and then failed

Are you able to run from command line locally on that same machine? (using :develop tag)

after that can you give a try for " docker pull dmytrokoren/auto-southwest-check-in:dev-beta " ?

[mickgiles]

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.

@natecodes try docker pull dmytrokoren/auto-southwest-check-in:develop again. Hope it helps.

I just tried this image and got 403s logging in. I am also getting them with the newer alpine image.

@mickgiles I've updated once again :develop tag can you try and see if you still get 429 on login?

I tried this image and was still getting a 403 (not 429). It retried the maximum times and then failed

Are you able to run from command line locally on that same machine? (using :develop tag)

after that can you give a try for " docker pull dmytrokoren/auto-southwest-check-in:dev-beta " ?

I do run the script on the same machine (ubuntu) outside of docker and have never had the login issue except in docker running your new dev-beta image I get the following error

auto-southwest | 2024-07-17 22:37:14 DEBUG Process-3[webdriver:145]: Using browser version: 126.0.6478.126 auto-southwest | 2024-07-17 22:37:14 DEBUG Process-3[webdriver:149]: Loading Southwest home page (this may take a moment) auto-southwest | Process Process-3: auto-southwest | 2024-07-17 22:37:22 DEBUG Process-7[reservation_monitor:60]: Lock acquired auto-southwest | 2024-07-17 22:37:22 DEBUG Process-7[checkin_scheduler:48]: Refreshing headers for current session auto-southwest | 2024-07-17 22:37:22 DEBUG Process-7[webdriver:128]: Starting webdriver for current session auto-southwest | Traceback (most recent call last): auto-southwest | File "/usr/local/lib/python3.12/multiprocessing/process.py", line 314, in _bootstrap auto-southwest | self.run() auto-southwest | File "/usr/local/lib/python3.12/multiprocessing/process.py", line 108, in run auto-southwest | self._target(*self._args, *self._kwargs) auto-southwest | File "/app/lib/reservation_monitor.py", line 44, in monitor auto-southwest | self._monitor() auto-southwest | File "/app/lib/reservation_monitor.py", line 62, in _monitor auto-southwest | should_exit = self._check() auto-southwest | ^^^^^^^^^^^^^ auto-southwest | File "/app/lib/reservation_monitor.py", line 83, in _check auto-southwest | self.checkin_scheduler.refresh_headers() auto-southwest | File "/app/lib/checkin_scheduler.py", line 50, in refresh_headers auto-southwest | webdriver.set_headers() auto-southwest | File "/app/lib/webdriver.py", line 84, in set_headers auto-southwest | driver = self._get_driver() auto-southwest | ^^^^^^^^^^^^^^^^^^ auto-southwest | File "/app/lib/webdriver.py", line 153, in _get_driver auto-southwest | driver.click('img[alt="Check in banner"]') auto-southwest | File "/app/.local/lib/python3.12/site-packages/seleniumbase/core/sb_driver.py", line 59, in click auto-southwest | page_actions.click(self.driver, args, **kwargs) auto-southwest | File "/app/.local/lib/python3.12/site-packages/seleniumbase/fixtures/page_actions.py", line 1534, in click auto-southwest | element.click() auto-southwest | File "/app/.local/lib/python3.12/site-packages/selenium/webdriver/remote/webelement.py", line 94, in click auto-southwest | self._execute(Command.CLICK_ELEMENT) auto-southwest | File "/app/.local/lib/python3.12/site-packages/selenium/webdriver/remote/webelement.py", line 395, in _execute auto-southwest | return self._parent.execute(command, params) auto-southwest | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ auto-southwest | File "/app/.local/lib/python3.12/site-packages/selenium/webdriver/remote/webdriver.py", line 354, in execute auto-southwest | self.error_handler.check_response(response) auto-southwest | File "/app/.local/lib/python3.12/site-packages/selenium/webdriver/remote/errorhandler.py", line 229, in check_response auto-southwest | raise exception_class(message, screen, stacktrace) auto-southwest | selenium.common.exceptions.ElementClickInterceptedException: Message: element click intercepted: Element is not clickable at point (712, 846). Other element would receive the click:

...

auto-southwest | (Session info: chrome=126.0.6478.126)

[dmytrokoren]

@mickgiles can you try pull dev-beta again? See if there is any new update. I changed from click to js_click.

[mickgiles]

@mickgiles can you try pull dev-beta again? See if there is any new update. I changed from click to js_click.

js error is gone now but back to the 403's. it continues to work outside of docker on the same host

[dmytrokoren]

@mickgiles can you try pull dev-beta again? See if there is any new update. I changed from click to js_click.

js error is gone now but back to the 403's. it continues to work outside of docker on the same host

made some changes in :dev-beta - its working working locally and in docker. Let me know

[mickgiles]

@mickgiles can you try pull dev-beta again? See if there is any new update. I changed from click to js_click.

js error is gone now but back to the 403's. it continues to work outside of docker on the same host

made some changes in :dev-beta - its working working locally and in docker. Let me know

sorry mate, still 403s

[dmytrokoren]

@jdholtz - Great news! I've successfully set up the virtual display in Docker. We no longer need to use "is_mobile" or manipulate the "user-agent". Everything is working good in both locally and within Docker, and lot less 429 and 403 errors.

Here's a snapshot of the Docker interface (no more popups). While it doesn't show much, you'll notice a clean UI with no extra workarounds required. The 429 and 403 issues are resolved.

I'll push these changes shortly. Please test them on your machines and let me know if you encounter any issues.

[dmytrokoren]

Test away! - docker pull dmytrokoren/auto-southwest-check-in:dev-beta

[mickgiles]

Test away! - docker pull dmytrokoren/auto-southwest-check-in:dev-beta

I've pulled the latest image and am still getting 403s at login :(

[dmytrokoren]

Test away! - docker pull dmytrokoren/auto-southwest-check-in:dev-beta

I've pulled the latest image and am still getting 403s at login :(

Pull again. Pls

[mickgiles]

Test away! - docker pull dmytrokoren/auto-southwest-check-in:dev-beta

I've pulled the latest image and am still getting 403s at login :(

Pull again. Pls

Now I get... auto-southwest | Notice: Encountered a Too Many Requests error while logging in for . Skipping reservation retrieval until next interval

[dmytrokoren]

Test away! - docker pull dmytrokoren/auto-southwest-check-in:dev-beta

I've pulled the latest image and am still getting 403s at login :(

Pull again. Pls

Now I get...

auto-southwest | Notice: Encountered a Too Many Requests error while logging in for . Skipping reservation retrieval until next interval

You are running this in Ubuntu docker?

[mickgiles]

Test away! - docker pull dmytrokoren/auto-southwest-check-in:dev-beta

I've pulled the latest image and am still getting 403s at login :(

Pull again. Pls

Now I get... auto-southwest | Notice: Encountered a Too Many Requests error while logging in for . Skipping reservation retrieval until next interval

You are running this in Ubuntu docker?

correct, ubuntu docker ok, I ran it a few times and am getting the 403 still, and when I ran it outside of docker I got the same too many reqests error so that maybe a red herring. looks like the 403 is still consistent in docker

[dmytrokoren]

Test away! - docker pull dmytrokoren/auto-southwest-check-in:dev-beta

I've pulled the latest image and am still getting 403s at login :(

Pull again. Pls

Now I get...

auto-southwest | Notice: Encountered a Too Many Requests error while logging in for . Skipping reservation retrieval until next interval

You are running this in Ubuntu docker?

correct, ubuntu docker

ok, I ran it a few times and am getting the 403 still, and when I ran it outside of docker I got the same too many reqests error so that maybe a red herring.

looks like the 403 is still consistent in docker

Can you confirm if your machine is not on VPN? Do you use pfsense?

[dmytrokoren]

@mickgiles pls pull again same image. I've tested on docker Mac, windows and Linux (Synology)

4 accounts, only 1 got too many requests the rest success

[mickgiles]

Test away! - docker pull dmytrokoren/auto-southwest-check-in:dev-beta

I've pulled the latest image and am still getting 403s at login :(

Pull again. Pls

Now I get...

auto-southwest | Notice: Encountered a Too Many Requests error while logging in for . Skipping reservation retrieval until next interval

You are running this in Ubuntu docker?

correct, ubuntu docker ok, I ran it a few times and am getting the 403 still, and when I ran it outside of docker I got the same too many reqests error so that maybe a red herring. looks like the 403 is still consistent in docker

Can you confirm if your machine is not on VPN? Do you use pfsense?

definitely not on a vpn and no pfsense as a sanity test I just tried on a macos docker on the same network egress and got the same 403

[mickgiles]

@mickgiles pls pull again same image. I've tested on docker Mac, windows and Linux (Synology)

4 accounts, only 1 got too many requests the rest success

latest image I am getting the below error but just to confirm, do any of your test accounts have scheduled flights? from the logging it appears that it may be logging in successfully but getting the 403 on a later action after being logged in. That may be the missing piece here...?

this error below is new

auto-southwest | selenium.common.exceptions.ElementClickInterceptedException: Message: element click intercepted: Element is not clickable at point (632, 565). Other element would receive the click: