Award Booking Error - Access Denied!

serfty

Veteran Member
Moderator
Joined
Nov 16, 2004
Posts
46,609
Qantas
Platinum
Virgin
Platinum
I have been trying to look at a maulti city award booking and am getting the following error:

Access Denied​

You don't have permission to access "http://book.qantas.com/pl/QFAward/wds/tripflow.redirect?" on this server.
Reference #18.6cae4d68.1637708569.2c0b011b
This has been happening for at least the last 12 hours on multiple desktops.

Is anyone having a similar error?
 
I've been getting the same error since last night. The work around I found was do search as a revenue booking then once it loads up to tick the box for classic award.
 
I'm told that this issue was caused by an update that took place yesterday. QF is aware of the problem and they're apparently working on trying to fix it.
 
I'm told that this issue was caused by an update that took place yesterday. QF is aware of the problem and they're apparently working on trying to fix it.
Its frustrating that updates cause these issues which really means that testing wasn't done before making changes. Microsoft jams up our work systems so many times by updating. I've turned off the auto updates on my laptop.
 
The Frequent Flyer Concierge team takes the hard work out of finding reward seat availability. Using their expert knowledge and specialised tools, they'll help you book a great trip that maximises the value for your points.

AFF Supporters can remove this and all advertisements

I'm told that this issue was caused by an update that took place yesterday. QF is aware of the problem and they're apparently working on trying to fix it.
Shame that QF didn’t put a banner on their website about this. Wasted my time in trying different browsers multiple times, and the time of many others.
 
I called QF this morning reporting the error and noting I had experienced it since yesterday. She was convinced it was my server error and to her credit, really tried to help me 'fix' my IT issues. The lady did try her best!
Nice of her to try and help with your ‘server issue’, when all along it was a problem at QF, and no fault of yours. 🤷‍♂️
 
Back
Top