QNAP Not working for some reason

When I attempt to launch the storj app it just loads a window that shows the error:

Not Found

The requested URL /STORJ/ was not found on this server.

Apache Server at xxx.xxx.xxx.xxx Port 8080

Any ideas what may cause this?

The QNAP app is outdated, you need to perform an additional steps, described in the linked thread.

hello, can you share the link?

Hello @hugosbnarciso ,
Welcome to the forum!

I would recommend to do not use a QNAP app and follow the guide for CLI: CLI Install - Storj
To setup a Docker, you need to enable Container station and ssh.

Hello everyone, like to know if there is a compatibility issue between QTS 4.5.2 ans STORJ QNAP Package 1.1.0.

I just installed the application according to the STORJ documentation.

The installation went easy and I configure the required parameters using the configuration wizard provided.

The node status comes online on the appliance; however the dashboard report the status as Offline.

I went thru various troubleshooting documentation and I found that the port 28967 is not open on my internal network using a port Scanner.

When you look at the Docker process created by the appliance on the Container Station on the console screen I see the following errors over the Docker console (storjlabsSnContainer):

2021-04-01T20:46:32.668Z INFO Telemetry enabled {“instance ID”: “12TNrQg1z45vRPx4162CuWB6oqVjLQWnB9uGz2RLLwvcYXGe9AE”}
2021-04-01T20:46:32.776Z INFO db.migration Database Version {“version”: 51}
2021-04-01T20:46:34.299Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2021-04-01T20:46:35.049Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2021-04-01T20:46:35.049Z INFO Node 12TNrQg1z45vRPx4162CuWB6oqVjLQWnB9uGz2RLLwvcYXGe9AE started
2021-04-01T20:46:35.050Z INFO Public server started on [::]:7777
2021-04-01T20:46:35.050Z INFO Private server started on 127.0.0.1:7778
2021-04-01T20:46:35.051Z INFO trust Scheduling next refresh {“after”: “7h28m6.185161518s”}
2021-04-01T20:46:35.054Z ERROR services unexpected shutdown of a runner {“name”: “piecestore:monitor”, “error”: “piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory”, “errorVerbose”: “piecestor
e monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:131\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:1
28\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2021-04-01T20:46:35.055Z ERROR nodestats:cache Get pricing-model/join date failed {“error”: “context canceled”}
2021-04-01T20:46:35.055Z INFO bandwidth Performing bandwidth usage rollups
2021-04-01T20:46:35.056Z ERROR bandwidth Could not rollup bandwidth usage {“error”: “bandwidthdb error: context canceled”, “errorVerbose”: “bandwidthdb error: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*bandwidthDB).Rollup:301\n\tstorj.io/storj/storagenode/bandwidth.(*Servi
ce).Rollup:53\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/bandwidth.(*Service).Run:45\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:81\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:80\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2021-04-01T20:46:35.057Z ERROR contact:service ping satellite failed {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “attempts”: 1, “error”: “ping satellite error: rpc: dial tcp: operation was canceled”, “errorVerbose”: “ping satellite error: rpc: dial tcp: operation was canceled
\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstor
j.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cy
cle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2021-04-01T20:46:35.057Z INFO contact:service context cancelled {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2021-04-01T20:46:35.058Z ERROR collector error during collecting pieces: {“error”: “piece expiration error: context canceled”, “errorVerbose”: “piece expiration error: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceExpirationDB).GetExpired:39\n\tstorj.io/storj/storagenod
e/pieces.(*Store).GetExpired:520\n\tstorj.io/storj/storagenode/collector.(*Service).Collect:88\n\tstorj.io/storj/storagenode/collector.(*Service).Run.func1:57\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/collector.(*Service).Run:53\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:
81\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:80\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2021-04-01T20:46:35.058Z ERROR contact:service ping satellite failed {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “attempts”: 1, “error”: “ping satellite error: rpc: dial tcp: operation was canceled”, “errorVerbose”: “ping satellite error: rpc: dial tcp: operation was canceled
n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstorj
.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cyc
le).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2021-04-01T20:46:35.059Z INFO contact:service context cancelled {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”}
2021-04-01T20:46:35.058Z ERROR contact:service ping satellite failed {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “attempts”: 1, “error”: “ping satellite error: rpc: dial tcp: operation was canceled”, “errorVerbose”: “ping satellite error: rpc: dial tcp: operation was canceled
n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstorj
.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cyc
le).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}

I’m including the software versions running on my NAS.

QTS 4.5.2.1594
STORJ QNAP Package: 1.1.0
STORJ Node Version: v1.24.4

Any help on this issue will be greatly appreciated.

Please advise!

Welcome to the forum @rdiaz63 !

2 Likes

Thanks nerdatwork,

I will follow the the CLI procedure and let the team knows any updates.

Regards!

Hi nerdatwork,

I configure the node using the CLI procedure suggested and works, thanks!

However, during the Automatic Updates cli procedure I got the following error message:

[~] # docker pull storjlabs/watchtower
Using default tag: latest
latest: Pulling from storjlabs/watchtower
c979c4a210b9: Pull complete
86f82b7eaf31: Pull complete
4f32bae73a2d: Pull complete
Digest: sha256:31c0c558ec8adad5cec6cb86320c58018289ca22dafa019c31cd5d6f65f03655
Status: Downloaded newer image for storjlabs/watchtower:latest
docker.io/storjlabs/watchtower:latest

<labs/watchtower storagenode watchtower --stop-timeout 300s
WARNING: The requested image’s platform (linux/amd64) does not match the detected host platform (linux/arm/v7) and no specific platform was requested
65a6883c295aae37e50049f631f7238dfe74c5d8468535085113decaf1a9d037

                                                                                       ago        Up 6 minutes    127.0.0.1:14002->14002/tcp, 0.0.0.0:28967->28967/tcp                                                                                                storagenode

[~] # docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
65a6883c295a storjlabs/watchtower “/watchtower storage…” About a minute ago Up About a minute watchtower
62e62afd297c storjlabs/storagenode:latest “/entrypoint” 6 minutes ago Up 6 minutes 127.0.0.1:14002->14002/tcp, 0.0.0.0:28967->28967/tcp storagenode
[~] #

Please advise!

Forgot to mention my platform is a QNAP appliance and not a linux box.

Please advise!

It should work, even if the platform detected wrongly, because it’s started and not failed.

A post was split to a new topic: May I know if storj work with Qnap TS219p ii?