rustdesk / rustdesk-server-pro

Some scripts for RustDesk Server Pro are hosted here.
148 stars 74 forks source link

Relay temporary not avalaible (add relay with dns name) #102

Open pdifeo opened 1 year ago

pdifeo commented 1 year ago

I configured RustDesk with two relays. One himself and another. For maintenance reasons the additional relay server is down. I cannot connect to all peers. It's normal ?

rustdesk commented 1 year ago

How about?

image

pdifeo commented 1 year ago

Return the server that in this moment is down

rustdesk commented 1 year ago

It has health check periodically, please test after it is down for some seconds.

pdifeo commented 1 year ago

image

pdifeo commented 1 year ago

image

pdifeo commented 1 year ago

More than an hour has passed. Otherwise I would not have posed the problem.

rustdesk commented 1 year ago

I just tested repeatly many time by close/open hbbr process on one of relay servers, it worked as expected. Could you confirm telnet <the_ip_which_is_down> 21117? Our health check just telnet the port.

rustdesk commented 1 year ago

@Mouxy do you have similar issue?

rustdesk commented 1 year ago

@pdifeo could you try using ip rather than domain?

pdifeo commented 1 year ago
telnet rd-relayxxxxxxxxxxxxx 21117
Trying 217.x.x.x ...
telnet: connect to address 217.x.x.x: Connection refused
pdifeo commented 1 year ago

@pdifeo could you try using ip rather than domain?

tomorrow, now I'm updating the hosting machine.

rustdesk commented 1 year ago

I will test domain names also tomorrow.

Mouxy commented 1 year ago

It only works with IP addresses, I mentioned that in the docs

pdifeo commented 1 year ago

It only works with IP addresses, I mentioned that in the docs

Not good and I'll explain why

I use the domain name because some clients are on the same LAN as the relay.

So to make the scenario clear to you, this relay is with private address. Necessarily I had to assign a domain name. On the Internet it is solved with the public IP address. On LAN it is resolved with private ip.

Clearly the server is under NAT 1:1

From what you say, a relay cannot be under NAT and in the same network as some clients.

rustdesk commented 1 year ago

@Mouxy Thanks for your clarification.

pdifeo commented 1 year ago

using just the IP address .

That's all ? It is honestly not clear.

Mouxy commented 1 year ago

image

That's it, it should work fine with the IP addresses, I'll make sure to state it doesn't work with names.

I do believe this could be fixed though 😊

pdifeo commented 1 year ago

I do believe this could be fixed though

I very much hope so. I was planning to install a relay at each of my custome or so. If the problem is not solved, I cannot implement my plan.

Mouxy commented 1 year ago

Why would you install a relay in every client?

pdifeo commented 1 year ago

Why would you install a relay in every client?

In every site of my customers. Before I wrote wrong. "Cliente" in Italian is Customer.

Mouxy commented 1 year ago

I know 😊 in Portuguese we also say Cliente.

I was genuinely trying to understand what benefit you would have. I can see deploying relays close to regions/countries but in every client might not give you any benefits and you'll have to manage it and allow traffic in.

The devs maybe have a different view, but you might be putting yourself up for big amounts of work for marginal (if any) benefits.

pdifeo commented 1 year ago

I have customers in Italy, Spain and France. So it makes a little sense what I want to do.

But I honestly see inefficiency in choosing a relay based on geographic location. I might get a faster connection by going through another relay because there might be less latency and not the one closest geographically. it is just my opinion which as such is debatable.

dinger1986 commented 1 year ago

image

That's it, it should work fine with the IP addresses, I'll make sure to state it doesn't work with names.

I do believe this could be fixed though 😊

Relay servers do work with names, I have setup around 100 RustDesk Server Pro's on VPS both testing and installing for other people, DNS works fine if setup ONLY for ipv4 and when added in the relay box its added without the port, (tbf never tried it with the port).

dinger1986 commented 1 year ago

further proof it worked (I never touched that server) https://github.com/rustdesk/rustdesk/discussions/5817#discussioncomment-7180781

TLDR: Not working for OP or relaying sessions, kept on getting failed when trying to connect, added in relay server under web console as dns name and working immediately after

rustdesk commented 1 year ago

I think we may solve >1 relay servers with dns in next releases.

pdifeo commented 1 year ago

@dinger1986 Perhaps the problem is not clear. If the ADDITIONAL relay server is DOWN, nothing works anymore. It normally works fine. I keep the problem. So some thing makes it happen.

rustdesk commented 1 year ago

This issue is very clear I think, no need to discuss it further which making it more confusing.

pdifeo commented 1 year ago

I think we may solve >1 relay servers with dns in next releases.

Hi Any news about it ?

pdifeo commented 1 year ago

Hi,

when is implementation planned? is very important to me.

rustdesk commented 11 months ago

https://github.com/rustdesk/rustdesk-server-pro/releases/tag/1.1.11