VGA output shows
System is starting up node=production release=202509120559
bringing up the network
systemd-timesyncd failed to perform NTP synchronization, system time may be incorrect
bringing up the local storage
starting application name=incus version=202509120559
system is ready release=202509120559
installed applications: incus(202509120559)
network configuration enp1s0(10.10.3.183), enp2s0
(time appears to be correct and updating (albeit UTC).
Below are the commands I issued to create the 3 containers. The last thing I did was upload the SQL from my existing production metabase instance (after modifying it slightly to run in the test environment). I stopped metabase, uploaded the sql to postgres, and started metabase. After starting metabase is when I lost connectivity via CLI or webui. I can probably rebuild it without too much effort since I have the commands, but I figured maybe someone could help me identify some logs or something to examine.
incus storage volume create local NPM-Data
incus storage volume create local NPM-Letsencrypt
incus storage volume create local metabase-data
incus create docker:jc21/nginx-proxy-manager:latest npm \
-c boot.autostart=true \
-c boot.autorestart=true
incus create docker:metabase/metabase:latest metabase \
-c environment.MB_DB_FILE=/metabase-data/metabase.db \
-c environment.MB_DB_TYPE=postgres \
-c environment.MB_DB_DBNAME=metabase \
-c environment.MB_DB_PORT=5432 \
-c environment.MB_DB_USER=metabase \
-c environment.MB_DB_PASS=<password> \
-c environment.MB_DB_HOST=postgres \
-c environment.MB_SITE_URL=https://testmb.domain.com \
-c boot.autostart=true \
-c boot.autorestart=true
incus create docker:postgres:16 postgres \
-c environment.POSTGRES_PASSWORD=<password> \
-c environment.POSTGRES_USER=metabase \
-c environment.POSTGRES_DB=metabase \
-c boot.autostart=true \
-c boot.autorestart=true
incus storage volume attach local NPM-Data npm /data
incus storage volume attach local NPM-Letsencrypt npm /etc/letsencrypt
incus storage volume attach local metabase-data metabase /metabase-data
incus config device add npm hostport80 proxy connect="tcp:127.0.0.1:80" listen="tcp:0.0.0.0:80"
incus config device add npm hostport81 proxy connect="tcp:127.0.0.1:81" listen="tcp:0.0.0.0:81"
incus config device add npm hostport443 proxy connect="tcp:127.0.0.1:443" listen="tcp:0.0.0.0:443"
incus start npm
incus start postgres
incus start metabase
I also tried to connect from a windows computer that I downloaded the latest windows incus-client onto and it gave me and error:
Error: Get "https://10.10.3.183:8443/1.0": Unable to connect to: 10.10.3.183:8443 ([dial tcp 10.10.3.183:8443: connectex: No connection could be made because the target machine actively refused it.])
It has a different incus certificate than my mac (it was generated on the windows computer and added using my mac).