Discovery not functioning

Installation
1

I apologize if this has been addressed before but I wasn’t able to find it in search and I also may be lacking in understanding what I’m looking for.

I’m currently running Open Media Vault as an OS and I’m using Docker for multiple containers including: Transmission, Plex, Radarr, Sonarr etc… all of which run perfectly.

I recently installed Home Assistant in a container and I’m unable to get any devices or servers to “discover”.

My log reads:

2019-10-29 13:12:19 ERROR (MainThread) [homeassistant.components.yr.sensor] Retrying in 17 minutes: Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:None [Network is unreachable]

Configuration YAML:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

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

# Sensors
sensor:
  # Weather prediction
  - platform: yr

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

Additionally since I used the GUI in OMV to do the installation I feel like the piece I’m missing is --net=host which i keep seeing being used in the CLI installations but I can’t seem to use that as an extra argument in running any new image.

2

I was able to find this thread: https://community.home-assistant.io/t/nest-and-myq-components-not-connecting-and-duckdns-also-not-working/110202

it seems like the OP was able to change his DNS and it resolved the problem. I was also using Google for my primary/secondary so I changed it. Rebooted the container and checked. Same issue. I’ve changed it 4 times now and I’m lost. Any help would be appreciated.

edit: Maybe I’m in the wrong part of the forum… Mod?