Inspiring

Solved

Meta Quest Pro WiFi setup fail on university network

41 replies
28935 views

We've purchased a bunch of new Meta Quest Pros for our university XR lab. We cannot connect them to the university's WiFi network at all -- cannot get through the initial device setup. In the WiFi settings, the Quest Pro does not seem to retain the CA Certificate selection [Use system certificates] nor the Domain name. It indicates that it has saved the network settings, but fails to connect. When I go back to the settings, all of the other settings appear to be retained: EAP method [PEAP], Phase 2 authentication [MSCHAPV2], Identity [correct], Anonymous identity [blank], Password [(unchanged) -- I can only guess whether it has been retained; I have retyped it many times]. But the CA certificate reverts to [Please select] and after selecting [Use system certificates] the Domain has reverted to [blank] again.

These things are bricks if we can't get past this.

We have many other WiFi devices running on our network -- notebook computers, phones, ... it is not a problem with WiFi signal strength or stability.

W

wynneneoAnswer

New Participant

Hey guys, I might find a weird workaround suddenly. Quest3 with v59

1) Make sure quest does not automatically connect to any Wi-Fi, eg. forget all saved WiFi or disable "auto-connect";

2) You need a open wifi that needs sign-in;

alternative might work: use a phone to set up a open wifi 🤔

3) Connect to the open wifi, then in this Wi-Fi setting, disable the "auto-connect", and disconnect it.

4) Quest will push some notifications claiming that connection lost and tell you to sign-in. In the main menu, there is a ringbell icon - "Notifications" next to "Quick Settings", open it and click the notification that tells you to sign-in the open network.

5) Quest will show a "SECRET" wifi menu hidden by Meta 😅😅, I think it is the old version of wifi setting menu.
In this menu, you can choose the school WiFi and all other staff like "Domain". And the "connect" is clickable in my case😅

Maybe it is a bug of the new Wi-Fi setting menu, please try and see if it works.

MetaStoreHelp Please fix this ASAP

Show previous replies

A

axiom360

New Participant

The other workaround we're testing (but seems a bit flakey) is adding the WPA2 Enterprise network using the Meta Oculus App on a phone and selecting 802.1X EAP. I get periodic "can't reach oculus servers" errors and "hardware" errors when trying to authenticate, but eventually it does connect, even after forgetting all networks (and verifying the oculus is disconnected from WiFi) and rejoining them. Because the connect button remains greyed out no matter what WiFi settings are selected, I'm increasingly getting the sense this is a UI bug that doesn't show the required "domain" field when selecting PEAP>MSCHAPV2>Use System Certificates.

A

axiom360

New Participant

The other workaround seems to be to go into Experimental Features and Toggle on "Disable WiFi Refresh", and you get the old WiFi menu option that includes the Domain field (thanks to my co-worker who just discovered this!).

W

wynneneo

New Participant

great job!

T

twhallAuthor

Inspiring

After nearly 11 months, we finally got the attention of competent people at Meta to look at the issue and provide a workaround. The instructions Meta provided have some specifics to our secure campus network (after I provided them with campus IT URLs for their reference), so you'll need to adapt these to your own campus situation:

[BLOCKQUOTE]

I received an update from our Engineering team. Please see their response below;

We see two possible root causes based on the logs:

The University's certificate cannot be verified with the system certificates of the device.
The domain is incorrect and should be "[xxx.yyy.zzz].edu" instead of "[zzz].edu" (less likely than the above.) Fortunately, the university IT admin page offers the certificate that devices can store to verify with. Can we ask the customer to try out the following steps?
Go to https://documentation.its.[zzz].edu/[long-URL-for-wifi-manually-configuring-wpa2-enterprise-devices] using their headset's browser after having a connection with their phone's hotspot or other available Wi-Fi network.
Download the "2038 USERTrust RSA Certification Authority root certificate" by following that link and clicking "Download Certificate: PEM" on the left column.
Try connecting to the enterprise network.
Instead of "Use system certificate", select "Install certificate".
The file browser will appear and you can find the downloaded certificate.
Install it as a "Wi-Fi certificate" type.
Give a name like "wifi".
At first installation, the Wi-Fi settings might prematurely close the Wi-Fi settings window. If so, try connecting from the Wi-Fi settings again.
Choose PEAP and MSCHAPv2.
At the certificate selection dropdown menu, you will see the certificate with the name that you gave. Select it.
Put in the domain, identity and password as before.
See if it succeeds. If it fails,
Forget the network.
Reconnect by following the same steps as above except for using "[xxx.yyy.zzz].edu" for the domain instead of "[zzz].edu" If that also fails, try the above two domain values but with the "2024 InCommon RSA Server CA intermediate certificate".
The link in the university's IT page leads to a txt file displayed on the browser directly. So you won't be able to download to the headset using that link.
You may need to copy the content as a .crt file and send/upload it to a mail/cloud storage service that you use and download from that service to your headset. If it still fails, please file a bug report after connecting to a working Wi-Fi network.

[/BLOCKQUOTE]

That eventually worked for me, with some obstacles:

* The newly installed "2038 USERTrust RSA Certification Authority root certificate" did not immediately appear in the "certificate selection dropdown menu", but after several minutes and several tries, it did appear. Not sure what I might have done wrong initially, or what I did differently to make it finally appear. Maybe it was a matter of completely exiting the Wi-Fi settings and then coming back to them again.

* When I first tried to use the new certificate with the secure Wi-Fi SSID, I was left in a model Edit dialog, with two buttons: Cancel, and Save. Save seemed to have no effect, it wouldn't close the dialog to allow me to try to connect. Cancel closed the dialog, but without evidently saving anything. It still failed to connect.

* I tried again today, but started in the Wi-Fi settings with "+ New network" where I was able to select the downloaded certificate. I gave the "new network" the same old SSID name. I thought it might complain that that SSID already existed, but it did not; so I presume it replaced the settings for for that SSID. Instead of merely a "Save" button, I had a "Connect" button, and it succeeded in connecting.

* In retrospect, I can't remember whether I did "Forget" on the SSID before trying to "Edit" it with the certificate. Maybe I could have avoided the "+ New network" step. But in any case, that wasn't any harder than "Forget"; just a different menu click.

Best wishes to all.

T

twhallAuthor

Inspiring

Thanks @michellecornelius721

That still begs the question why all of the other tens of thousands of Android devices connect easily, but the Meta Quest Pro absolutely refused.

Go back to my post dated "07-02-2024 09:08 AM" at the bottom of this page [click] to find the solution received from Meta after 11 months of pain: a 15-step process to download a certificate onto the headset, install it, create a new Wi-Fi SSID to use it, ...

Nothing to do with the network signal strength, stability, or congestion.

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO