Having trouble with the docker compose instructions

[cstrife1]

Hi, this should be easy enough, but I can't get into the UI, so something went wrong in the middle.

I have a Windows machine running a clean Ubuntu in a Virtualbox VM. Network is in Bridged mode so it has direct access to the network. Ubuntu IP is 192.168.88.16.

I edited the docker-compose.yml with the following changes:

POSTGRES_PASSWORD: asjflksajflskadfASDFSADFSAFDSFDSA

POSTGRES_PASSWORD: SAFDfAFSefsekfjlksajdflkEFsaF
NEXTAUTH_URL -> https://192.168.88.16:3000
NEXTAUTH_SECRET: "kasjflaskjfslakfdSAFSDAFsdaFSADfasdFsaf"

Uncomment the https-proxy section.

<YOUR-PUBLIC-HOST-NAME> -> https://192.168.88.16

Uncomment #caddy_data:

docker compose up -d seems to work fine and pulls and starts everything.

ufw allow 3000
ufw allow 9993

But on another machine, going to https://192.168.88.16:3000 just returns refused to connect.

I can ssh into the machine from outside the network (home to office) and it's fine, so I don't think it's any firewall issue.

docker ps -a

CONTAINER ID   IMAGE                       COMMAND                  CREATED          STATUS          PORTS                                                                                             NAMES
035d5ca9694e   caddy:latest                "caddy reverse-proxy…"   44 minutes ago   Up 44 minutes   0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 443/udp, 2019/tcp   ztnet-https-proxy
a4ee8c54aef5   sinamics/ztnet:latest       "/app/init-db.sh nod…"   44 minutes ago   Up 44 minutes   0.0.0.0:3000->3000/tcp, [::]:3000->3000/tcp                                                       ztnet
9f36fad6413f   postgres:15.2-alpine        "docker-entrypoint.s…"   44 minutes ago   Up 44 minutes   5432/tcp                                                                                          postgres
a985205e8eaf   zyclonite/zerotier:1.14.2   "entrypoint.sh -U"       44 minutes ago   Up 44 minutes   0.0.0.0:9993->9993/udp, [::]:9993->9993/udp                                                       zerotier

Ideas?

[sinamics]

I have not tested Caddy with a local IP address, but this is what I notice at a glance.
You enabled the Caddy, but you're trying to access https://192.168.88.16:3000. When Caddy is enabled, it handles HTTPS on the standard ports (80/443) and proxies to ztnet internally.

Try accessing: https://192.168.88.16 (no port)

Other things to fix:

1. <YOUR-PUBLIC-HOST-NAME> should be just the IP, not a URL:

   192.168.88.16

Not https://192.168.88.16

2. NEXTAUTH_URL should match how you access the app:

   NEXTAUTH_URL=https://192.168.88.16

(remove :3000)

[cstrife1]

fix below, ignore this
I tried your suggestions, but it didn't work. So, I set up a ddns using duckdns.org as in your video. Still no good. Most likely it's a network issue on my end.

I do notice in your docs that you do add :3000 to NEXTAUTH_URL, but you don't in your video nor your suggestion above. Is the :3000 necessary for NEXTAUTH_URL?

[cstrife1]

fix below, ignore this

My Ubuntu is a desktop install. Should I be able to open up https://localhost to get to ztnet? That should bypass any and all firewall issues and the ztnet page should come up, yes?

[cstrife1]

Alright, I'm an idiot. I should have looked at the logs first. My passwords for the postgres weren't the same so the db never came up, and the service never started.

It works with the test duckdns.org url (machine outside the network across the internet can get to the ztnet page now).

Thanks