If after cleaning the containers and rebooting you still have this issue, try running sudo systemctl status docker-compose. This service starts the container via docker-compose on a docker-compose.yml we preloaded on the file system. To elaborate, the Portainer container stack is managed by a systemd service called docker-compose. After you clean the containers up try rebooting the system. Basically docker ps -a should return nothing. Let’s try this, try removing all containers running/stopped, everything. So I can’t conclusively reproduce your issue on my side. On reboot Portainer than started up consistently and I was unable to recreate the timeout error. Seemed to be a a http timeout error or something similar. On first boot after flashing Portainer wouldn’t start up for me at all.
#REFUSED TO CONNECT DOCKER IP SOFTWARE#
Please let me know if you need anything else.Īlright I did some tests using the same software version on the Verdin platform.
These are “ is unreachable”, “portainer’s server IP address could not be found”, and “portainer refused to connect”.
This might be the cause of the problem, or it might be a consequence. By using docker ps the container created on boot where portainer resides is seen to constantly restart.The main screen to which the module boots still gives the same error, even with the new portainer. The module itself can also access it using the IP:9000 address, but a new tab must be opened using CTRL+T on the keyboard for the address to be typed in manually. What I meant is that when another docker container with portainer is created other computers on the network can access it just fine. Other computers connected to the network also face the problem of being unable to connect to the initial portainer.Įxcuse my wording on the update. When the board turns on the same error appears. Yes, the error shows up on the screen connected to the devboard. I’m currently running TorizonCore 4.0.0-devel-202007+build.17 Running the $docker ps command shows that the original portainer keeps restarting. The module can access portainer when following the guide, but it needs to be accessed through another tab where the IP and port are written manually. Worth noting is that following the guide found here allows other computers on the network to access the portainer page by using the module’s IP, but the module itself shows the same error.Īny ideas on how the problem may be resolved? A connection using PuTTY was established with this computer, successfully giving access to the terminal.
#REFUSED TO CONNECT DOCKER IP INSTALL#
This is on a fresh Torizon install on a new device, and was configured through the Easy Installer that came with the board.Ī similar error is experienced when trying to load portainer through another computer by using the IP:9000 method. “This site can’t be reached portainer refused to connect”Īlthough the portainer page does not load, all other websites do. So as the title suggests the Development Board turns on, boots into Torizon and shows this error:
0 kommentar(er)
