I don't have any problem decrypting traffic to that site from the browser; have you tried?
In your capture, we see that the client is noxvmhandle, which appears to be some sort of Android VM. The most likely explanation here is that the client application, upon seeing Fiddler's interception certificate, refused to send any HTTPS requests over the channel because it didn't trust Fiddler's root certificate. (You may see some notice in Fiddler's LOG tab to that effect, if the client shut down the TLS channel with an appropriate status code).
There may be some way to configure the VM to trust the Fiddler root, e.g. if it exposes the Android Settings UI.