You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: