homeassistant-portainer
homeassistant-portainer copied to clipboard
[Question] No response from host.
Hello together, I'm running my Homeassistant as an Container and installed HACS. Now I want to control my other containers with Homeassistant and found your Addon. When I tried to connect to docker, it says: unable to fetch data "endpoints" (no_response)
So I activated the debug and he says: query: endpoints, get, {} and in the second line: unable to fetch data "endpoints" (no_response)
I've tried to use https and without, tried to add "/api/endpoints/2/" and other things. I even removed the docker from the swarm and it didn't helped. I have no clue how i could go further.
Hopefully, somebody could help me. Thanks, before. Greetings Ralf
I'm not sure if it's a bug or a question, if this is a bug, maybe I, should it recreate that someone reacts?
@RatWolf
I was in the same boat as you. But just figured it out by looking at the source code.
You will want to provide the ip address of the system where you have portainer running along with the port in the field for ˋhostˋ. Also, check the ˋUse SSLˋ option box. See image below for reference.
First, thanks for your reply @vinkmr . Sadly, I've also tried that and it doesn't work. The interesting thing ist, the only Packages from my HA to my Docker is this (IP changed): 19:01:08.430519 ARP, Request who-has 10.0.0.1 tell 10.0.0.2, length 46
@RatWolf I am having a little trouble understanding your question. Correct me if I understand your situation wrong.
You have homeassistant(HA) running as a docker container, and you also have portainer running as docker container, you have forwarded port 9443 for the portainer container to the some port on the host machine. Now when you provide <host_IP>:<some_port> in the ˋHost` field, along with the API key you have generated on portainer, and after turning on "Check SSL" option on the HA portainer integration, you are still getting "no_response"?
Are you able to login to your portainer instance from the machine running HA via a browser?
check if you can reach it from HA directly. its likely that they cant communicate.
@RatWolf I'm having the same problem as you before. You need to check the following:
-
Make sure you have installed Portainer container, running on 9443 port and you can reach GUI through the browser like https://
:9443. (http should set the redirect rule) -
Make sure you have register an account and generate the access token. (If not, following this guide: https://github.com/tomaae/homeassistant-portainer 【#Get portainer access token】)
-
Make sure you have downloaded the Portainer integration from the HACS
-
【The most important step】Reboot the HA and do the things as the vinkmr said aforementioned.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Sorry, I Missed the Answers. @vinkmr since the HA is only a container on the same machine, I have no Browser on the “Machine”. @tomaae how could I check that? “Docker exec -it homeassistant ping"? @colinLH everything done, but still won't work :(
I could reach the docker from my pc via: https://docker.local:9443/api/endpoints/2 And Ive got this message in my Browser: {"message”:”A valid authorisation token is missing”,”details”:”Unauthorized”}
So I think the docker-Side seems ok. Could it be since it is on the same Host the docker and the HA? Or because I give the HA an own IP? They are both in the same subnet, and on my pfSense is nothing blocked for now. Maybe is there a difference between Portainer CE and Business? And what I also could say, the Ports in Portainer are shown in the Container-Config as 0.0.0.0:9443 and when I click them from the Container-List it leads me to local:9443. So, perhaps the hostname is not right? But that shouldn't be an issue, am I right?
from portainer, you can execute shell in container and run commands there. you need to check both ping and port accessibility from HA
When I tried that, I've got: Unable to retrieve image details So I couldn't connect to the console of the container :(
try different shell
idk how, so I'm fine with it that it will never work.