Is there an existing issue for this?
Current Behavior
Logs fill up with error that look like this when variosu components attempt to validate SSL certificates.
http.client_exceptions.ClientConnectorCertificateError: Cannot connect to host sso.carrier.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1028)')]
Expected Behavior
No response
Steps To Reproduce
I was able to reproduce this reliably using the ha_carrier extension. Each time it attempts to poll for new data, an error is generated instead.
Originally filed here - dahlb/ha_carrier#263
Running 'pip install pip-system-certs' and restarting the container temporarily resolves the issue.
Environment
- OS:
- How docker service was installed:
CPU architecture
x86-64
Docker creation
homeassistant:
image: linuxserver/homeassistant:latest
restart: always
network_mode: host
environment:
PUID: 1024
PGID: 100
TZ: America/Los_Angeles
PATH: /usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/scripts:/opt/photoprism/bin
volumes:
- HomeAssistantConfig:/config
Container logs
Is there an existing issue for this?
Current Behavior
Logs fill up with error that look like this when variosu components attempt to validate SSL certificates.
Expected Behavior
No response
Steps To Reproduce
I was able to reproduce this reliably using the ha_carrier extension. Each time it attempts to poll for new data, an error is generated instead.
Originally filed here - dahlb/ha_carrier#263
Running 'pip install pip-system-certs' and restarting the container temporarily resolves the issue.
Environment
CPU architecture
x86-64
Docker creation
homeassistant: image: linuxserver/homeassistant:latest restart: always network_mode: host environment: PUID: 1024 PGID: 100 TZ: America/Los_Angeles PATH: /usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/scripts:/opt/photoprism/bin volumes: - HomeAssistantConfig:/configContainer logs
Logspew in description.