GUI container manager in Dsm Synology

Hello everyone, I started my first node on a synology nas ssh cli install, everything worked for 1 day, after that i don’t know why i tried to add a new variable but by using container manager(docker) gui in Dsm, i restarted the node in Dsm and got back lots of errors including paths to identity and everythiong else, this happend a couple of day ago, now reciving this by email:
Your Node has gone offline
Node IDs: 12p5T1RkmXFBEMWoM6zYT1bpdEAm16T7RtbiVK8Va3VkZqA2Sj3
Your Storage Node on the EU1 satellite has gone offline.
If your node remains offline, you may be suspended or disqualified.

Meanwhile i started a new node on the same HDD which is running for a couple of days now.
My question is: Will my new node be disqualified or i can keep it running? My first node which worked for 1 day is unrecoverable. And now i’m not sure how to modify anything without breaking it, i guess cli only, for adding zksync wallet for example.

You are suspended on the first node, perhaps the problem is the connection if you are offline, you must have a fixed IP or use a DDNS

this is a useful guide but you need to check that your node is reachable from the outside

2 Likes

Thank you, yes my node is reachable from the outside, I’ve got a fixed IP from my ISP for my synology nas.
Now there is one more thing, i can only ssh into the serv and access the cli console but very little details there about the node. Don’t know why won’t let me access the web dashboard. I followed the instructions here but getting this back: This site can’t be reached
**** refused to connect.

Oh, sry forgot to mention my PC and synology are in different locations and different ISP
Port 14002 opened

If you want to access from another computer in your docker command you have to put


-p 14002:14002

Clearify this… your PC and NAS are on the same network?
You access the PC through Anydesk/ Teamviewer/ etc and from that you SSH into NAS?
If both are YES, than yes, put that port into docker run without local IP. That way it can reapond to requestes from any machine in that local network, including from the PC.
If you let 127.0.0.1, it can only respond to local requests made on that machine.
Just mimique the commands in my guide and you won’t have any problems.
A quick tip: use in that location a router that supports Wireguard server (VPN), than you can connect to that local network through Wireguard VPN and ssh into any device there, without the need of a local PC.
Also, you don’t need to forward the dashboard port in router. If you do that, it can be reachable from internet by anyone.

1 Like

Thank you for your response and NO the NAS I am using is in a different location and it’s used for video surveillance and the router it’s set up in bridge mode so can’t really change things there. There is nothing else connected there, just the NAS. I can only ssh in remotly, that’s it. My access to DSM GUI is limited. I will just keep an eye on the node that stays on.
If there will be a report by the end of the month it’s good enough for me. Do node operators recive a report by mail every month or it’s just the dashboard?

You can safely use Synologys GUI only, it’s stable and safe and preventing manual command mistakes Guide to install Storj on synology - #35 by xsys

2 Likes

Hopefully not opened to the entire world of hackers, just limit access on firewall to your IP address/ range only

Thank you, i missed that on the forum :slight_smile: and no, ports opened to ranged ip only

So you SSH from WAN (Internet) to it… so hackers can too :wink:.
If the router is in bridge mode, than you must have another one after it. You could replace the second one with Asus TUF Gaming 3000 as a cheap good option; it has Wireguard server. Than you ssh through VPN and you don’t need to open SSH to WAN.
In the curent setup, you can access the CLI dashboard or forward the dashboard port through router, and let it be accesible from internet, to use the GUI dashboard. But anyone can see it too.

1 Like

No no, SSH is opened only when needed and after that closed. I will try to buy that Asus router, hope it’s worth it, don’t really expect to earn much from this node but things can change after the first months with no held amount, future looks bright. Thank you for your responses.

  1. Do not buy router. You do not need one. Router is for routing traffic between two (or more) networks. If you have only one device there (as you indicated), no need for a routing at all.
  2. You also do not need to buy firewall. Synology NAS has it’s own firewall. You just need to turn it on (it’s off by default) and set the rules.

Allow access only to single specific port (TCP 14002 for node Dashboard, TCP 5000 for Synology GUI), and only from your home IP address, or a range if you have dynamic that changes over the time. Your ISP will be able to tell you what IP range you can expect to get.

If you set up your firewall that tightly, you do not need VPN too.

2 Likes

Just for my curiosity, how did you make it?

Of course firewall is on and specific rules created.

I have no idea about that, the NAS it’s located at a different address and wasn’t setup by me but i can only login from my home network and i have dynamic IP here. I can ask about that and get back here with the answer.

I reckon you should get access to the Syno GUI to be able to check and configure stuff properly there. You can get it directly by allowing port 5000 or 5001 to you, or using Syno’s QuickConnect app, that does not require opened ports / direct access.