I am able to setup the multinode. However when adding a node(from here) I am getting this error
Which I know comes from the beforeEach guard of the router. On clicking the Add Node the vue store should dispatch a node/add event which is working fine(no error in that). await this.$router.push(RouterConfig.MyNodes.path);
This is the line responsible for the error. Which always call the beforeEach guard of the router. It check if node added or not. Which fails in my case. The value for store.state.nodes.nodes.length always comes 0. Which causes the error. However, the nodes/add dispatch event works fine.
Is it a bug or I am missing something? I tried with both storj-sim and multinode run.
I believe it’s a bug, but seems not affecting the business logic.
I don’t think so, and it’s easy to check - just call a GET method for the hostname with port.
You can always use nodes from storj-up or storj-sim for tests.
I initially thought that I was doing something wrong so I started logging which actually helped me to understand the whole multinode codebase from the client to cmd to server. But after coming to the server realised the node wasn’t valid so I tried with the storj-up nodes and it worked.
Thank you for the help.
@Alexey I used satellite info inside my storagenode and I got this
ID: 1PastuS5ce9TT2A5AsCf5Qkwnrt2cCwVTkssAjJY9vN1GuHvYF
API Secret: QMBO3ars4TjdELzzfcx203yxpdf2DNq2q5KTAYTMV3A=
Public Address: storagenode1:30001
So I ran the multinode add API(http://localhost:15002/api/v0/nodes) with it but I got rpc: tcp connector failed: rpc: dial tcp: lookup storagenode1 on 127.0.0.53:53: server misbehaving this error
So I thought there might be a DNS resolution problem so I tried the Public Address with 172.18.0.7:30001 but the API goes loading and then timed out
For localhost:30001 and 0.0.0.0:30001 I got rpc: tcp connector failed: rpc: dial tcp 127.0.0.1:30001: connect: connection refused
For localhost:30000 and ``0.0.0.0:30000 I got rpc: tcp connector failed: rpc: tls: first record does not look like a TLS handshake
So I tried to look inside the DRPC protocol but didn’t find any solution.
It should be storagenode info, not a satellite info
However, the output looks valid.
Did you change the IP for storj-up? then you need to restart the whole stack. I do not know, why is that.
So,
docker compose restart
or
docker compose stop
and
docker compose start
should fix this issue. However, you need to wait until the satellite would be fully available I guess for any operations, because nodes would likely restarting every time until it would be available.
For that you need to be in the same network. I do not know details of your setup, but perhaps your docker-compose.yaml does not have options to expose these ports to your host or it’s limited to a some IP (like a localhost).
Hey @Alexeyrpc: tcp connector failed: rpc: tls: first record does not look like a TLS handshake Can you please tell me why it’s happening in localhost:30000?
this is a single node dashboard port, it can be used to see the single node dashboard in your browser, e.g. http://localhost:30000, and some API calls, like a reputation and usage, but it’s an insecure http protocol.
The Multinode dashboard uses dRPC and secure channel to connect the storagenode port, i.e. 30001.