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

LISTEN_PORT setting not configured by env variable shouldn't be forced #168

Open
Robonau opened this issue Aug 12, 2024 · 1 comment
Open

Comments

@Robonau
Copy link

Robonau commented Aug 12, 2024

for instance i would like to be able to change the listen port setting via the jsonrpc api but how it is currently setup i cant.
even if LISTEN_PORT is unset it uses the default value of 6888.
if i send the jsonrpc to change the listen port setting to say 6889 it will respond with success but not actually change it.

@Robonau Robonau changed the title settings not configured by env variable shouldn't be forced LISTEN_PORT setting not configured by env variable shouldn't be forced Aug 12, 2024
@YujiaCheng1996
Copy link

Agreed!Due to massive use of NAT by ISP, STUN needs LISTEN_PORT and DHT_LISTEN_PORT to be different!

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