Develop branch: No element present exception during login #279
Comments
jdholtz
changed the title
|
Could you run the script with the |
|
I just checked, the locator is valid. It's just that SW page took more than 7 seconds to load. We need to increase the wait time to 14 seconds - IMO |
Good point. @natecodes could you make the following edit in - driver.js_click("(//div[@data-qa='placement-link'])[2]")
+ driver.js_click("(//div[@data-qa='placement-link'])[2]", timeout=15)Also, a picture of |
|
Ohey, I came here to post the same error message. Glad I searched first. Tried adding the 15 second timeout, still got the error. Increased to 30, and that seemed to do the trick for the first account I attempted to log into (I have 5), but got the error twice and did not get "successful schedules" for 2/5 of the accounts. Retrying with |
|
Ok this time around, I got:
Then another Element not present after 30 seconds for the 4th and 5th accounts. :-{ |
|
Just to add Southwest website is extremely slow right now. |
|
Sorry am out of town at the moment, can hop on this when I'm back. |
Log(southwest-venv) ➜ auto-southwest-check-in git:(develop) ✗ python3 southwest.py --verbose 2024-07-09 20:16:58 DEBUG Process-1[reservation_monitor:58]: Acquiring lock... (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 |
I got the fix for this. I'll push it and let you know |
|
@natecodes @darryllee try this: docker pull dmytrokoren/auto-southwest-check-in:develop |
This may be the same popup in #226, which means that you're being detected as a bot right away. I removed the workaround for this in 753b5b9 after #274 as users shouldn't be getting detected. Even by clicking the popup to remove it, you'd still hit a Too Many Requests error, so it doesn't matter much (although, it can be added back). |
This is correct. I tried on windows machine via docker and I'm getting 429 error on login. |
I'll correct my comment. The interfering popup is no longer coming but I was running into 429 error after login. The issue was that my VPN was turned on and I was not connected to my residential IP. SW is strict on which IP you use, all VPN IP's are flagged since they using cloud flare most likely. |
|
Could anyone who is running into this issue try dmytrokoren's changes using the image |
Using dmytrokoren's latest develop image, I was able to login to my accounts in my config file, but still getting 403's. I'm not getting any element errors anymore. logs2024-07-15 03:57:34 DEBUG MainProcess[log:24]: Initialized the application 2024-07-15 03:57:34 DEBUG MainProcess[main:113]: Auto-Southwest Check-In v7.5 2024-07-15 03:57:34 DEBUG MainProcess[main:71]: Called with 1 arguments 2024-07-15 03:57:34 DEBUG MainProcess[config:132]: Initializing configuration file 2024-07-15 03:57:34 DEBUG MainProcess[config:161]: Reading the configuration file 2024-07-15 03:57:34 DEBUG MainProcess[config:174]: Reading configuration from environment variables 2024-07-15 03:57:34 DEBUG MainProcess[config:60]: Setting check fares to True 2024-07-15 03:57:34 DEBUG MainProcess[config:75]: Setting retrieval interval to 24 hours 2024-07-15 03:57:34 DEBUG MainProcess[config:109]: Setting notification level to 2024-07-15 03:57:34 DEBUG MainProcess[config:122]: Using 1 notification services 2024-07-15 03:57:34 DEBUG MainProcess[config:144]: Creating configurations for 7 accounts 2024-07-15 03:57:34 DEBUG MainProcess[config:151]: Creating configurations for 0 reservations 2024-07-15 03:57:34 INFO MainProcess[main:97]: Monitoring 7 accounts and 0 reservations2024-07-15 03:57:34 DEBUG Process-2[reservation_monitor:58]: Acquiring lock... |
|
@jwin3 try updated docker pull dmytrokoren/auto-southwest-check-in:develop again. |
Thanks for testing @jwin3, I'll merge that fix soon. Could anyone send the screenshot |
|
Updates are still being made to help avoid 403/429 errors. I want to at least get this issue fixed before releasing v8.0. |
|
Can we use browseless? It seems like settings ws://192.168.1.200:3200/ in variable path AUTO_SOUTHWEST_CHECK_IN_BROWSER_PATH gives an error. |
Could you expand on what you mean about using browseless a bit more? The browser path should contain the path to the location of your browser (e.g. |
Ah okay. I thought there was support for WS protocol with the AUTO_SOUTHWEST_CHECK_IN_BROWSER_PATH tag. Using Browseless might resolve: #277 https://forums.unraid.net/topic/160453-support-template-masterwishxbrowserless-v2/ <- Setup using docker I use it for changedetection.io. |
|
Ah, there’s no support for the WS protocol right now. Right now, the browser path is just passed straight into SeleniumBase’s driver. SeleniumBase does have support for that, but through the |
Selenium does not have a stealth mode. https://www.browserless.io/blog/stealth-mode Maybe with this plugin. https://www.npmjs.com/package/puppeteer-extra-plugin-stealth. Implementing a web socket protocol support might be easier in the long term. |
Puppeteer is in JavaScript, but this script is in Python so unfortunately I don’t think that integration will be possible until Browserless supports stealth mode. |
Also it's not free!
|
|
I was having issues with this line timing out: Looking on the selenium base documentation, I couldn't find a good description on the differences between the two methods. But I asked Gemini and it mentioned: click
js_click
Would |
It is free: https://ghcr.io/browserless/chromium |
Yes click is the better option. Will be updated. |
|
Hey @natecodes and @darryllee, could you guys try the following change (as suggested by @aaron-pham) and see if you are still running into the same issue? The change should be on line 152 of self._take_debug_screenshot(driver, "after_page_load.png")
- driver.js_click("(//div[@data-qa='placement-link'])[2]")
+ driver.click("(//div[@data-qa='placement-link'])[2]")
return driver |
|
I changed |
|
Hi - I haven't seen the issue in a while, but I'm also not trying to check fares for 5 different accounts, as I was doing previously. (I removed the accounts to prioritize and make sure our check-ins were successful.) After a few flights next week I can add all 5 accounts back and see if the problem recurs. |
Version
7.5
Browser Version
126.0.6478.127
Description
Refer to logs
To Reproduce
Run script as normal
Expected Behavior
No response
Relevant logs and program output
Additional context
No response
The text was updated successfully, but these errors were encountered: