Found a key with difficulty 36!
Error: unable to write certificate to “/share/public/Storj/Identity/storagenode/storagenode/ca.cert”: /share/public/Storj/Identity/storagenode/storagenode/ca.cert is not a writeable directory: write permission bit is not set on this file for user
@Pauantich - I see the problem - the path /share/public/… doesn’t exist.
As an example:
- my QNAP login username is ‘karl’
- my home directory is /share/homes/karl
- my identity path where I want to keep my identity is /share/homes/karl/identity
- my identity path will contain the a folder with the name of my identity (defaults to “storagenode”) - this means there will be a sub-directory created of /share/homes/karl/identity/storagenode after generation is complete
If you are copying your identity from another machine, make sure it lives in a sub-directory called “storagenode” inside your identity directory.
The filestation app that QNAP provides, while fantastic, doesn’t show you all the raw UNIX file paths in the left-hand file tree, so it can be confusing as to what the physical path is.
Let me know how it goes.
1 Like
I don’t have a directory named share in view.
I create the paths and copy them from the folder properties in Filestation. Is there any way to know what the real route is? From the network of my pc win this address appears: \\ NASio \ homes \ admin \ identity
@Pauantich - you won’t see the physical path in Filestation - trust me it’s there.
try using /share/homes/admin/identity as the path for your identity config.
I am in difficulty 35 with this path: / share / Public / identity
that may work if you are logged in as admin. If you were a non-admin user I would expect that to fail.
Yes, as an administrator I am logged in. I already post results
Got it! valid identity, although it seems ofline
Docker:
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
2020-06-09T15:55:55.508Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-06-09T15:55:55.536Z INFO Operator email {“Address”: “@gmail.com"}
2020-06-09T15:55:55.536Z INFO Operator wallet {“Address”: "0xD30*******************************”}
2020-06-09T15:55:56.446Z INFO Telemetry enabled
2020-06-09T15:55:59.191Z INFO db.migration Database Created {“version”: 39}
2020-06-09T15:56:00.001Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-06-09T15:56:00.922Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-06-09T15:56:00.922Z INFO trust Scheduling next refresh {“after”: “6h3m56.824925002s”}
2020-06-09T15:56:00.922Z INFO bandwidth Performing bandwidth usage rollups
2020-06-09T15:56:00.922Z INFO Node 1h***************************************** started
2020-06-09T15:56:00.922Z INFO Public server started on [::]:28967
2020-06-09T15:56:00.922Z INFO Private server started on 127.0.0.1:*****
2020-06-09T15:56:04.997Z ERROR nodestats:cache Get pricing-model/join date failed {“error”: “heldamount service error: node not found: 1h**************************************; heldamount service error: node not found: 1h*******
", “errorVerbose”: "group:\n— heldamount service error: node not found: 1hE****************\n\tstorj.io/storj/storagenode/heldamount.(Service).GetAllPaystubs:132\n\tstorj.io/sto
rj/storagenode/nodestats.(Cache).Run.func1:78\n\tstorj.io/storj/storagenode/nodestats.(Cache).satelliteLoop:233\n\tstorj.io/storj/storagenode/nodestats.(Cache).Run:77\n\tstorj.io/storj/private/lifecycle.(Group).Run.func1:56\n\tgolang.org/x/sync/err
group.(Group).Go.func1:57\n— heldamount service error: node not found: 1h**************************************\n\tstorj.io/storj/storagenode/heldamount.(*Service).GetAllPaystubs:132\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.fun
c1:78\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:233\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run:77\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func1:56\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
I have restarted the container and it no longer gives an error, although it is still offline
2020-06-09T16:57:00.631Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-06-09T16:57:00.661Z INFO Operator email {“Address”: "@gmail.com"}
2020-06-09T16:57:00.661Z INFO Operator wallet {“Address”: “0xD3***********************************”}
2020-06-09T16:57:01.472Z INFO Telemetry enabled
2020-06-09T16:57:01.493Z INFO db.migration Database Version {“version”: 39}
2020-06-09T16:57:02.405Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-06-09T16:57:03.323Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-06-09T16:57:03.324Z INFO bandwidth Performing bandwidth usage rollups
2020-06-09T16:57:03.324Z INFO Node 1h************************************+ started
2020-06-09T16:57:03.324Z INFO Public server started on [::]:28967
2020-06-09T16:57:03.324Z INFO Private server started on 127.0.0.1:*****
2020-06-09T16:57:03.325Z INFO trust Scheduling next refresh {“after”: “4h31m41.45474677s”}
2020-06-09T17:57:03.324Z INFO bandwidth Performing bandwidth usage rollups
2020-06-09T18:57:03.324Z INFO bandwidth Performing bandwidth usage rollups
Have you signed this identity with an authorization token?
Yes, of course, with one of these that came to my email
p*******@gmail.com:1GSPN*************************************************************L
Please, compare the WAN IP on the status page of your router with IP there: https://www.yougetsignal.com/tools/open-ports/
If they are different, the port forwarding will not work.
Please, check your port forwarding rule on your router, it should contain the same IP as your NAS, the port should be 28967
Make sure that you allowed this incoming port on all firewalls, on router and on your NAS.
Check the address option in the QNAP App, it should contain your external address with port, for example: external.address.tld:28967
Also check this address and port with yougetsignal
Please, compare the WAN IP on the status page of your router with IP there: [https://www.yougetsignal.com/tools/open-ports/ is different from NAS
If they are different, the port forwarding will not work.
Please, check your port forwarding rule on your router, it should contain the same IP as your NAS, the port should be 28967 it is the same as the NAS and the port is the one indicated
Make sure that you allowed this incoming port on all firewalls, on router and on your NAS.
Check the address option in the QNAP App, it should contain your external address with port, for example: external.address.tld:28967 It is configured, but does not load any page
Also check this address and port with yougetsignal Port 28967 is open on xxxxx.ddns.net
What address should I change? as?
You need to compare the public IP from yougetsignal with the WAN IP on the status page of your router.
We are not comparing them with an IP of your NAS, because they are public. The NAS has a local IP, it will be different from the public in most cases and this is ok.
If the port is open, but the dashboard show offline, this is usually mean either unsigned identity or firewall blocking an outgoing traffic.
Do you able to login to your NAS via ssh?
Debe comparar la IP pública de yougetsignal con la IP WAN en la página de estado de su enrutador.
yes, I have compared it and it is different
Yes, I can access it through Putty
If your WAN IP is different from the IP on yougetsignal, then your port can’t be opened, unless you have two routers and made a port forwarding on each of them.
In most cases it is mean that your provider is placed you behind their NAT. In such case you cannot publish any service to the internet.
Thus you have a three options:
- ask your current ISP how to obtain a public IP (it can be dynamic, but must be a public, i.e. WAN IP will match the public IP);
- switch the ISP to one who offer a public IP;
- use a VPN service with port forwarding option, such as portmap.io, ngrok, PIA, PureVPN, etc.
All that process I already did.
Dear Customer,
We will contact you to confirm that your request regarding our internet service at home is complete.
They confirm from our technical platform that they have already been assigned a public IP.
For this change to take effect, you need to keep your router (and ONT in case you have two devices) off for at least fifteen minutes.
Remember that it is a dynamic and not a fixed IP.
Receive a cordial greeting.
Sincerely,
letter isp
Then now the time for the PuTTY.
Please, login to your NAS and check the identity, use the sudo before docker:
ok try the way from the documentation: https://documentation.storj.io/dependencies/identity#confirm-the-identity, but specify the path to the identity in both commands.