Replies: 2 comments
-
If anyone has the same issue, just change your port 8888 to the one that you are brodcasting with your box |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hey @Nyfero, I'm not sure I see the benefit considering you're running the container within Docker, which is why both are tied to the same variable. You're almost always going to want them to be the same, but I'd love to hear your use-case! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I have an issue where I brodcasted my port on port 8888 in order to play in 1.1 version but i was stuck on the loading screen because the external reliant port was on 8888 as well. I looked at the run.sh code and I notice that reliant port and external reliant port are bind with the same variable that user can interact with. It could be great to add another variable to control external reliant port as well.
Beta Was this translation helpful? Give feedback.
All reactions