Unable to connect to Home Assistant Cloud

Installation Home Assistant OS
1

Hi,

I am running hassio as docker images on Raspbian.
Everything works great, except for the connectivity to Home Assistant Cloud.

I get the following in the log file:
… botocore.vendored.requests.exceptions.ConnectTimeout: HTTPConnectionPool(host=‘169.254.169.254’, port=80): Max retries exceeded with url: /latest/meta-data/iam/security-credentials/ (Caused by ConnectTimeoutError(<botocore.awsrequest.AWSHTTPConnection object at 0x729a0bf0>, ‘Connection to 169.254.169.254 timed out. (connect timeout=1)’))

2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.utils] Max number of attempts exceeded (1) when attempting to retrieve data from metadata service.
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.session] Loading variable profile from defaults.
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.hooks] Event creating-client-class.cognito-idp: calling handler <function add_generate_presigned_url at 0x756778a0>
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.args] The s3 config key is not a dictionary type, ignoring its value of: None
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.endpoint] Setting cognito-idp timeout as (60, 60)
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.client] Registering retry handlers for service: cognito-idp
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.session] Loading variable profile from defaults.
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.session] Loading variable ca_bundle from defaults.
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.session] Loading variable profile from defaults.
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.session] Loading variable api_versions from defaults.
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.credentials] Looking for credentials via: env
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.credentials] Looking for credentials via: assume-role
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.credentials] Looking for credentials via: shared-credentials-file
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.credentials] Looking for credentials via: config-file
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.credentials] Looking for credentials via: ec2-credentials-file
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.credentials] Looking for credentials via: boto-config
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.credentials] Looking for credentials via: container-role
2018-05-20 18:51:42 DEBUG (SyncWorker_11) [botocore.credentials] Looking for credentials via: iam-role
2018-05-20 18:51:42 INFO (SyncWorker_11) [botocore.vendored.requests.packages.urllib3.connectionpool] Starting new HTTP connection (1): 169.254.169.254

I know that the 169.254.169.254 IP is not supposed to leave the RasPi it is running on, but I wonder what is going on? Why is it even resolving to that IP?
SSH’ing into the image reveals that I can easily ping hosts on the internet, so outbound connectivity should be ok.

Any ideas?

-Lars

2

Yeah, so I finally found time to find the issue, which seemed to be related to IPv6.
I disabled it on the RasPi and the issue was gone.

3

I have the same issue, my installation is on docker on Qnap, Home Assistant 0.82.1.
I have a static IP-address and I also set a global setting for the container station my gateways IP as primary DNS and 8.8.8.8 as secondary DNS. I did not publish the server on my external interface.
The error I’m getting is “Unable to reach the Home Assistant cloud” although my account is already on a 1 month trial.
I read other posts about this issue and the general consensus is that it is related to DNS. Can someone instruct a n00b on how to change that in the underlying OS?
Thank you in advance
/Mike

edit** Issue resolved, I had to add DNS in QNAP’s global network switch and choose which interface should act as gateway

4

How did you disable ipv6?

1 Like
5

Yeah…I’d love to know how to disable IPv6, too.