I've looked into this a bit further. A 404 page wouldn't produce this error (and observably so, as nobody would be playing LSPDFR right now!). However, an invalid response which returns 200 (e.g. network level interception on the local machine/network, or abnormal cloudflare challenge) could. I'll look into a fix for a future release.