"Cannot connect to host" with Google, Telegram, Yahoo... #305
Comments
|
Some log found in hassio logs, not sure it's relevant :
|
|
Can you post the |
|
Like describe here: https://home-assistant.io/components/http/ Can you remove the server_host options from config and retry it? |
|
I don't have server_host option in my config |
|
What is you host system? With generic system, what is your docker version? If you have host access, please report: |
|
Sorry, I can't access to host, it's a pi3 with default hassio installation. I only have ssh access to hassio container, not to host. I need a physical access to PI to open access to host and I'm at work actually. Some info from container : |
|
No problem. For resinos, I need this data not. Can you send my also the Maybe what could help: |
|
|
I think the problem is with NetworkManager on host system ( Maybe with host access: |
|
Hello, I did not have time to look last night, will check tonight. |
|
Maybe the bug is fix with home-assistant 0.61 |
|
Hello, still did not have time to access host by ssh, but I did the update (supervisor -> 0.82, hassio -> 0.61.dev) and problem is still there. |
|
Do you use DHCP? |
|
yes |
|
Any manual changes on network config sample inside boot folder? |
|
No, nothing has changed, IP is the same. Router is configured to always assign the same IP. I really need to take some hours in the night to reboot my raspberry and activate host ssh while at home, we won't understand without this. (kids are definitely eating time !!!) |
|
Finally I managed to take some time and get access : |
|
Also getting this issue, Raspberry Pi 3, running 0.61.1. If I SSH, I can ping websites, but doing a wget gives me the error This has affected all my platforms that use the external network. Maybe worth mentioning that hassio also powers the PiHole add on, which my router is configured to use. |
|
@SteveEdson Please share you Resin network configuration file |
|
@prigal can you get from host: Do you can share you network config or you never change the config file and run on LAN? All look fine. That mean can't resolve the DNS over the router. I play with the idea that we implement a own dns server. |
However |
|
Yes I think so. You can edit this over that: https://docs.resin.io/deployment/network/2.x/ |
|
@pvizeli do you know which bit I need to edit? I edited (directly on the SD card) the file However this was also reverted on a restart, as well as the |
|
Did you set a static IP using the resin-sample file? If not, it is overwritten/extended by your DHCP server... |
|
Realised that my router was still set to use the old |
|
You mentioned using the Pi-Hole add-on and secondly, the Pi is using DHCP (since it gets its DNS via your router). The Pi-hole add-on requires a static IP to be set (not via DHCP or DHCP Lease). |
I have never change anything in my local network. |
|
From command line, I can ping any domain with it's name, so DNS is working (on host and on homeassistant container) |
|
Have updated to 0.61.1, but problem is still there. |
|
@prigal I was not clear in my last message. Does your HA machine have a static IP assigned? |
|
It's not a static IP, only a DHCP static route to ensure my PI will always have the same IP. |
|
(and on my side, I don't use pi-hole) |
|
That is a docker issue. He use only the first DNS server. You can fix it, if you router will send the correct working DNS settings. |
|
Or simply set a true static IP, which also fixes this. |
|
I solved my issue, think I had my PiHole config wrong, and because it's only using the first DNS server, it couldn't connect to anything. The rest of my network was fine, because it was able to fall back correctly. |
|
Ok serving 8.8.8.8 directly from my router via DHCP instead of local DNS server solves problem. |
|
Is using the first DNS server a generic docker issue, or is it a problem with resin / hass? Is there an issue we can track? Apart from that, I think this issue can probably be closed now. Thanks for the help. |
|
Yes thanks for the help :) |
|
So I have been dealing with this for the last couple days as an HA Newb. This information would have been useful on the GETTING STARTED page and I wouldn't have wasted so much time. What I am reading is to assign a static IP to the HA in order to bypass the hassio docker issue of using the first DNS? |
|
@rsissons I don't think we need it in GETTING STARTED page as long as it's an issue that only affect some users. Moreover, issue is quite well documented, in forum and here. A google search should drive everyone to here quite fast. On my side, I solved it without touching anything in hassio. I only update my gateway settings to send 8.8.8.8 as DNS via DHCP and not the local IP of my gateway. |
|
@prigal As a new HA user, I respectfully disagree. If there are known issues that affect the initial installation of HA (Step 3), then putting a note to fix the issue(like the 2.4GHz issue) will save a new user from having to scour the forums to figure out why the default sensors don't work. If this would have been stated as an issue when setting up the wireless BEFORE(you can't change it via ssh, so you have to take it back out of the RPI) inserting it into the RPI for the very first time would have saved me a lot of wasted time and headache. You may be pushing the DNS from your router, but per the instructions on the HA site, it doesn't state that and is not something someone new to HA would know.
There's a Note for connecting to 2.4GHz only as an issue. Another Note could be
It's a small addition to the instructions for new HA users installing for WiFi only just to get the basic setup to actually work. If not, then they have to do a search in the forum (if they know what to search for), remove the card from the Pi, edit the resin_sample to add the DNS, and put it back into the Pi for something a simple addition to the instructions would alleviate. I couldn't get weather underground to work(couldn't reach the site), ecobee couldn't be set up because it couldn't get the pin, and api calls fail. If you don't want to put these in the installation instructions, then at least put a link to Known Installation Issues with forum links. This would save unneeded forum posts asking the same questions, or be searching the internet for a solution that should have been included in the instructions. Don't get me wrong, I am all for new users seeking out their own knowledge for HA(and the learning curve) for things they want to do and how to do them, but initial installation shouldn't be one of them. Help the new users out a little. |
|
sorry for digging this up again. I'm facing the same issue, running PiHole on the same device (using the HASS.io add-on). Now I'm trying to set a static IP and did Google on how to do it on resin. The guide I found suggested to edit the config.json of the boot partition (which somehow didn't work for me, since after a reboot everything was back to normal). In here I read something about editing the resin-sample file. Which way is considered best practice here? Thanks. edit: managed to do it. In the end I didn't use either of the two ways, since I found another guide simply using the network manager CLI tool after that, reboot and you're good to go. That way you even don't need a static IP but can have your DHCP manage it for your |
After update to 0.60.2, hassio can't connect to online apis and services.
Thread on forum : https://community.home-assistant.io/t/strange-cannot-connect-to-host-issue/37467
Google calendar :
Google maps :
Telegram :
The text was updated successfully, but these errors were encountered: