I have a node running correctly using docker on a linux VM on my QNAP, I have try to use this app, all working fine but my node remain offline, I have a firewall and I replicate the rule that was working on my VM for port forward and NAT on 28967.
What I can do ?
can you connect to the port using tools such as netcat or similar network testing utilities? what is the value you put in for the port forwarding config?(screenshot please)
No, but i think to have find the problem, there is on container the file resolv.conf that have set the dns to127.0.0.11 that can not be change or override so can non solve the public Ip address.
I have to run the node with public IP address to solve the DNS problem but on log I saw that there are other request to DNS:
2020-04-09T14:15:08.924Z WARN trust Failed to fetch URLs from source; used cache {“source”: “https://tardigrade.io/trusted-satellites”, “error”: “HTTP source: Get https://tardigrade.io/trusted-satellites: dial tcp: lookup tardigrade.io on 127.0.0.11:53: read udp 127.0.0.1:39957->127.0.0.11:53: i/o timeout”, “errorVerbose”: “HTTP source: Get https://tardigrade.io/trusted-satellites: dial tcp: lookup tardigrade.io on 127.0.0.11:53: read udp 127.0.0.1:39957->127.0.0.11:53: i/o timeout\n\tstorj.io/storj/storagenode/trust.(*HTTPSource).FetchEntries:63\n\tstorj.io/storj/storagenode/trust.(*List).fetchEntries:90\n\tstorj.io/storj/storagenode/trust.(*List).FetchURLs:49\n\tstorj.io/storj/storagenode/trust.(*Pool).fetchURLs:240\n\tstorj.io/storj/storagenode/trust.(*Pool).Refresh:177\n\tstorj.io/storj/storagenode.(*Peer).Run:652\n\tmain.cmdRun:209\n\tstorj.io/private/process.cleanup.func1.2:312\n\tstorj.io/private/process.cleanup.func1:330\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:84\n\tstorj.io/private/process.ExecCustomDebug:66\n\tmain.main:329\n\truntime.main:203”}
this id the resolv.conf on my node running on linux VM:
**/app # cat /etc/resolv.conf **
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 1.1.1.1
nameserver 8.8.8.8
search mybrizio.net
this is the same file on QNAP container station:
**/app # cat /etc/resolv.conf **
nameserver 127.0.0.11
options ndots:0
That is odd. I just checked one of our QNAP containers and see the following:
/etc # cat res*
nameserver 10.0.3.1
/etc #
it looks like Docker is likely using network configs relative to the QNAP. please check your container station preferences to confirm DNS settings.
1 Like
@utropicmedia-karl When I enter all the details and click ‘Update my Storage Node’ all the values disappear and that page returns to default values - is that right? You cant see what you entered?
Also if I click on Dashboard → Storage Node Stats I get a Refused Connection Error - presumably its not running?
Also the email text talks about DNS ?
Not much luck so far 
Andrew
Hi guys,
Just posting because I’m getting status “offline” on QNAP docker.
Logs are as follow:
2020-05-07T19:17:11.819Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-05-07T19:17:11.820Z INFO tracing disabled
2020-05-07T19:17:11.855Z INFO Operator email {“Address”: “XXX”}
2020-05-07T19:17:11.855Z INFO Operator wallet {“Address”: “XXX”}
2020-05-07T19:17:13.041Z INFO db.migration Database Version {“version”: 36}
2020-05-07T19:17:14.959Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-05-07T19:17:15.868Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-05-07T19:17:15.868Z INFO bandwidth Performing bandwidth usage rollups
2020-05-07T19:17:15.869Z INFO Node XXX started
2020-05-07T19:17:15.869Z INFO Public server started on [::]:28967
2020-05-07T19:17:15.869Z INFO Private server started on 127.0.0.1:7778
2020-05-07T19:17:15.869Z INFO trust Scheduling next refresh {“after”: “5h17m49.131044427s”}
From the QNAP, I’m able to resolve any name, so DNS is correctly configured.
Port 28697 is opened from the internet.
From the Dashboard, the info I get is:
Version: 1.3.3
Uptime Check: 0%
Audit Check: 100%
At this stage, I don’t know what else to check.
Can anyone help me?
Thanks in advance.
Hello @scrappy,
Welcome to the forum!
Please, enable the debug log level in the config.yaml instead of info and restart the container.
Then take a look into logs.
Check your identity on any case: https://documentation.storj.io/dependencies/identity#confirm-the-identity
Thanks @Alexey
After digging a little bit, I’ve found the following error:
2020-05-08T06:26:49.220Z FATAL Failed to load identity. {"error": "file or directory not found error: open identity/identity.cert: no such file or directory", "errorVerbose": "file or directory not found error: open identity/identity.cert: no such file or directory\n\tstorj.io/common/identity.Config.Load:329\n\tmain.cmdRun:146\n\tstorj.io/private/process.cleanup.func1.4:344\n\tstorj.io/private/process.cleanup.func1:362\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.ExecCustomDebug:68\n\tmain.main:329\n\truntime.main:203"}
Looks like the docker can’t find the identity.cert file. However, my .cert file is stored correctly and mapped to the correct folder:
/share/Storj/StorjV3/identity/
Inside this folder, there’s the identity.cert file. This is the path I’ve configured on the Storj APP in QNAP.
Any idea?
Thanks,
Hi, I have an old qnap TS-219P II that doesn’t support container station. So this app will not work for me? At least I ve tried without success.
Could you login to the NAS via ssh and give me the response of this command:
ls -l /share/Storj/StorjV3/identity/
Yes. Here is the output:
[/share/Storj/StorjV3/identity] # ls -l /share/Storj/StorjV3/identity/
total 16
-rw-r--r-- 1 admin administrators 514 2020-05-08 09:40 ca.cert
-rw-r--r-- 1 admin administrators 241 2020-05-08 09:40 ca.key
-rw-r--r-- 1 admin administrators 1056 2020-05-08 09:40 identity.cert
-rw-r--r-- 1 admin administrators 241 2020-05-08 09:40 identity.keyWith which user you running the QNAP App?
By the way, your identity looks like unsigned. Please, check it:
https://documentation.storj.io/dependencies/identity#confirm-the-identity
It should return 2 and 3 respectively.
Ok, I’ve found the error. As you said, the certs weren’t signed. It’s weird as I signed them with powershell (windows) and exported them to my QNAP. Something happened in between…
Anyway, my node is up and running now.
Thanks very much for your assistance.
1 Like
As an update the latest version of this app are located at:
https://github.com/storj/qnap-storagenode-app/releases
the current versions are pre-release and going through QA. As always all feedback is welcome.
Thanks!
1 Like
Hi, I’m running STORJ_0.7.41.qpkg on my QNAP TVS-1282 and it isn’t running at all. I’ve attached a photo of the log. 
Here is another image.
Hello @Shenron2020,
Welcome to the forum!
Please, show the last 10 lines of the log of the container (text, please)
I move my node to container on QNAP, on dashboard the status is offline:
but it seems that is working, looking the log:
I have check the TCP port 28967 and from a external test it seems close but looking my firewall log I have the connection:
Any suggestion ?
If the port is closed, then it’s offline.
Make sure that you updated the router port forwarding rule to the new IP (here should be IP of your NAS)
Thanks for answer looking the firewall logs that I have attach You can see the accepted connection on port 28967. The internal ip nas is 10.1.0.235. The problem is only related to container on my VM on same QNAP all work perfect !