Unable to connect to Portainer

[Berengario]

Hi Guys

I am very new to all this VM, and Hyperviser. So I have given this a try as I wanted to run a small wordpress site at home for journaling.

I have setup Proxmox successfully. Initially it got stuck at finding my country, but rebooting and starting the install again worked fine.

Once in Proxmox at server "https://192.168.1.15:8006", downloaded Ubuntu 22-04, setup a container.
On the networking side i just selected DHCP, and for dns, i selected "use host settings"

Started the ubuntu server, logged in as root. Then installed Docker as per this article:
https://docs.docker.com/engine/install/ubuntu/

All went well

Installed portainer using this article:
https://docs.portainer.io/start/install/server/docker/linux

All was well

However unable to connect using the port "9443". I entered in the address bar: https://192.168.1.15:9443
no connection

I tried:
https://192.168.1.15:9443
https://192.168.1.15:9000
https://192.168.1.15:8000
http://192.168.1.15:8000

Nothing worked.

I typed "curl https://192.168.1.15:8006"
no problem

typed: "curl https://192.168.1.15:9443"
I got: Failed to connect to 192.168.1.15 port 9443 after 0 ms: Connection refused

I even tried: curl https://192.168.1.15
I got: Failed to connect to 192.168.1.15 port 9443 after 0 ms: Connection refused

Trying for 2 days now. Almost giving up. I tried CE and EE versions

 

[Folke]

Hi,
when you create a vm or a container, they don't share an ip with the host system (proxmox). You can run ip -a inside your container/vm to check which ip it got from your dhcp server.
You can imagine everything you create in Proxmox as a seperate device on your network with it's own ip and everything (gross oversimplification, but for the default settings it works

 

[fschauer]

192.168.1.15 is your PVE host. By default when you create a new container or VM in PVE they will use a bridge and be accessible on a different IP address. Just run ip a in the container or set a static IP address for the container in the network settings of the container.

 

[Berengario]

OMW! You guys are amazing!

running ip a gave me the ip address as 192.168.1.27, using that worked!!!

Thank you so much!!!

 

[Pato_77]

Hi all,

I have the same issue here but...still slightly different

I've installed a Debian VM, and docker in Debian. I've setup Duplicati according:

This is my .env-file:

###  DOCKER-COMPOSE ENVIRONMENT VARIABLES BEGIN HERE

IP_ADDRESS=X.X.X.84  # IP of my Debian VM

# Use: id Docker to find PUID and PGID
PUID=1000
PGID=1000
TZ=America/Santiago
UMASK_SET=007 #Optional
# AUTO_UPDATE=true #optional
# RUN_OPTS=run options here #optional

# Directory Variables
D_Data=/mnt/D_Data/

This is my compose-file:

  Duplicati:
    image: lscr.io/linuxserver/duplicati
    container_name: Duplicati_Media
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - CLI_ARGS= #optional
    network_mode: bridge
    volumes:
      - ${D_Data}/duplicati/config:/config
      - /mnt/USB:/USB
    ports:
      - '${IP_ADDRESS}:9230:8200'
    restart: unless-stopped

My Proxmox-server has IP: X.X.X.7

Calling Duplicati in my browser by: X.X.X.84 or X.X.X.84:9230 is not loading anything.

In the VM (terminal) I do:
wget X.X.X.84 or wget X.X.X.84:9230
Result: Connecting to X.X.X.84... failed: Connection refused.
or Connecting to X.X.X.84:9230... failed: Connection refused.

ip a gives me:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
[B]2: enp6s18[/B]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8000 qdisc fq_codel state UP group default qlen 1000
    link/ether X:X:X:XX:X:X brd ff:ff:ff:ff:ff:ff
    inet X.X.X.84/25 brd X.X.X.127 scope global enp6s18
       valid_lft forever preferred_lft forever
    inet6 X:Xa:X5:Xe:X4:Xf:X:X/64 scope global dynamic mngtmpaddr
       valid_lft 1691sec preferred_lft 1691sec
    inet6 X::X4:Xf:X:X/64 scope link
       valid_lft forever preferred_lft forever
[B]3: docker0[/B]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    inet 172.10.0.1/16 brd 172.10.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 XX::XX:XXXf:XXX7:cXX4/64 scope link
       valid_lft forever preferred_lft forever

I added ALLOW for port 9230 from ANY in UFW, also tried deactivating UFW all without result.
As far as I know and can see, in Proxmox no Firewall is active either.
I've removed the $IP_ADDRESS leaving only the ports, no result.

To verify it's not only Duplicati, I installed Portainer just now. The Docker runs/starts without issues but here also no access to the web service.

I actually don't think so, but could this also have a cause looking at directory/file user/group permissions set in Samba in combination with the user/group/permissions in the Debian VM?
The users ARE able to create, remove and edit files on de SMB Shares mounted in the VM.

I'm out of ideas here. If the community here has any ideas where to look or how to solve this, I'd appreciate it.

 

[fschauer]

- '${IP_ADDRESS}:9230:8200'

looks like duplicati is only listening on that one $IP_ADDRESS. Changing it to '9230:8200' should make it listen on all IP addresses.

 

[Pato_77]

looks like duplicati is only listening on that one $IP_ADDRESS. Changing it to '9230:8200' should make it listen on all IP addresses.

I think I've found something.
I have installed Portainer again, used port 9443 and have a working portainer container. So, it's not my VM. It's Duplicati

According to the Duplicati manual, I should pass these commands through by using the CLI_ARGS=. I only need to find out how to put these arguments in the compose file with the CLI_ARGS=

--webservice-interface=any
--webservice-allowed-hostnames=*
--duplicati-server

So far, browsing online to only thing I got was: "- CLI_ARGS= #Optional" Doesn't help me at all. Hahaha!
I've tried a lot of combinations, but none of them are giving me the nice GUI welcoming me.

If you have any ideas, I'm open to try them.

Thanks in advance