Open tadaskay opened 3 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity for a long time. If this issue is still valid, please ping a maintainer and ask them to label it as "pinned". Thank you for your contributions.
tail -f ~/.mysterium/logs/mysterium-node.log
2023-06-15T09:52:35.385 INF source/cmd/di.go:513 > Node chain id 137
2023-06-15T09:52:35.669 ERR source/session/pingpong/hermes_url_getter.go:102 > failed to get hermes url from blockchain, using fallback error="Post \"https://polygon1.mysterium.network/\": x509: “polygon1.mysterium.network” certificate is not trusted" chain_id=137 hermes_id=0x80Ed28d84792d8b153bf2F25F0C4B7a1381dE4ab
2023-06-15T09:52:35.905 DBG source/firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed
2023-06-15T09:52:35.905 DBG source/firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://broker.mysterium.network:4222 removed
2023-06-15T09:52:35.905 DBG source/firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.15.116.186:4222 removed
2023-06-15T09:52:35.905 DBG source/firewall/outgoing_firewall_noop.go:61 > Rule for URL: nats://51.15.72.87:4222 removed
2023-06-15T09:52:35.905 INF source/firewall/incoming_firewall_noop.go:38 > Rules reset was requested
2023-06-15T09:52:35.905 INF source/firewall/outgoing_firewall_noop.go:35 > Rules reset was requested
2023-06-15T09:52:35.905 DBG source/config/config.go:216 > Returning CLI value usermode:true
2023-06-15T09:52:35.905 ERR source/cmd/mysterium_node/mysterium_node.go:68 > Failed to execute command: error="could not get hermes URL: Get \"https://observer.mysterium.network/api/v1/observed/hermes\": x509: “observer.mysterium.network” certificate is not trusted"
Still valid
It's a common use case to use VPN with insecure wifi, but our node is unable to start under such network due to SSL cert errs (logs below). It would be nice to have a fallback mechanism that could work under such conditions.