I know there are “ways” to do that. But I would prefer a simple and secure solution that is built into the node software, so I don’t have to set-up and fiddle around and monitor an additional application. As node operator I’d like less complexity not more.
1 Like
Hi @Alexey
I opened this port to accees to my dashboard. I have disabled this rule.
Forwarding port rules :
| Application/Service | Internal Port | External Port | Protocol | Device | External IP |
|---|---|---|---|---|---|
| Storj node udp | 28967 | 28967 | UDP | mynode | all |
| Storj node udp | 28967 | 28967 | TCP | mynode | all |
| Storj QUIC udp | 7777 | 7777 | UDP | mynode | all |
| Storj QUIC tcp | 7777 | 7777 | TCP | mynode | all |
mynode = internal IP of my node
The Identity files seems ok :
mynode :~ $ grep -c BEGIN ~/.local/share/storj/identity/storagenode/ca.cert
2
mynode :~ $ grep -c BEGIN ~/.local/share/storj/identity/storagenode/identity.cert
3
Please remove these rules.
Make sure it has a different name.
Please post the last 20 lines from your logs (you can mask the private information).
If you use DDNS, make sure it is updated to your current WAN IP = public IP.