I updated the location of the identity files and it worked properly, but when I ran the command below it shows that my node is offline. I am wondering if I entered the port information correctly? Should I have used the port provided by Portmap.io in the -p xxxxx:28967? Do I need to add a new rule on portmap.io for port 28966 (if this is the case is it possible to create a second username on portmap.io and run both on the same windows 10 machine to avoid having to pay 29.99/year?)?
I was able to add an aditional OVPN file and add a TAP. Both OVPN files are running on my windows 10 machine now. However the second docker node is still offline. When I check the logs I see there is an issue with the buffer size (logs below). Where do I enter " ```
sysctl -w net.core.rmem_max=2500000
2021-03-20T20:08:53.981Z ERROR contact:service ping satellite failed {"Satellite ID": "12tRxxxxxxWwxxxxxxxx67kmdhH9txxxxxxxxxxxfS2rUmo", "attempts": 4, "error": "ping satellite error: context canceled", "errorVerbose": "ping satellite error: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:138\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.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-03-20T20:08:53.981Z INFO contact:service context cancelled {"Satellite ID": "12tRQrMTWxxxxxxxxxxqs67kmdhH9t6axxxxxxxxxxxUmo"}
2021-03-20T20:08:57.602Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2021-03-20T20:08:57.642Z INFO Operator email {"Address": "xxxx@xxx.xxx"}
2021-03-20T20:08:57.642Z INFO Operator wallet {"Address": "0xxxxxxxc7980bxxxxf9xxxxxx881xxxxxxxxxxxc0"}
2021-03-20T20:08:58.343Z INFO Telemetry enabled {"instance ID": "127P1tt9JkVxxxxxxxxxxTuTZxxxxEdVxxxxxxxxxR3Tja8"}
2021-03-20T20:08:59.049Z INFO db.migration Database Version {"version": 51}
2021-03-20T20:08:59.572Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
2021-03-20T20:09:00.210Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
2021-03-20T20:09:00.210Z INFO bandwidth Performing bandwidth usage rollups
2021-03-20T20:09:00.211Z INFO Node 127P1tt9JkVcCvfAZ6E8pbPuYTuTZpc4AEdV8b8fmydknR3Tja8 started
2021-03-20T20:09:00.211Z INFO Public server started on [::]:28967
2021-03-20T20:09:00.211Z INFO Private server started on 12x.x.x.x:7xxx
2021-03-20T20:09:00.211Z INFO failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2021-03-20T20:09:00.211Z INFO trust Scheduling next refresh {"after": "6h0m29.253789059s"}
should be -p 28967:28967 if you specified 28967 in the configuration on portmap.io
The -e ADDRESS should contain their hostname with their port.
If you trying to run two containers via portmap.io, then you definitely need to have a second connection for the second node and use a different destination port.
The portmap gives you a hostname with unique port and forward this unique port to specified port by you.
If you specified 28967, then port mapping in docker run should use it too, i.e. -p 28967:28967.
If you changed destination port in portmap.io configuration to 28966, then you need to use port mapping in docker run as -p 28966:28967