ethanic
ethanic
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
thanks for the help!! i appreciate it lots :), i might get stuck when doing port forwarding later but for now everything works!
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
ahh gotcha
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
In the diagram you provided, I would forward 192.168.1.100 and whatever port Velocity is hosted on right? Velocity would then be able to route traffic to the Docker containers without the need to port forward all of the other containers ports?
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
ahh okay, and that's regardless of whether I use the host IP or docker container ID? so theoretically it doesn't matter if I use the host IP + port or docker ID + port?
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
so I ended up just using the static IP address of my local machine with the port # (I don't know why I didn't think of this before, kinda just flew past my head lmao) and it ended up working. just wanna make sure that thats okay tho, since im using the external IP address and not the docker IP/container ID. Would it pose a problem for when I port forward the velocity proxy tho since all the other containers link to the static IP port(s) on the machine hosted (that hasn't been forwarded) as opposed to the internal docker container ID/IP address?
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
no worries, again thank you!
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
I see, thanks! when I get home later, I'll update on trying to set up Velocity again
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
gotcha, so I woudln't need to mess with forwarding Docker IPs or container IPs when forwarding just velocity
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
ignore the bottom diagram* just the top one since I am hosting velocity inside of a container
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
No description
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
ahh okay I see, this is off topic but I also had a question with port forwarding those IPs as well (which I'm planning to do after setting up Velocity correctly). So with Velocity acting as a proxy to all the other MC servers inside docker containers, I technically wouldn't need to port forward every single MC server I have under the Velocity proxy correct? Since those servers are only reachable if you connect through Velocity, I should be fine with just forwarding the port where Velocity is hosted on and players can connect?
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
gotcha, will update you when I try it out, im out rn but will be back home soon
36 replies
AAdmincraft
Created by ethanic on 9/1/2024 in #questions
Setting up Velocity Inside Docker Container - Can't Connect To Server
ahh okay, I'll try that when I get home. Velocity is able to recognize the Docker container ID/name without it's internal Docker IP address? Sorry I am kind of new to all of this, but if I'm understanding it correctly, each Docker container has it's own internal IP address (separate from whatever IP address the local machine uses to connect players to, which routes to the docker IP), and Velocity only listens on the internal IP connection so I can just use the container ID/name directly? thank you!
36 replies