TLS Inspection - Audible not working

Hi there,

Just setting up Gateway and associated scanning. I’ve got TLS decryption working well, but my exception for Audible hasn’t worked and the mobile app refuses to connect. I’ve spent a long time trying to track down and exclude all the hosts it’s trying to access, but no joy.

Can anyone shed any light please?

Cheers!

Not sure if it’s possible to match regex to see if the hostname contains the word “ansible”?

Hi,

I’ve used regex to exclude all of the Audible domains I can find (having checked my own local DNS logs to see where the app is calling) and yet it still won’t work. Most odd.

Cheers.

Perhaps you can check your rule ordering, to see if your Do Not Inspect rule is located at the top, then try again?

Yup - it’s at the top of the list. I only have do not inspect rules - not blocking anything at this stage.

I’m having a good few issues actually - a few apps, that I’ve fully excluded, are not working still. In the HTTP logs, they’re all showing as Bypass. Most odd and very frustrating. If I can’t get this to work, I will not be able to use the service (just setting it up for the first time this evening).

Bizarre - I’ve just disabled proxy and TLS inspection and tried the Audible and other apps I’m having troubles with (connected through WARP) and they still don’t work. So it’s something fundamentally wrong with the service.