A relay server is integrated into the customized client. If the relay server fails, the client cannot connect.
A relay server is integrated into the custom client, and if the relay server fails, the client will be unable to connect.
Can I set up more than two relay servers in the client's relay server? If one relay server fails, the others will still be available.
Can not
Can not
Can you add the ability to enter multiple relays? Alternatively, could the relay entry option be moved outside of the network setting? That way, after I customize the client to hide the network, I can still set up custom relays in the client.
However, I'd prefer to be able to set up multiple relays at once when using the custom client. Even if some relay domains are no longer used, I can still point them to other relay servers.
For example, we have two relays for the Japan region. I've listed both. If one relay fails, the other relay will continue to work. I've also listed the relays built into our servers. If both relays in Japan fail, the connection will ultimately go through the domestic relay. While speeds will be slower, they'll still be usable.
Relay 1: japan1.example.com Relay 2: japan2.example.com Relay 3: china.example.com
Relay 1 is used first. If Relay 1 fails and becomes unreachable, Relay 2 is used. If both Relay 1 and Relay 2 are unreachable, Relay 3 is used.
Is there a solution to this problem? When the relay server is unreachable, the terminal will be unable to connect, which is unacceptable.
to be fair there is a solution to this. Multiple relay servers (automatically selects your closest relay)
but i understand that this is not the same as you ask for. (a list of relay servers that gets used in correct order) still - it would work as a fallback.
to be fair there is a solution to this. Multiple relay servers (automatically selects your closest relay)
but i understand that this is not the same as you ask for. (a list of relay servers that gets used in correct order) still - it would work as a fallback.
We have set up relay servers in the console, but the rustdesk pro relay servers are selected based on the geographical location of the IP address. We have found that this method has only a 10% chance of selecting the relay server you want, which is not as convenient as directly specifying the relay server in the client.
Can this problem be solved first? We have been troubled by the relay problem for a long time. Now we can only manually change the geographical location of the other party's IP address in the management background to make it go through the relay server, but after the other party's public IP address changes, it becomes ineffective.