Hey guys,
Ive installed successfully i think my storj node on my Synology, atleast its showing so,
I am trying to access the dashboard on my windows PC but it keeps saying connection refused when i go to my local IP and :14002
can anyone assist?
Hey guys,
Ive installed successfully i think my storj node on my Synology, atleast its showing so,
I am trying to access the dashboard on my windows PC but it keeps saying connection refused when i go to my local IP and :14002
can anyone assist?
The service is listening on 127.0.0.1:14002, hence why you get a connection refused(=nothing is listening on that) when you try to access it through 192.168.1.3:14002.
im accessing it on a different pc. the Node is on a Synology NAS, at 192.168.1.3, im on another local windows PC
Then change the listening address to 192.168.1.3. Computers don’t make mistakes, they only do what you tell them to do.
im following the steps from here…
omg can anyone else, help. this guy. not even understanding.
look at the second picture in the very first post
make sure ports 28967 and 14002 are clear on both the synology and on your home router.
Hello @codedbymatt,
Welcome back!
@Mitsos is correct - you need either remove 127.0.0.1:
from the console port in the TrueNAS app configuration to make it 14002
, or replace it with 192.168.1.3:
to make it 192.168.1.3:14002
.
if you run it as a docker container from the shell, then this is a section which need to be updated:
...
-p 127.0.0.1:14002:14002 \
...
to be either
...
-p 14002:14002 \
...
or
...
-p 192.168.1.3:14002:14002 \
...
Then you need to stop and remove the container and run it back, using all your parameters including the changed ones.
Regarding offline, please check from this check-list:
how do i change the config file from SSH? as synology doesnt have a text editor?
Have you tried editor
or nano
or vi
or vim
from the shell?
You can use ssh
as far as I know, you need to enable it. But you would get the same shell, where you can try to use editor
, nano
, vi
, vim
.
Also, if you run docker, you shouldn’t change the config. You need to change parameters of your full docker run
command: How do I change values like wallet address or storage capacity? - Storj Docs
Can’t do nano on Synology, and vi doesn’t load correctly but I just removed the container and created it via GUI on docker, it wouldn’t let me edit, but I could duplicate and edit then delete the old
You need to stop and remove the container, then edit parameters and run again. Do not know how this implemented in Synology though. But if in the CLI, you need to stop and remove the container, then run a new one with all your parameters include changed ones.
I guess you need to remove the custom app and run it again. So, CLI would be likely better than GUI.
However, it may work to configure almost everything in config.yaml
instead, but for example at least the STORAGE variable you need to provide empty in this case, e.g. -e STORAGE=""
, then it wouldn’t override what’s specified in the config file.
I would suggest to take a look on docker compose:
And use one of the samples:
You can use Synology GUI as described GUI container manager in Dsm Synology - #7 by xsys
Most variables are configured in the initial setup, while few of them in the config.yaml file.
Furthermore, there is multiple ways how to edit config files or any text file without command line access on Syno. I can elaborate if needed…
i have gone through a full reset of my synology now, and reinstalled the NAS, but i when i go into nano into the config.yaml file, it has none of my settings but it shows on the CLI dashboard that its running.
i set these when i setup,
8TB and with my static IP, and my wallet and it seems to all be missing
But i just cant get in anywhere to change the 127.0.0.1 to 192.168.1.3:14002
i just did it based on a manual software update and removed it and then updated the 127.0.0.1 to my local 192.168.1.3
Parameters in the docker run
command have a precedence above parameters in config.yaml
, so you do not need to change this file at all, you are passing all needed parameters in your docker run
command.