search

MozillaReality / FirefoxReality

INACTIVE - A fast and secure browser for standalone virtual-reality and augmented-reality headsets.
https://mzl.la/reality
Mozilla Public License 2.0
769 stars 217 forks source link

webxr.today showing cloudflare 520: Web server is returning an unknown error #3936

Closed giannic closed 3 years ago

giannic commented 3 years ago

Configuration

Firefox Reality version: 12.2 Firefox Reality build ID: 5f700c82 (AC 51.0.0)

Hardware: Oculus Quest 2

Steps to Reproduce

  1. Open firefox reality
  2. Observe that the homepage is trying to load webxr.today but shows cloudflare 520 error 520: Web server is returning an unknown error

Current Behavior

webxr.today homepage shows cloudflare 520 error

Expected Behavior

webxr.today loads correctly on homepage

Possible Solution

Not sure

Context

Any VR environment does not load thru firefoxreality as far as I can tell (but I'm pretty new)

Error Logs and Stack Traces

I don't have the right tools to retreive logs

giannic commented 3 years ago

For example: opening https://immersive-web.github.io/webxr-samples/immersive-vr-session.html makes the VR session stuck and unable to back out

nigeljw3 commented 3 years ago

I have had the same problem for over a week on my Oculus Quest. This issue is completely breaking webxr. Only the first frame is rendered and then I have to kill the app.

zec37 commented 3 years ago

We had the same issue on Pico devices as well.

PhilipGullberg commented 3 years ago

Still having this issue on Pico Neo 2, any solutions yet?

GuillemEspejo commented 3 years ago

I'm having the same problem with my Oculus Quest 2, haven't been able to play any VR content since this bug came out :\

nigeljw3 commented 3 years ago

@keianhzo not sure who to ping about this, but Firefox reality has lost its primary function for over a month on most platforms.

AreEyeGeeBeeWhy commented 3 years ago

I have been running into this issue for over a month with my Oculus Quest 2. Has a solution been found?

nigeljw-unity commented 3 years ago

@bluemarvin or @MortimerGoro do either of you know who we should ping about this issue?

ZemGit commented 3 years ago

Or...@keianhzo ?

jaredhirsch commented 3 years ago

Hey all! 👋 Sorry for the lack of movement here. I'm looking into this.

jaredhirsch commented 3 years ago

Hey again, we're making progress on debugging this. Hope to have the cloudflare config fixed soon. Thanks and sorry 🙏

jaredhirsch commented 3 years ago

OK, this is now fixed. DNS should propagate out in 24-48 hours. (I'll have to find someone with the right permissions to close this bug.) Thanks all!