#QNAP LOST SSH SHELL ACCESS INSTALL#

qpkg package that is part of the QNAP environment to be able to install 3rd party apps without needing to ssh in the server and use CLI and thus no idea what series of Docker run commands have been used to install Portainer at the time. I had Portainer installed on my QNAP NAS through the webUI of QNAP appstore. However, it shows the containers that have been installed with Container Station, but not the Tdarr containers that have been installed with the previous installation of Portainer on my system.Īny help appreciated to try to put things back on track on my NAS. I had some issues connecting to Portainer, but eventually got it working again. I tried to do same by removing Portainer via Qnapclubstore in Appcenter on my QNAP NAS and reinstalling it again outside the appstore via ssh. Additionally, the timestamp next to 'down status' in Portainer dashboard shows a date of March 2 which is earlier than I installed the updates and restarted the NAS.Īny guidance what to do to resolve this issue?Įdit: I found that someone with a Synology NAS had same issue as I do and solved the issue by removing Portainer Container and reinstalling the Portainer container. I am not sure whether restarting the NAS is related to my issue as I fail a bit of conceptual understanding of Docker and Endpoints.

#QNAP LOST SSH SHELL ACCESS MAC#

The Endpoint on my Mac where I have a node running also still works fine. Portainer used to work fine and the containers that I configured with Portainer are still running. The Endpoint on my NAS is of type Docker and has URL 127.0.0.1:2375 When opening Portainer UI on my QNAP it shows that my Docker named 'primary' (on NAS) is down and when I do a refresh of Endpoints it returns it's 'Unable to connect to the Docker endpoint'. I upgraded Container Station (a light Docker implementation) and firmware on my QNAP today so my NAS has been shutdown and restarted with containers that have been installed with Portainer.

Qnap lost ssh shell access