[Bug]: ERR_CONNECTION_REFUSED

[jraben]

Issue Category

Installation/Setup

Bug Description

Script said successful installation, on newly installed Ubuntu PC, not able to access the Command Center. Where should I start troubleshooting?

Steps to Reproduce

System Details Report

---

Report details

• Date generated: 2026-03-18 21:20:35

Hardware Information:

• Hardware Model: Dell Inc. Vostro 3681
• Memory: 64.0 GiB
• Processor: Intel® Core™ i5-10400 × 12
• Graphics: Intel® UHD Graphics 630 (CML GT2)
• Disk Capacity: 1.0 TB

Software Information:

• Firmware Version: 2.35.1
• OS Name: Ubuntu 25.10
• OS Build: (null)
• OS Type: 64-bit
• GNOME Version: 49
• Windowing System: Wayland
• Kernel Version: Linux 6.17.0-19-generic

Expected Behavior

Able to access Command Center

Actual Behavior

ERR_CONNECTION_REFUSED

N.O.M.A.D. Version

1.29.1

Operating System

Ubuntu 24.04

Docker Version

29.3.0

Do you have a dedicated GPU?

No

GPU Model (if applicable)

No response

System Specifications

System Details Report

---

Report details

• Date generated: 2026-03-18 21:20:35

Hardware Information:

• Hardware Model: Dell Inc. Vostro 3681
• Memory: 64.0 GiB
• Processor: Intel® Core™ i5-10400 × 12
• Graphics: Intel® UHD Graphics 630 (CML GT2)
• Disk Capacity: 1.0 TB

Software Information:

• Firmware Version: 2.35.1
• OS Name: Ubuntu 25.10
• OS Build: (null)
• OS Type: 64-bit
• GNOME Version: 49
• Windowing System: Wayland
• Kernel Version: Linux 6.17.0-19-generic

Service Status (if relevant)

No response

Relevant Logs

Browser Console Errors (if UI issue)

Screenshots

No response

Additional Context

No response

Pre-submission Checklist

• I have searched for existing issues that might be related to this bug
• I am running the latest version of Project N.O.M.A.D. (or have noted my version above)
• I have redacted any personal or sensitive information from logs and screenshots
• This issue is NOT related to running N.O.M.A.D. on an unsupported/non-Debian-based OS

[PattheRat22]

Have you run start_nomad.sh yet? The script to run start_nomad.sh should be at the bottom of the README, or you can just run this command in your terminal: sudo bash /opt/project-nomad/start_nomad.sh

[jraben]

jraben@unbt:/opt/project-nomad$ sudo bash /opt/project-nomad/start_nomad.sh
[sudo: authenticate] Password:
Finding Project N.O.M.A.D containers...
Found the following containers:
nomad_admin
nomad_updater
nomad_redis
nomad_mysql
nomad_dozzle
nomad_disk_collector

Starting container: nomad_admin
nomad_admin
✓ Successfully started nomad_admin

Starting container: nomad_updater
nomad_updater
✓ Successfully started nomad_updater

Starting container: nomad_redis
nomad_redis
✓ Successfully started nomad_redis

Starting container: nomad_mysql
nomad_mysql
✓ Successfully started nomad_mysql

Starting container: nomad_dozzle
nomad_dozzle
✓ Successfully started nomad_dozzle

Starting container: nomad_disk_collector
nomad_disk_collector
✓ Successfully started nomad_disk_collector

Finished initiating start of all Project N.O.M.A.D containers.

http://localhost:8080/ = ERR_CONNECTION_REFUSED

[wouterwashere]

Same here after running the command below, as recommended by the installer script, due to problems with the Docker runtime.

sudo systemctl restart docker

Reboot and the shell scripts to start or stop the service in all different orders will not solve this. An uninstall and re-install will make it available again.

[jraben]

not able to use uninstall script:

curl: (23) client returned ERROR on write of 1369 bytes

[jraben]

new Ubuntu install, new error on install:

✘ Container nomad_mysql Error dependency mysql failed to start

[jraben]

reran install script, back to original error: ERR_CONNECTION_REFUSED

✔ Image ghcr.io/crosstalk-solutions/project-nomad:latest Pulled 3.6ss
✔ Image ghcr.io/crosstalk-solutions/project-nomad-disk-collector:latest Pulled 2.7ss
✔ Container nomad_updater Running 0.0ss
✔ Container nomad_redis Healthy 8.0ss
✔ Container nomad_dozzle Running 0.0ss
✔ Container nomad_disk_collector Running 0.0ss
✔ Container nomad_mysql Healthy 38.0s
✔ Container nomad_admin Started

[jraben]

another new install, same issue.

[PattheRat22]

I'm starting to encounter an issue similar to this. However, I did find an error in nomad_admin when checking Dozzle that may be related to this issue:

Container started
Starting entrypoint script...
Running wait-for-it.sh to ensure MySQL is ready...
wait-for-it.sh: waiting 60 seconds for mysql:3306
wait-for-it.sh: mysql:3306 is available after 0 seconds
MySQL is up and running!
Running AdonisJS migrations...
node:internal/modules/run_main:92
  const type = getNearestParentPackageJSONType(mainPath);
               ^

Error: Invalid package config /app/package.json.
    at shouldUseESMLoader (node:internal/modules/run_main:92:16)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:20)
    at node:internal/main/run_main_module:36:49 {
  code: 'ERR_INVALID_PACKAGE_CONFIG'
}
Node.js v22.22.1
Container stopped

Can you try to go to http://localhost:9999/container and check nomad_admin to see if this is the same error you have (Unless you can't access Dozzle either?) This issue only occurred to me when I tried to update from NOMAD 1.30.0 rc-2 to 1.31.0.

[jraben]

Error:
Access
denied
for
user
'nomad_user'@'172.18.0.7'
(using
password:
YES)

⁃ Packet.asError
node_modules/mysql2/lib/packets/packet.js:739
⁃ ClientHandshake.execute
node_modules/mysql2/lib/commands/command.js:29
⁃ Connection.handlePacket
node_modules/mysql2/lib/base/connection.js:508
Container stopped
Container started
Starting entrypoint script...
Running AdonisJS migrations...

[PattheRat22]

This error has been documented on #387, try seeing if it helps you. If it does, you might as well close this, since I can just make another bug report for my issue.

[jraben]

ran those commands and it did NOT solve the issue.

[chriscrosstalk]

This is a MySQL credential mismatch that sometimes happens on fresh installs. The nuclear option that reliably fixes it:

cd /opt/project-nomad
sudo docker compose -p project-nomad down
sudo rm -rf /opt/project-nomad/mysql
sudo docker compose -p project-nomad up -d

This wipes the MySQL data directory so it reinitializes with the correct credentials from the compose file. You'll lose any content you've already downloaded, but on a fresh install that should be nothing.

If you've already downloaded content you want to keep, let us know and we can walk through resetting just the MySQL credentials instead.