How to access guacamole [Docker installation] - docker

I was following this tutorial https://www.youtube.com/watch?v=iZB4msyOaUs
Could finish all the steps and I have all my containers up and running (see picture below).
But when I run the browser and type the ip address, the port and /guacamole the only thing I can see is a blank screen.
What is the correct address to access it? I tried localhost, 192.168.100.99 (docker machine address), 0.0.0.0, all the ip listed on ipconfig but nothing happens.
Need help. Thx!

Related

We can’t connect to the server at precious.htb. HACKTHEBOX

I cant connect to the server machine named precious.
Here the screenshot
I already run the opennvpn.
And gain Lab Accesss
But the IP Address still not working...
Any idea what should i do?
I tried runserver and run the openvpn.
I gained Lab Access too
but when i go to Precious Machine IP Address... it says Server not Found
then i search for this problem on internet, but there is no clue for it
Add IP to the /etc/hosts and it should resolve the issue.
┌──(kali㉿kali)-[~/Downloads]
└─$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 kali
10.10.11.189 precious.htb

From docker container cant access 192.168.2.* network which is under VPN

The container connects to external servers and executes code there.
These external servers are behind a VPN.
From the local host I can connect to them, either by name or by direct IP.
But for some reason, to the servers in the subnet 192.168.2.* I can not connect from the container. But I can connect to subnets 192.168.123.* (also under VPN).
DNS servers are given to me through the VPN 192.168.2.1 and 192.168.123.1. I tried to assign the same DNS to the container through the key --dns, nothing changes.
Pinging by domain name server1.company.com extracts correct address 192.168.2.200 and thats all.
Does anyone have any ideas?
Answering my own question.
There's no magic here, after all.
with the command scutil --dns I found out which nameservers added by VPN and just added them to docker run ... command like:
--dns=192.168.2.1 --dns=192.168.123.1 --publish-all
and now it works fine.
PS: But I still dont have any idea how it worked before (.

How to debug network host access

I'm having problems with getting proxy setup right in a docker container. I want to download a file from github, but get unable to resolve host address error from wget. Now, how do I debug what goes wrong in accessing the host? I want to see steps like :
requesting `docker.host.internal:3128" (my local proxy)
requesting "company.com/proxy:1234"
requesting "github.com".
What command line utility can get this information? or what other approach can I use to debug inaccessible host?
I had similar issues and found it helpful to debug by comparing behavior of curl locally and via docker.
curl google.com
docker run -it curlimages/curl google.com
If docker network setup is fine, result should be the same.
"unable to resolve host address" points to a problem with DNS resolution. You can try to ping the IP address of github. If you use docker behind a proxy, you need to make some configuration (https://docs.docker.com/network/proxy/). To test connectivity you can use: ping, curl, wget.

Unable to get docker container working with its own IP address

I have been using docker for some time now on my Synology NAS and it works just fine but I need something a little more powerful to run Plex Media Server.
I have installed Photon OS (on my ESXi Host) running Docker and enabled SSH. I have setup a static IP using the following network file configs:
5-Main.link
[Match]
MACAddress=00:00:00:00:00:00 (example)
[Link]
Description=Main
Name=Main
5-Main.network
[Match] Name=Main
[Network] Gateway=192.168.1.1
Address=192.168.1.3/24
DNS=192.168.1.1
DHCP=no
[DHCP] UseDNS=false
I have installed Portainer fine and that works on the 192.168.1.3:9443 address.
What I am trying to achive like I had done successfully on the NAS is to grant a container its own IP address. I created a docker network using the following command:
docker network create --driver=macvlan --gateway=192.168.1.1 --subnet=192.168.1.0/24 --ip-range=192.168.1.0/24 -o parent=Main LAN
This creates the network fine but when you attach it to a container, give the container a MAC address and an IP address within the same range (192.168.1.50) it does not ping out of the container or from the host (or another device) in. curl ipino.io also does not work from inside of the container. These exact steps works perfectly on the Synology NAS (with selecting the NAS' correct NIC etc)
I have tried using Debian OS instead but that also has the same problem. I have tried accepting all traffic in the IP tables but no effect also. On Debian OS, I have also allowed the NIC to be DHCP instead and tried using a static IP within the container but still no effect. I am running out of ideas. I feel this would be something simple but I have searched high and low now but I am coming to a dead end. Any advice would be greatly appreciated.

Nginx proxy manager is not being able to serve the page from another docker container

I am trying for nginx proxy manager (running in a docker container) to connect to another docker container that has port 8080 open on it. When I setup the proxy to connect to 192.168.0.29:8080 the ip address of the host, but it doesn't work, the browser just says that the site didn't send any data.
I tried setting up the reverse proxy with other services (that weren't running inside a docker container), and they worked flawlessly. So, I've concluded, the problem is something with the docker containers.
First, I tried replacing the ip address with the address of the container (shown in portainer) which showed to be 172.17.0.2. But, that didn't work. I can confirm that both containers are in the same network, bridge.
I could not find any solutions for this problem either here, at Stack Overflow, or anywhere else. Hope there's enough data to solve this problem. Thanks ahead of time!
Edit:
running arp -na from within the container gives this output:
[root#docker-00244f7ab2cc:/app]# arp -na
? (172.17.0.1) at 02:42:d1:fc:fc:6b [ether] on eth0
I found the solution to my question after lots of searching and testing and it's quite simple. The solution is to start the nginx proxy manager docker container on the host network instead of the bridge network. Then, you can use localhost and then the port to refer to which service you want to redirect to.

Resources