Meta Quest client times out but works as host

Unity Engine
,
1

Hi,

I have a very basic NetCode setup with one synced transform just for testing.

When I start the host from the Quest I can connect to it from the editor and everything works as expected.

But when the editor is the host, or another Quest, I cannot connect from the Quest and the connection times out.

So basically the Quest is able to be a host but not a client.
(Editor-editor works fine).

Am I missing something?

2

Possibly. :wink:
Without any code that’s nearly impossible for us to tell though.

How do you test editor-editor? I suppose Multiplayer Playmode (if not: use that).

Check that your wifi router isn’t the culprit. Easiest is to add Relay to your test, if connection works then its your local network setup. You probably have to add port forwarding. But weird that it would only work one-way, that’s not typical for a port forwarding issue.

Perhaps the Quest also has networking security issues or app requirements (like Android manifest) to satisfy.

3

This is the setup for conenction, as simple as it can be. I am calling these methods with 2 buttons, the ip parameter is the ip of the hosting device.

    public void StartHost()
    {
        var unityTransport = NetworkManager.Singleton.GetComponent<UnityTransport>();
        unityTransport.SetConnectionData("0.0.0.0", PORT);
        NetworkManager.Singleton.StartHost();
    }
   
    public void Connect(string ip)
    {
        var unityTransport = NetworkManager.Singleton.GetComponent<UnityTransport>();
        unityTransport.SetConnectionData(ip, PORT);
        NetworkManager.Singleton.StartClient();
    }

ParrelSync

4

Don’t forget to set the serverlistenaddress (third parameter). This should be 0.0.0.0 to allow all incoming connections.
If the Quest uses IPv6 (not familiar) then maybe try IPv6 addresses.

Last thing: shutdown is important. When you open a port you need to make sure it also gets closed. I tend to assume that Netcode does that no matter how the app shuts down but with today’s devices where the app isn’t actually quitting but pushed to the background you may still have an open port. Rebooting all devices should clear all possibly open ports. Or increment the port number for every new test to be sure.

And add a script that responds to NetworkManager events like OnStartServer/Client and connection/transport events to be able to log those.

5

Unfortunately, I have already tried this and it did not solve my issue :confused:

6

I tried with Relay and it is working, not sure what is the problem with a simple local connection.