You must listen on the public interface. You’re currently listening on localhost where no one outside of your computer can connect. Your milage may vary, but with my implementation of netcat I have to use this command line to listen on all the public interfaces. netcat -vv -l 0.0.0.0 6666
I’m not an expert (so please check to confirm) but I believe there will be an UPGRADE mechanism where a regular HTTP connection can be made, then upgraded to a WebSocket, so no existing firewall rules interfere unless they are doing aggressive application level packet inspection. Connections are still initiated by the browser.
Install socat in your container and at startup run socat TCP-LISTEN:3306,fork TCP:B-IP:3306 & This will listen locally on your 3306 and pass any traffic bidirectionally to B-IP:3306. socat is available in package named socat. So you will run any of the below commands to install it $ yum install -y socat $ apt install -y … Read more
The reason the connection is refused is that there is no process listening on port 82. The dockerfile used to create the nginx image exposes port 80, and in your pod spec you have also exposed port 82. However, nginx is configured to listen on port 80. What this means is your pod has two … Read more
Specify the required host IP in the port mapping docker run -p 127.0.0.1:1234:80 -d -v /var/www/:/usr/share/nginx/html nginx:1.9 If you are doing a reverse proxy, you might want to put them all on a user defined network along with your reverse proxy, then everything is in a container and accessible on their internal network. docker network … Read more
Short answer for most recent Windows versions mDNS has been a feature of WSL2 for a while now. Concatenating your WSL2 hostname (or the equivalent command/function in your programming/language environment) with “.local” should get you access. For example, from Bash, try: ping “$(hostname).local” For instance, if your hostname is “MyComputer”, then the mDNS should be … Read more
If you want to forward two ports, you may simply add another line like this: config.vm.network :forwarded_port, guest: 8080, host: 8080 config.vm.network :forwarded_port, guest: 5432, host: 5432 A better way, in my opinion, is to setup a private network (or host-only network), so that you don’t have to forward all the ports manually. See my … Read more
A very common problem can be this: Bind your app inside Docker to 0.0.0.0, not to 127.0.0.1 address to let Docker reach the app inside container. UPD: Don’t try to solve it with docker. There is no docker command to fix that. It strictly depends on the using app, web-framework, etc. Read the manual of … Read more
If you have access to SRV Records, you can use them to get what you want 🙂 E.G A Records Name: mc1.domain.example Value: <yourIP> Name: mc2.domain.example Value: <yourIP> SRV Records Name: _minecraft._tcp.mc1.domain.example Priority: 5 Weight: 5 Port: 25565 Value: mc1.domain.example Name: _minecraft._tcp.mc2.domain.example Priority: 5 Weight: 5 Port: 25566 Value: mc2.domain.example then in minecraft you can … Read more
ssh -v -L 8783:localhost:8783 myacct@server.com … channel 3: open failed: connect failed: Connection refused When you connect to port 8783 on your local system, that connection is tunneled through your ssh link to the ssh server on server.com. From there, the ssh server makes TCP connection to localhost port 8783 and relays data between the … Read more