Portainer CLI access
Posted: 02 Dec 2023, 00:02
Hi folks, first of all I wanted to say hello! Decided to get a TerraMaster NAS (F2-223) after browsing this forum quite a bit, so thanks a million everyone!
One problem for which I couldn't find a solution was the one described here. Since this problem still persisted with my current TOS version 5.1.95 on my NAS, here's what I did to fix it (assuming the default Portainer app from the TOS App Center):
1. Connect to the NAS via SSH (make sure the Allow SSH access option is enabled under Control Center > Network Services > Terminal & SNMP
2. Create a backup of /etc/nginx/conf.d/portainer.conf just in case:
3. Open /etc/nginx/conf.d/portainer.conf for editing:
4. Add the headers required for nginx to allow websockets connections. The file should look like so:
5. Restart nginx using
Afterwards opening a console within Portainer works as expected for me:
Note: I only have a single NAS, so couldn't test run extensive tests here. This approach might not survive an OS update, your device might use a port other than 19000 for portainer, etc. Pay close attention to the existing content of /etc/nginx/conf.d/portainer.conf and any error messages or warnings you might encounter. Make sure to document what exactly you do so you can revert changes if something breaks along the way.
Hope this helps
One problem for which I couldn't find a solution was the one described here. Since this problem still persisted with my current TOS version 5.1.95 on my NAS, here's what I did to fix it (assuming the default Portainer app from the TOS App Center):
1. Connect to the NAS via SSH (make sure the Allow SSH access option is enabled under Control Center > Network Services > Terminal & SNMP
2. Create a backup of /etc/nginx/conf.d/portainer.conf just in case:
Code: Select all
cp /etc/nginx/conf.d/portainer.conf $HOME/portainer.conf.backup
Code: Select all
nano /etc/nginx/conf.d/portainer.conf
Code: Select all
location /portainer/ {
proxy_pass http://127.0.0.1:19000/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
Code: Select all
service nginx restart
Note: I only have a single NAS, so couldn't test run extensive tests here. This approach might not survive an OS update, your device might use a port other than 19000 for portainer, etc. Pay close attention to the existing content of /etc/nginx/conf.d/portainer.conf and any error messages or warnings you might encounter. Make sure to document what exactly you do so you can revert changes if something breaks along the way.
Hope this helps