dappnode / DNP_HTTPS

A fully automated HTTPS server powered by Nginx, Let's Encrypt and Docker.
2 stars 5 forks source link

Can't access dappnode via local proxy (403) #88

Open ulope opened 8 months ago

ulope commented 8 months ago

Describe the bug

Accessing the UI via the local proxy (i.e. dappnode.local) returns a 403 Forbidden error.

It appears that the hardcoded allowed IP ranges don't include the 172.33/16 network. Possibly related issues: https://github.com/dappnode/DNP_DAPPMANAGER/issues/951 and https://github.com/dappnode/DNP_HTTPS/pull/61

To Reproduce

Unsure, after initial install local access worked but after about a week and a couple of reboots this behaviour started happening.

Expected behavior

Local access to work

DAppNode version:

Core DAppNode Packages versions bind.dnp.dappnode.eth: 0.2.11 core.dnp.dappnode.eth: 0.2.90 dappmanager.dnp.dappnode.eth: 0.2.84, commit: 657ee5f4 https.dnp.dappnode.eth: 0.2.1 ipfs.dnp.dappnode.eth: 0.2.22 wifi.dnp.dappnode.eth: 0.2.9 wireguard.dnp.dappnode.eth: 0.1.3

System info dockerComposeVersion: 2.21.0 dockerServerVersion: 20.10.24+dfsg1 dockerCliVersion: 20.10.24+dfsg1 os: debian versionCodename: bookworm architecture: amd64 kernel: 6.1.0-15-amd64

Additional context

Some probably relevant context: