-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
Error. when checking in #13
Comments
assuming you have a check-in available now, can you do me a favor and replace your southwest headers file with this:
and manually check-in using:
let me know if that works. |
I'm still getting "Error." There is a slight possibility that it is on my end. I had recently switched where I am hosting the script. Can I dm you with the info for you to try on your end? |
@Bryan792 sure, send me confirmation number and name here: https://www.alextran.org/contact/ |
thanks for sending me your confirmation number. i was able to check in without any issue. knowing you switched hosts, i would double and triple check you installed both autoluv and the southwest headers repos correctly. particularly with the southwest-headers, there are a lot of little steps that are critical. |
ok, glad to know that it was on my end. It was a direct clone of my previous setup, and it still didn't work even with the headers you sent me. I'll try playing with it. Thanks |
I think I found the issue. I'm getting: 429 Too Many Requests I'm not sure why it originally didn't work though. Hopefully, it will resolve itself |
hmm, yeah, there's something else going on. you shouldn't get a 429 error if everything is setup correctly. i had it work on two check-ins yesterday, so i think something is still off with your setup. the 429 error is something auto check-in apps were getting last summer that prompted the need for me to create the southwest-headers repo. if you're getting it, that tells me the southwest headers file isn't right. for way more context than you probably need, read here: |
ya something is weird. Is it possible my machine has been detected and blocked? I was able to copy the exact same header file to another machine and get it to work. I was also using that previous setup and was lead here when it started to fail. |
That definitely used to happen on a Heroku based setup I used to use. We ended up adding a proxy module to get around it. |
I'm also having issues getting the automated check in to succeed. I have a flight at 6AM tomorrow and the initial check-in failed with the 429 errors. I was able to create a new file by pulling the headers manually from the website and then automated check-in succeeded, but of course that won't work for my return flight. The only main difference I can spot between the generated headers and my manually-captured headers is the absence of a -a0 entry in the generated headers. Removing the -a0 entry from my manually captured headers also results in a 429 error, which correlates. Should I be seeing a -a0 header in the chromium output? Has something changed to require that header now? Note: I have edited the chromium exe to replace _cdc with _jld. |
so there's definitely something going on. i've now had my last two check-ins fail with the 429 error. @Steve-Super looking at manual headers just now, i don't see any differences in what southwest-headers produced. do you mind sharing the output of your manually captured headers and the ones automatically generated? |
@Steve-Super nm, you might be on to something. i just recaptured some manual headers and see the a0 key now. i had some regex that wasn't matching that key, however, i noticed the headers captured by chromedriver don't even have it. so even though i fixed the regex, there's no a0 header to save to the file. so need to do some more troubleshooting to see why chromedriver isn't capturing the a0 header. i hope southwest hasn't discovered a way to detect these scripts. 🤞🏻 |
I had 2 check-ins fail today. Can someone share where they are seeing the log files? |
While not nearly as fun, you can always send a text to +19493292899 to get automatic checkins. Seems to work well, they have a free and VIP version. Dude seems super responsive. |
after digging in some more, i think southwest has done a couple things:
for the first point, i used to use dummy data and got headers that worked for automated check-in. now that doesn't work anymore, however, using a valid confirmation number and manually grabbing the headers does. for number two, i know manually grabbing the headers works. however, when i try to automate grabbing the headers via chromedriver using the same valid confirmation number, it fails. trying to figure out what southwest is doing to detect chromedriver is going to be difficult. so right now my plan is to see how long valid southwest headers work before having to get updated ones. the interim solution for people wanting this script to still work will probably be to manually pull headers when your confirmation number is within the 24 hour window and use those (making sure you disable any cronjobs beforehand) until they expire. @Steve-Super looks like the a0 header isn't always present. in my testing, i only see it occasionally. and i have a working headers now that doesn't have it. |
@flyize has that worked for you recently? curious is they're running into the same problem i am or if they've found a solution around it. is there a website for that service? can only see reddit/forum posts referencing that number. (while it seems to work for people, i'd be vary of providing flight data to an unknown person. rapid rewards numbers are tied to it, family member names, etc.) |
Yes. I used it today and it worked perfectly. I found The author at the Reddit link below. I replied to him. Thanking him for it, and he already sent me a PM. He is definitely active. https://www.reddit.com/r/SouthwestAirlines/comments/tcioo4/psa_check_in_an_hour_early_today_bc_of_dst/&ved=2ahUKEwj15Lak9sL5AhUWk4kEHfZKDkIQFnoECAkQAQ&usg=AOvVaw0LEnBLcXXjTlmPGHTzI1eI |
Not sure if it helps at all, but on my check in yesterday with the text method, I got this text message reply, but it still worked. I'm not sure if it provides any info on how they might be interfacing with Southwest. |
Could I just manually add my confirmation code in the southwest-headers.py file and then leave the cronjob on? Would this lead to broken headers files until the confirmation code is valid and then work as intended for checkin day? Or am I mistaken? |
@Imisrael based on my testing, even a valid confirmation number isn't producing valid headers. i think southwest is somehow able to detect the script and gives invalid headers. |
@byalextran Ah, I see, I totally misunderstood the issue. So any and all auto-scrapped headers are borked. Can I ask you how to manually generate the headers json file? Do I just try to follow the sequence followed in the southwest-headers.py file in my own browser and download some json file 24 hours before checkin time? thanks again! |
I'm not sure if it just stopped working for all auto-scraped headers. I was able to get it to work on a different host a few weeks ago. |
@Bryan792 veeeeery interesting. but still using the southwest-headers code to pull the headers on the new host? what host did it stop working on? i won't ask which host you're on now to protect you being able to use it as long as possible. ;) |
I switched from my vps to my home pc, and ya it was using southwest-headers. |
@Bryan792 that's a huge clue. thanks for sharing. that would align with what someone else shared above saying they were blocked on heroku but got around it with a proxy. so it may not be an issue with the code but more with what server you're running it on. will need to do more experimenting when i have time. if someone can, maybe try proxying your requests as well on the same server that has been failing and see if that works. |
I'm the one that brought up the heroku/proxy issue. I believe this is the app I was using at the time. |
@mkitchingh how long ago was that where you had to proxy it? are you able to try proxying with my southwest-headers code? as far as logging, i know my currently logging isn't great. however, even with better logging the codes/info given to me by southwest on an error are ambiguous and unhelpful. so while i could improve the logging, it would just improve your ability to see an unhelpful error. 😅 |
also, i'm curious what servers people are using that are now failing? i'm on digitalocean. |
It was a heroku plugin, so I don't know how that would translate to other services. I'm using a Ubuntu instance at my house over Xfinity. |
sorry i've been a bit MIA on this lately. i was using a workaround where i manually copied headers from chrome, so a long-term fix wasn't high on my priority list. but i got inspired today and did some troubleshooting. i think i might have a working solution after switching to undetected-chromedriver. i think my original solution using a slightly modified version of chromedriver is being detected by southwest. the undetected version seems to do just that ... go undetected. who would've thought!? testing it now on a couple flights with check-ins on tuesday and wednesday. will report back then. |
happy to report i think things are working again! had two successful check-ins over the last couple days. i just pushed updated code. please follow the instructions here for updating: https://github.com/byalextran/southwest-headers#updating-southwest-headers also, it's worth upgrading chrome to the latest version (v108) since that's the version i tested with (and noticed it fails with v96). once i confirm things are working again for people, i'll close this issue. |
I've been using this for months without error, until today, I had multiple flights fail with a generic "Error." message. Is there a way for me to log to try and debug the error?
The text was updated successfully, but these errors were encountered: