Why not provide a simple and convenient way to deploy relay #2280

Open
opened 2025-11-20 07:06:55 -05:00 by saavagebueno · 6 comments
Owner

Originally created by @UA-Jin on GitHub (Sep 15, 2025).

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

There have been continuous issues with the deployment of relay relay nodes, making cross-regional use extremely inconvenient. This is because the latency is particularly high, and the back-and-forth stacking will be very sluggish
I think this function is extremely important in self-hosting. Otherwise, when each node cannot P2P, it is very normal for the relay signal to stack back and back, and the delay to rise to over 1000ms

Describe the solution you'd like
A clear and concise description of what you want to happen.

can directly use peers for relaying or add relay nodes in the console just like peers

Originally created by @UA-Jin on GitHub (Sep 15, 2025). **Is your feature request related to a problem? Please describe.** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] **There have been continuous issues with the deployment of relay relay nodes, making cross-regional use extremely inconvenient. This is because the latency is particularly high, and the back-and-forth stacking will be very sluggish** **I think this function is extremely important in self-hosting. Otherwise, when each node cannot P2P, it is very normal for the relay signal to stack back and back, and the delay to rise to over 1000ms** **Describe the solution you'd like** A clear and concise description of what you want to happen. **can directly use peers for relaying or add relay nodes in the console just like peers**
saavagebueno added the feature-request label 2025-11-20 07:06:55 -05:00
Author
Owner

@1nerdyguy commented on GitHub (Sep 15, 2025):

What kind of issues do you have on the deployment?

It's literally just 'spin up container, add new url to config on management server'

@1nerdyguy commented on GitHub (Sep 15, 2025): What kind of issues do you have on the deployment? It's literally just 'spin up container, add new url to config on management server'
Author
Owner

@mlsmaycon commented on GitHub (Sep 15, 2025):

@UA-Jin can you clarify if your issue is with having multiple relay servers, how to do that or running multiple nodes behind a loadbalancer?

@mlsmaycon commented on GitHub (Sep 15, 2025): @UA-Jin can you clarify if your issue is with having multiple relay servers, how to do that or running multiple nodes behind a loadbalancer?
Author
Owner

@UA-Jin commented on GitHub (Sep 15, 2025):

@UA-Jin你能澄清,如果你的问题是有多个中继服务器,如何做到这一点或运行多个节点后面的负载平衡器?

It's not load balancing. I have many servers with bandwidth ranging from 50M to 200M, but their configurations are not high, only 1CPU and 0.5G memory. I tried to pull netbirdio/relay from docker and run the configuration using docker run. In the middle, rel://SPARE_IP:33080 After writing the management configuration ,All ports of the relay server have also been opened. A rather troublesome issue is that I cannot use the domain name to bind the ip and apply for an ssl certificate to use rels://. Only the server's IP can be used for relay

@UA-Jin commented on GitHub (Sep 15, 2025): > [@UA-Jin](https://github.com/UA-Jin)你能澄清,如果你的问题是有多个中继服务器,如何做到这一点或运行多个节点后面的负载平衡器? It's not load balancing. I have many servers with bandwidth ranging from 50M to 200M, but their configurations are not high, only 1CPU and 0.5G memory. I tried to pull netbirdio/relay from docker and run the configuration using docker run. In the middle, rel://SPARE_IP:33080 After writing the management configuration ,All ports of the relay server have also been opened. A rather troublesome issue is that I cannot use the domain name to bind the ip and apply for an ssl certificate to use rels://. Only the server's IP can be used for relay
Author
Owner

@UA-Jin commented on GitHub (Sep 15, 2025):

您在部署时遇到了哪些问题?

它的字面意思是 “旋转容器,在管理服务器上添加新的url到配置”

rel:// SPARE_IP:33080 Cannot be used normally, However, I can only use the server ip for relay configuration,It's really a headache.

@UA-Jin commented on GitHub (Sep 15, 2025): > 您在部署时遇到了哪些问题? > > 它的字面意思是 “旋转容器,在管理服务器上添加新的url到配置” rel:// SPARE_IP:33080 Cannot be used normally, However, I can only use the server ip for relay configuration,It's really a headache.
Author
Owner

@1nerdyguy commented on GitHub (Sep 15, 2025):

Relay's don't load balance, really. The clients will use the relay that responds the fastest to them. So depending on how your clients are distributed, I'd expect them to end up using the same one over and over all things considered.

@1nerdyguy commented on GitHub (Sep 15, 2025): Relay's don't load balance, really. The clients will use the relay that responds the fastest to them. So depending on how your clients are distributed, I'd expect them to end up using the same one over and over all things considered.
Author
Owner

@UA-Jin commented on GitHub (Sep 15, 2025):

Relay's don't load balance, really. The clients will use the relay that responds the fastest to them. So depending on how your clients are distributed, I'd expect them to end up using the same one over and over all things considered.

Yes, I'm aware of this, but I'm currently stuck on the deployment of relay. So, is there a complete tutorial for deploying relay using IP, Or a deployment script can be added,Deployment only requires running the script and modifying management.json

@UA-Jin commented on GitHub (Sep 15, 2025): > Relay's don't load balance, really. The clients will use the relay that responds the fastest to them. So depending on how your clients are distributed, I'd expect them to end up using the same one over and over all things considered. Yes, I'm aware of this, but I'm currently stuck on the deployment of relay. So, is there a complete tutorial for deploying relay using IP, Or a deployment script can be added,Deployment only requires running the script and modifying management.json
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2280