Hi everyone,I have a Quest 3 and cannot connect the the wifi (it's a freebox, french internet provider).Steps i took to troubleshoot : I did manage to connect the quest to my cellphone via hotspot. I factory reseted the quest and retried to connect to the freebox via passwords and QR code. I trued to connect the quest via the phone app. Rooter was rebooted, i was in the same room etc. We have all other devices connecting without problem to this rooter. Thanks for your help

New Participant

Solved

Quest 2, 3 & Pro - Connectivity Issues

448 replies
127840 views

Hi everyone,
I have a Quest 3 and cannot connect the the wifi (it's a freebox, french internet provider).

Steps i took to troubleshoot :

I did manage to connect the quest to my cellphone via hotspot.
I factory reseted the quest and retried to connect to the freebox via passwords and QR code.
I trued to connect the quest via the phone app.
Rooter was rebooted, i was in the same room etc.
We have all other devices connecting without problem to this rooter.

Thanks for your help

TheLegend271265668Answer

Honored Contributor

Hey everyone! I'm a bit late to the party for announcing this, but the PTC for V67 just started rolling out not too long ago. It sounds really promising that some of you are already reporting improvements after updating! For anyone else participating in the latest V67 PTC build, please feel free to continue providing your feedback and experiences—along with your full build numbers, so that I can continue funneling these reports to the team. I don't have confirmation on whether or not a fix was supposed to roll out for this PTC build, but I'm working on finding out anything more I can share from the team. Thanks for continuing to keep me updated with your feedback!

Update:

Hey everyone, its looking like some people are seeing their issue resolved by updating to the latest PTC. If you're interested in testing out the new PTC release, you can find more information for how to opt in here. Please keep in mind that the PTC is a test build for unreleased Quest software builds, so while your Wi-Fi connectivity may have improvements, it's possible that other features of the software could be unstable. If you prefer to stay on stable public builds, I recommend holding out for the live V67 release, which should hopefully be coming out sometime soon!

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably

Show previous replies

V

Velbaek82

New Participant

I’ve installed v67 on my device, and from the testing I’ve done so far it has fixed my issues. But I have to test it further.
I’m connected to a Ubiquiti U7 pro,

P

paulframpton754

Participant

Still happening for me on v67 😞

J

Jiphou

Participant

2 brief disconnection today then a new V66 update (I had already V66) will test it soon

P

paulframpton754

Participant

Yep, still dropping out. V67 Wifi 5.

B

blackboxy

Participant

Nothing has changed!

I am furious!

This is no longer acceptable. META has not been able to fix this bug for half a year!

What are you doing in the development? Do your Job and fix this WIFI Bug!

WIFI is existential for a product like the Quest. Without a functional WIFI, the Quest is worthless.

This story is slowly becoming a law story.....

S

samebeat

Participant

I cannot play any online games because of this bug. Please fix it

A

adonis2101

New Participant

tested v67 PTC with 6GHz WiFi connected to a U7-pro and (after a very brief trial) it seems to be working for me! discovery takes a while with 5GHz disabled but once it's connected it stays up and i can run virtual desktop without immediate disconnects like in v66, but more in-game testing will have to wait till later.

i think it's a bit dicey to mark this as solved in a pre-release without a changelog that's not available to everybody, but, so far it does seem like good news.

T

Talgoro

Participant

Can confirm that v67 solved the problem for me as well. I only tested for about an hour but previously I was getting the first disconnect after 10 minutes of turning the Quest on.

petecod

Participant

I spotted this "solution" on reddit. I'm not going to try it but it may be helpful in giving a clue to the cause of the issue so nicely introduced by Meta way back in v64.

https://www.reddit.com/r/OculusQuest/s/5FHsESYrLr

S

samebeat

Participant

I activated private dns. Till now( maybe two hour) i got no wifi drops

S

samebeat

Participant

Okay, that was not the solution. Yesterday in the evening i did bot have any breakups. But today in the morning a lot of....and i thought just for two hours, i could play online games...thank you meta

TheLegend271265668

Honored Contributor

Hey everyone! Just wanted to check in after more of you got your hands on PTC V67. It sounds like a few more of you are starting to see positive improvements after making the switch to V67, so that's awesome to hear!

lucacesa That's a great question. To be completely transparent with you, "a lot" may have been too presumptuous considering the pool of users reporting in about the issue. I take full responsibility for that miscommunication. A better way to put it would've been that "some" users are reporting that V67 fixed the issue for them. I'll go ahead and correct that now. If it helps, reports can typically come through the multiple channels that we communicate on such as: Twitter, YouTube, Reddit, Instagram, Facebook, Email Support, Chat Support, etc.

Our scope for getting an idea of how many users are effected by a particular issue can most definitely go beyond the community alone. As for the PTC release notes, I'll check with the team to see if there's anything I'm able to provide! Since there's no way to 'pin' comments currently on the community, marking a solution is the next best option in our toolset. I wanted to mark that one in particular because I figured the information would be helpful to onlookers who aren't up to date on the current status of the thread.

paul.frampton.754 Any useful information that I get from the team, I'm always looking to share as soon as possible with everyone. The updates I receive from the team can range from there not being any updates available yet to confirmation that a fix should roll out in X update. This is most definitely something the team is still investigating. Currently, I'm working on gathering more build numbers for PTC's V67 where the issue is still being encountered, so that the team is aware which versions are effected. I apologize if my previous verbiage about the resolution was too ambiguous and up-for-interpretation. What I had meant specifically was that it seems as if users are reporting improvements on PTC V67, so I wanted to recommend others to try the same to see if they noticed any improvements.

samebeat blackboxy paul.frampton.754 Virago54 Can you please provide your full V67 build numbers, so that I can keep bringing these reports to the team for review? You can check in Quick Settings > Settings > Software Update under the Current Version Details section. The formatting should be 67.#.#.###.###.#########. The team is also asking everyone to confirm if any troubleshooting steps from MetaStoreHelp on this thread helped at all after updating to V67. Please let me know, so I can pass that to the team as well!

Update:

lucacesa At the moment, it doesn't look like we share any changelogs regarding our software updates. I completely understand the importance for ensuring everyone is informed about changes or improvements made to our software and products. I recommend keeping a close eye on our Blog, Announcements, and various social media channels for any updates or announcements that we do put out on our software!

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably

S

samebeat

Participant

I am on 67.0.0.506.358.616599355

Iam on a fritzbox with seperate 2,4 and 5 ghz. Channel 36. Static ip and static mac adress.

I sit 1 meter next to my router and got a breakup

TheLegend271265668

Honored Contributor

Thanks for the info! I'll be sure to pass this to the team. Before that, the team also wants to confirm if this troubleshooting made any noticeable difference for your breakups:

@MetaQuestSupport wrote:
If you receive an error while trying to connect to Wi-Fi, you may need to connect your headset to another Wi-Fi network.

Try to disable to off-band of your router if you are using a dual-band router (so, if you are connecting to a 2.4ghz network on a 2.4 / 5ghz router, try disabling the 5ghz network).

Try to eliminate any additional Wi-Fi traffic on your network if possible.

Try connecting to different network if possible to see if the issue follows the device.

Hard reboot the device:

Hold down the power button and volume down button for 30 seconds until you hear the boot-up sound

If the boot-up sound is not heard:

Hold the power and volume (-) button down simultaneously until the boot screen loads on your headset.

Use the volume buttons on your headset to highlight "Boot Device" and press the power button.

Use the volume buttons on your headset to highlight Yes and press the power button.

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably

M

MPires

Inspiring

Two days in a row without problems with wifi (5 Ghz) since I updated to the V67. In my case, the problem seems to have been resolved.

Show more replies

Update:

Update:

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO