💡 [REQUEST] - Master-Node Connection Through SOCKS proxy

[AmirReza2012]

Reference Issues

No response

Summary

In case somebody does not want the communications between the master and the nodes to happen directly and would prefer to use a proxy (eg. to pass the requests through warp) it would be a good idea to add a "Use proxy to connect" option for each node.

Basic Example

An optional "socks5://user:password@host:port" setting for each node.

Drawbacks

The proxy adds a potential point of failure

Unresolved questions

No response

[kastov]

Firstly, thanks a lot of your contribution.

It is really interesting thing, but i'm aware that supporting proxy can create delays with master → node communications?

There are a lot of background tasks, which relies on "connections".

Some of tasks, for example, Node Health Check, doing its work every 10 seconds.

[AmirReza2012]

Firstly, thanks a lot of your contribution.

It is really interesting thing, but i'm aware that supporting proxy can create delays with master → node communications?

There are a lot of background tasks, which relies on "connections".

Some of tasks, for example, Node Health Check, doing its work every 10 seconds.

Thank you for your efforts!

That is true but in Iran for example I think the communication between a domestic vps and a server located in another country might be suspicious to the gfw (and it does very often result in the foreign IP being blocked especially if the connections are initiated from domestic to foreigner) and using a fast and stable proxy connection shouldn't result in anything more than a few extra ms of delay.
I just thought this might be a useful feature for those who don't want to directly open communication channels from domestic to foreign IP addresses.

[kutovoys]

Firstly, thanks a lot of your contribution.
It is really interesting thing, but i'm aware that supporting proxy can create delays with master → node communications?
There are a lot of background tasks, which relies on "connections".
Some of tasks, for example, Node Health Check, doing its work every 10 seconds.

Thank you for your efforts!

That is true but in Iran for example I think the communication between a domestic vps and a server located in another country might be suspicious to the gfw (and it does very often result in the foreign IP being blocked especially if the connections are initiated from domestic to foreigner) and using a fast and stable proxy connection shouldn't result in anything more than a few extra ms of delay. I just thought this might be a useful feature for those who don't want to directly open communication channels from domestic to foreign IP addresses.

Have you considered using TailScale or similar services to organize connectivity between nodes through their internal network?

[AmirReza2012]

Firstly, thanks a lot of your contribution.
It is really interesting thing, but i'm aware that supporting proxy can create delays with master → node communications?
There are a lot of background tasks, which relies on "connections".
Some of tasks, for example, Node Health Check, doing its work every 10 seconds.

Thank you for your efforts!
That is true but in Iran for example I think the communication between a domestic vps and a server located in another country might be suspicious to the gfw (and it does very often result in the foreign IP being blocked especially if the connections are initiated from domestic to foreigner) and using a fast and stable proxy connection shouldn't result in anything more than a few extra ms of delay. I just thought this might be a useful feature for those who don't want to directly open communication channels from domestic to foreign IP addresses.

Have you considered using TailScale or similar services to organize connectivity between nodes through their internal network?

When dealing with domestic servers inside firewall-restricted countries it is very likely that a solution like TailScale will fail to connect in the first place.

Also you would probably want to conceal the true IP address of your "master" server and that is easily achievable by combining a socks proxy and a proxy outbound from xray-core.