SWA URL issue?
djre4orm opened this issue · 5 comments
ERROR:
/var/lib/gems/2.7.0/gems/json-2.3.1/lib/json/common.rb:263:in parse': 784: unexpected token at '<HTML><HEAD> (JSON::ParserError)
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>
You don't have permission to access "http://mobile.southwest.com/api/mobile-air-booking/v1/mobile-air-booking/page/view-reservation/?" on this server.<P>
Reference #18.ce6533b8.1644344262.10357553
</BODY>
</HTML>
Looks like common.rb is having issues accessing: https://mobile.southwest.com/api/mobile-air-booking/v1/mobile-air-booking/page/view-reservation/
I have tried from two different PCs on my network & even tried over cellular data with the same 403.
FYI, I added a new flight early yesterday, and successfully then checked in to four different flights throughout the day yesterday. Zero problems for me.
Update: All return flights worked as well. Added some friends too. 12 successful check-ins in the past week.
unfortunately, that error is hard to tell what's going on. the fact that you're getting an access denied error trying to hit the mobile API makes me think there's something wrong with the headers. did you install southwest-headers according to the instructions in that repo?
unfortunately, that error is hard to tell what's going on. the fact that you're getting an access denied error trying to hit the mobile API makes me think there's something wrong with the headers. did you install southwest-headers according to the instructions in that repo?
Thanks for the reply!
Yep sure did, the cron job was setup, still working, and creates southwest_headers.json. Latest one was this morning. I created .autoluv.env in my user dir and autoluv sees it. If I rename it, I get the standard "create headers" error message.
The headers look correct, maybe missing the a0 though?
{
"content-type": "application/json",
"x-user-experience-id": "560fd79c-e0c6-493f-b12c-984669fcc926",
"ee30zvqlwf-z": "q",
"ee30zvqlwf-b": "6soy1y",
"ee30zvqlwf-d": "ABaChIjBDKGNgUGAQZIQhISi0eIApJmBDgDwDnGxVC3MhAAAAABztSzTAJ9PZQONxtm6d23uAbZaiSk",
"ee30zvqlwf-c": "AAD0sQZ_AQAAO43RVD_UT5Jsbf2cwFeakP5roPUa3LHHGu8MlPAOcbFULcyE",
"ee30zvqlwf-f": "Ay4IsgZ_AQAAJpw9vURz6IDQ-X5snxN1XdUGOecDMsKAQESp5Q1a_yPx5InjAWDxrRGuci2nwH8AAOfvAAAAAA==",
"x-channel-id": "MWEB",
"ee30zvqlwf-a": "5ulPi32Znm4sNqgwHfJg <cut because length>
"x-api-key": "l7xx44e0282659f14664b831eeba67b38a6e"
}
I did a test check-in this morning and it worked.
I tested with a REAL check-in and it worked fine too. Scheduled in AT.
I have always found that I need to sudo or sudo su before using the autoluv Ruby. Have you tried that?
I think I got to the bottom of it. Seems if you run "autoluv schedule" without any further information, it results in a 403. I could have sworn I filled out the name & confirmation when trying to setup my last check in. Either way, I might have been sent down my own self-inflicted rabbit hole of troubleshooting. Tried it with a new flight and it schedule it as expected.
Scheduling flight departing BWI at 06:40 on 2022-03-29.
warning: commands will be executed using /bin/sh
job 10 at Mon Mar 28 06:40:00 2022
Scheduling flight departing PHX at 18:05 on 2022-04-02.
warning: commands will be executed using /bin/sh
job 11 at Fri Apr 1 20:05:00 2022
Closing this for now, thank you for all the eyes. Maybe a good use case for argument checking for dumb dumbs like me, haha