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

Why each server.services need to bind an port while client didn't need this port #399

Open
lucasjinreal opened this issue Nov 9, 2024 · 1 comment

Comments

@lucasjinreal
Copy link

Hi

I found this is hard to understanding compare with frp.

[server]
bind_addr = "0.0.0.0:7000" # `2333` specifies the port that rathole listens for clients

[server.services.my_nas_ssh]
token = "xx" # Token that is used to authenticate the client for the service. Change to an arbitrary value.
bind_addr = "0.0.0.0:8080" # `5202` specifies the port that exposes `my_nas_ssh` to the Internet

[server.services.fhh]
token = "xx" # Token that is used to authenticate the client for the service. Change to an arbitrary value.
bind_addr = "0.0.0.0:8081" # `5202` specifies the port that exposes `my_nas_ssh` to the Internet

the server bind port is understandable, but why each services need to bind differnt port?
When I using frp, there only 2 ports for all clients, and it can specific customized domain.

How could I do this simmilar to rathole

@Snowbelldog
Copy link

Rathole is limited to this because it is only intended for the transmission of raw streams. However, you can simply install the Nginx Proxy Manager at the server end and assign the domains to each port locally.

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