Fresh install from ISO v0.3.14: cannot access UI (403 on dappnode.local, empty reply on IP)

[KiwiAndCoffee]

Fresh install of DAppNode from the unattended ISO on an official DAppNode NUC (bought from the DAppNode shop, later upgraded to 64 GB RAM).
The installation finishes with Test Complete Successfully. Press enter to continue. After rebooting from the SSD (USB removed) the system boots fine and I can log in as dappnode, but the web UI is not accessible:

http://my.dappnode → ERR_CONNECTION_REFUSED

http://dappnode.local → 403 Forbidden - nginx

http://IP_NUMBER (LAN IP from my Freebox router) → ERR_EMPTY_RESPONSE

The DAppNode machine is reachable on the network (ping OK) and several core containers are running, but HTTP requests to / return an empty reply.

To Reproduce

Download ISO:
Dappnode-v0.3.14-debian-12.11.0-amd64-netinst-unattended.iso
sha256: 4f30b16557389ba9de9ede3a40279d2aacb8d1731014d212816af2bf3a01ee31

Flash the ISO to a USB stick (freshly reflashed) using Balena Etcher.

Boot an official DAppNode NUC from the USB stick.

Run the unattended installation, selecting the internal SSD and wiping all partitions.

Wait until the installation script shows Test Complete Successfully. Press enter to continue.

Press Enter, reboot, remove the USB stick, let the NUC boot from SSD.

Log in successfully on the console.

From another machine on the same LAN (Windows 11 PC, Chrome), try to open:

http://my.dappnode

http://dappnode.local

http://IP_NUMBER

Observe the connection refused / 403 / empty response.

Expected behavior

After a clean unattended ISO install, I expected the DAppNode admin UI to be available at http://my.dappnode or http://dappnode.local, or at least to get a valid HTTP response from http://IP_NUMBER (for example a redirect to the admin UI or a login page). Instead, the proxy returns a 403 or an empty reply even though Docker containers and port 80 are up.

Screenshots

(Attach les photos que tu as déjà prises.)

Installer end screen with Test Complete Successfully. Press enter to continue.

Console after login, showing DAppNode banner and sudo docker ps (multiple core containers Up).

curl -v http://localhost and curl -v http://127.0.0.1 → curl: (52) Empty reply from server.

sudo ss -tulpn | grep :80 showing docker-proxy listening on 0.0.0.0:80 and [::]:80.

ping IP_Number from the Windows 11 PC → 0 % packet loss, <1 ms latency.

Browser errors on http://my.dappnode, http://dappnode.local, http://IP_NUMBER.

DAppNode version:

Install method: unattended ISO Dappnode-v0.3.14-debian-12.11.0-amd64-netinst-unattended.iso

Hardware: official DAppNode NUC (DAppNode shop), upgraded to 64 GB RAM.

OS: DAppNode OS based on Debian 12 (bookworm) from the above ISO.

Browser: Chrome on Windows 11 Pro 25H2.

(Optionally add the exact output of cat /etc/dappnode_version.)

Additional context

Network:

NUC is connected via Ethernet to a switch, which is connected to a Freebox router.

PC client is on the same LAN (same Freebox, no VPN).

From the NUC, core services look up:

bash
sudo docker ps
Output (summarized): several containers Up, including
DAppNodeCore-api.wireguard.dnp.dappnode.eth,
DAppNodeCore-bind.dnp.dappnode.eth,
DAppNodeCore-ipfs.dnp.dappnode.eth (healthy), etc.

bash
curl -v http://127.0.0.1
→ connects to 127.0.0.1:80 but returns
curl: (52) Empty reply from server (no HTTP headers).

bash
sudo ss -tulpn | grep :80
→ docker-proxy listening on port 80 on 0.0.0.0 and [::].

Before wiping the disk and reinstalling from the unattended ISO, this NUC was already running DAppNode with active Ethereum and Gnosis validators. At some point the web UI became unreachable (similar 403 / connection errors), which is why I decided to do a full fresh install on a wiped disk. After the reinstall, the UI is still not accessible as described above.

Question

Could you please provide the exact commands to fix or reinstall the web/proxy / dappmanager for this ISO version, so that the admin UI becomes accessible at http://my.dappnode / http://dappnode.local / http://IP_NUMBER?

Thanks!