Node was successfully installed (without any port forwarding required), registered on the network and claimed into MMM. A few sessions from mobile dVPN app was made and both resulted in a container crash and node going offline on MMN. Investigated logs and identified the timeframes with err patterns which corresponded with node crashes.
1st time node went offline during active session:
2021-06-22T16:40:56.438 ERR session/pingpong/invoice_tracker.go:562 > unknown hermes error encountered error="hermes request promise error: could not request promise: could not execute request: Post https://testnet2-hermes.mysterium.network/api/v2/request_promise: unexpected EOF"
2021-06-22T16:40:56.438 ERR core/service/session_manager.go:281 > Payment engine error error="could not request promise hermes request promise error: could not request promise: could not execute request: Post https://testnet2-hermes.mysterium.network/api/v2/request_promise: unexpected EOF"
2021-06-22T16:40:56.439 DBG session/pingpong/invoice_tracker.go:636 > Stopping...
2021-06-22T16:40:56.442 DBG consumer/session/session_storage.go:294 > Session 73011c39-9e63-466c-9259-aabdc8780588 updated with final data
2021-06-22T16:40:58.044 WRN session/pingpong/invoice_tracker.go:325 > Marking invoice as not sent error="timeout waiting for reply to \"p2p-payment-invoice\": p2p send timeout"
2021-06-22T16:42:48.041 ERR core/service/session_manager.go:281 > Payment engine error error="sending of invoice failed: did not sent a new exchange message"
2nd time it went offline without any active session:
With use of stun-servers:[stun.l.google.com:19302 stun1.l.google.com:19302 stun2.l.google.com:19302] a Docker node was launched on a MAC comp using simplified installation method: https://docs.mysterium.network/node-runners/setup/docker/#for-macos-users-open-a-command-line-terminal-and-type-the-following-command
Node was successfully installed (without any port forwarding required), registered on the network and claimed into MMM. A few sessions from mobile dVPN app was made and both resulted in a container crash and node going offline on MMN. Investigated logs and identified the timeframes with err patterns which corresponded with node crashes.
1st time node went offline during active session:
2nd time it went offline without any active session:
2021-06-22T18:58:00.757 ERR github.com/mysteriumnetwork/payments@v0.0.14-0.20210428115252-773ce9debf01/client/client.go:183 > subscription error
Both cases needed a manual container restart to make my node alive again.
Provider: 0xaa3d1e65a1a84055cb619004a3ca59489970cef5 OS:Alpine Linux v3.12(docker) Architecture:l inux(docker)/amd64 Node version: 0.47.2