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

Yagna doesn't notice portforwarding when behind Docker or WSL (maybe VM's too?) #3092

Open
cryptobench opened this issue Mar 3, 2024 · 1 comment

Comments

@cryptobench
Copy link
Member

cryptobench commented Mar 3, 2024

I'm currently trying to solve an issue where our reputation ping stats collector doesn't get seen as portforwarded by the network. It's running inside docker and i've made port 11500 bound to 11500 on my host and portforwarded it, yet yagna net status doesn't write anything about it having a public IP.

As soon as we move it outside Docker, then it works perfectly fine. I tried this on our AWS EC2 instance and i've tried locally on my macbook and I can reproduce the issue. On our EC2 instance we have our loadbalancer exposed at port 80 and 443 via the exact same method, and it's working without any issues.

Today we have a user on our Discord who is trying the same but using WSL. He is experiencing the same issue where the portforwarding isn't going through. https://discord.com/channels/684703559954333727/767706268651094036/1213603107729186887

@cryptobench
Copy link
Member Author

Docker confirmed to have UDP portforwarding issues. --net host should work to mitigate it

WSL probably has some of the same issues.

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

1 participant