- Subscribe to RSS Feed
- Mark Post as New
- Mark Post as Read
- Float this Post for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
I've been a Chrome-only user for decade-plus. A month ago, multiple issues, just with Southwest's website popped up and have not gone away. I've cleaned cookies, reinstalled Chrome, etc. Everything works perfectly in Microsoft Edge.
Just trying to "Log In" with my RR number I get "We are currently unable to complete your request. Please try again later."
The Community (this forum) I got "494 Error The request could not be satisfied"
Trying to search flights I get "Sorry, we found some errors.... Error code 000999999
Incident Identifier: 7980ce3b-221b-4ec8-aa1c-9e7701fd7a16
Every other website in Chrome I have no issues with ... every SWA action in Edge works ... the issue hasn't resolved itself in a month and I'm stuck. Help? Thank you!
Solved! Go to Solution.
Re: Multiple Chrome issues, Microsoft Edge is fine
Re: Multiple Chrome issues, Microsoft Edge is fine
12-06-2023 10:21 AM - edited 12-06-2023 10:28 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
I have this problem with one of my computers. It is caused by my anti virus interacting with Chrome.
I can use one of the alternate southwest logons, which redirect to southwest.com and Chrome works fine.
iflyswa.com
setlovefree.com
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
Thank you for the Reply ... let me try that ...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
@jspartners wrote:
Thank you for the Reply ... let me try that ...
drum roll ... and what happened?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
That individual was right that now I go to SWA using another one of the URLs ... setlovefree ... and that works ... so I can use Chrome again!!! super weird, but it works!