Connecting through duckdns fails after last upgrades

I upgraded from 2021.5.5. to 2021.8.8. and now to 2021.9.8
On 2021.5.5. I could connect through duckdns. With last two updates connection fails. I did not change anything in the configuration file external en internal ip remain the same.
Returning to 2021.5.5. and connection is possible again.

I have been searching for some info about this but could not find anything usefull. What am I missing.

Are you using a reverse proxy such as NGINX? If so, read the first breaking change of 2021.7 → 2021.7: A new entity, trigger IDs and script debugging - Home Assistant, you need to adjust your http config accordingly.

That was something i missed indeed. I haven only checked release notes of august and september.
I think this is something to complicated for me. I use reverse proxy indeed on my synology nas.
To my config I added

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 196.192.2.14      # Add the IP address of the proxy server
#    - 172.30.33.0/24  # You may also provide the subnet mask

just copying and not exactly knowing what I am doing.
When checking config the error says :
Invalid config for [http]: [name] is an invalid option for [http]. Check: http->http->name. (See /config/configuration.yaml, line 14).
Should I add something for the subnet mask, and what would that be ?

Thank you for your quick response by the way :slight_smile:

Can you show the full configuration.yaml file please? Looks like an indentation error. The error says that ypu have name inside the http: block, which is invalid.

Herewith a part of my config

default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
homeassistant:
  external_url: https://stillanexample.duckdns.org:8443
  internal_url: https://192.168.2.14:8123

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 196.192.2.14 # Add the IP address of the proxy server
   #- 172.30.33.0/24  # You may also provide the subnet mask
  
#  media_dirs:
#    //media: /media/muziekwdtv
  #  media2: /media/videowdtv
  


  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 25.26086
  longitude: 9.395335
  # customize_domain:
    # automation:
      # initial_state: 'on'
  
  # Impacts weather/sunrise data (altitude above sea level in meters)
  
mobile_app:

stream:

You put the http: section in the wrong place ! (You splitted the homeassistant: key)

default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 196.192.2.14 # Add the IP address of the proxy server
   #- 172.30.33.0/24  # You may also provide the subnet mask
  
#  media_dirs:
#    //media: /media/muziekwdtv
  #  media2: /media/videowdtv
  

homeassistant:
  external_url: https://stillanexample.duckdns.org:8443
  internal_url: https://192.168.2.14:8123
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 25.26086
  longitude: 9.395335
  # customize_domain:
    # automation:
      # initial_state: 'on'
  
  # Impacts weather/sunrise data (altitude above sea level in meters)
  
mobile_app:

stream:

Ahh. thanks…that is what you get when you leave much space between lines, and not having much experience with yaml.
Have a lot of code lines, but still struggling with syntax