Can't access my HASSIO from outside, again

Configuration
1

Hi, I have the below configuration and I can’t access my HASSIO from outside or inside my LAN with

https://xxxo.duckdns.org

This since few days (has been working fine for years now)

I can access from inside the LAN with

https://192.168.1.10:8123

My configuration is

  1. router forwards port 443 to port 443 to 192.168.1.10 and also port 80 to port 80
  2. Caddy addon
  3. duckdns addon

Nothing in Log.

Any hint?

2

This is my Caddy options, but were working for a year or so, not sure is that

{
  "flags": [
    "-agree",
    "-email",
    "[email protected]"
  ],
  "env_vars": [
    "DUCKDNS_TOKEN=xxxxxxxe"
  ]
}


xxx.duckdns.org {
    tls {
	    dns duckdns
	}
	log data/requests.log {
	rotate_size 50  # Rotate after 50 MB
	rotate_age  90  # Keep rotated files for 90 days
	rotate_keep 20  # Keep at most 20 log files
	rotate_compress # Compress rotated log files in gzip format
    }
    header / {
    Strict-Transport-Security "max-age=31536000; includeSubdomains"
    X-XSS-Protection "1; mode=block"
    X-Content-Type-Options "nosniff"
    X-Frame-Options "SAMEORIGIN"
    Referrer-Policy "same-origin"
    -Server
}
    proxy / 192.168.1.10:8123 {
        websocket
        transparent
        header_upstream Authorization {>Authorization}
    }
}


xxx-dash.duckdns.org {
    tls {
	    dns duckdns
	}
	log data/requests.log {
	rotate_size 50  # Rotate after 50 MB
	rotate_age  90  # Keep rotated files for 90 days
	rotate_keep 20  # Keep at most 20 log files
	rotate_compress # Compress rotated log files in gzip format
    }
    header / {
    Strict-Transport-Security "max-age=31536000; includeSubdomains"
    X-XSS-Protection "1; mode=block"
    X-Content-Type-Options "nosniff"
    X-Frame-Options "SAMEORIGIN"
    Referrer-Policy "same-origin"
    -Server
}
    proxy / localhost:5665 {
        websocket
        transparent
        header_upstream Authorization {>Authorization}
    }
}

xxx-me.duckdns.org {
    tls {
	    dns duckdns
	}
	log data/requests.log {
	rotate_size 50  # Rotate after 50 MB
	rotate_age  90  # Keep rotated files for 90 days
	rotate_keep 20  # Keep at most 20 log files
	rotate_compress # Compress rotated log files in gzip format
    }
    header / {
    Strict-Transport-Security "max-age=31536000; includeSubdomains"
    X-XSS-Protection "1; mode=block"
    X-Content-Type-Options "nosniff"
    X-Frame-Options "SAMEORIGIN"
    Referrer-Policy "same-origin"
    -Server
}
    proxy / 192.168.1.9:8123 {
        websocket
        transparent
        header_upstream Authorization {>Authorization}
    }
}
3

I receive a

502 bad gateway, when I access https://xxx.duckdns.org

any hint on what to check?

In my system log

20-01-05 21:12:54 INFO (MainThread) [hassio.store] Load add-ons from store: 95 all - 0 new - 0 remove
20-01-05 21:23:57 INFO (SyncWorker_13) [hassio.docker.interface] Stop addon_fe41fc28_caddy application
20-01-05 21:23:57 INFO (SyncWorker_13) [hassio.docker.interface] Clean addon_fe41fc28_caddy application
20-01-05 21:23:58 INFO (SyncWorker_7) [hassio.docker.addon] Start Docker add-on korylprince/hassio-caddy-amd64 with version 1.6
20-01-05 21:26:15 INFO (SyncWorker_4) [hassio.docker.interface] Stop addon_fe41fc28_caddy application
20-01-05 21:26:16 INFO (SyncWorker_4) [hassio.docker.interface] Clean addon_fe41fc28_caddy application
20-01-05 21:26:16 INFO (SyncWorker_19) [hassio.docker.addon] Start Docker add-on korylprince/hassio-caddy-amd64 with version 1.6
20-01-05 21:31:32 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token

4

Have you tried pinging your IP:ports to see if your port forwards are responding?

FWIW, on a side note forwarding ports is generally not best practice for this sort of thing. I suggest looking in to router based vpn. You may already have a router that has open vpn or similar. If not, it would be a worthwhile upgrade for sure.

5

Hi, can you explain better for me what I shpuld do: ping from outside the lan, inside, ??

6

Doesn’t matter if your lan is connected to the internet. Just has to be your WAN ip (plus either port 80 or 443 per your config).