Internal HTTPS website no longer working - no attempt to resolve /deovr

Smother6647

Hello,

A while back I developed an internal website returning JSON for DeoVR. That worked fine (besides thumbnails not working) for some time, but now after revisiting the project, it seems DeoVR is no longer attempting to resolve the /deovr endpoint.

Here's the details:

A web server in my local subnet is serving a website under a public domain with a valid Let's Encrypt certificate via HTTPS.
The website can be accessed via HTTPS without issues from the Oculus browser, as well from the DeoVR browser.
The access logs do not indicate any request to /deovr. The website is displayed as-is, instead of showing the media overview.
When manually navigating to /deovr or to a specific JSON video within the app, the browser just prints the JSON response without interpreting it.

Unfortunately, I have no idea how I should debug this. It appears the app just doesn't even try to interpret the JSON. Has there been any change in this regard recently (within the last 6 months)?

Thanks for your help.

Smother6647

Okay, as pointed out here, it seems like the issue was related to my Caddy server requiring tls1.3. Setting that to min tls1.2 resolved the issue.