Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tcp-proxy default port 443 change has no effect #2392

Open
chenxudong2020 opened this issue Oct 21, 2024 · 5 comments
Open

tcp-proxy default port 443 change has no effect #2392

chenxudong2020 opened this issue Oct 21, 2024 · 5 comments

Comments

@chenxudong2020
Copy link

tcp-proxy default port 443 change has no effect

local.conf is configured as follows:

image

local.conf and tcp-proxy are in the same directory. Start command:
/var/lib/zerotier-one/tcp-proxy

Because my port 443 is already used by caddy, I get an error that port 443 is occupied.

@laduke
Copy link
Contributor

laduke commented Oct 21, 2024

sorry for any confusion. tcp-proxy doesn't have any configuration options. it runs only on 443.

local.conf configures zerotier-one not tcp-proxy

@chenxudong2020
Copy link
Author

Can it be changed to other ports? Port 443 is strictly controlled in China.

@laduke
Copy link
Contributor

laduke commented Oct 22, 2024

The only way is to edit the source code.

#define ZT_TCP_PROXY_TCP_PORT 443

@chenxudong2020
Copy link
Author

Thank you for your answer. I request to add the function of specifying the port. Since zerotier itself provides the function of forwarding traffic, why do we need to provide proxy?

@laduke
Copy link
Contributor

laduke commented Oct 23, 2024

I'm not sure why you need a custom proxy. Most people do not use a custom tcp proxy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants