search

IPRoyal / pawns-cli

10 stars 3 forks source link

connection test failed #12

Open zhxsglhq520 opened 1 year ago

zhxsglhq520 commented 1 year ago

{"happened_at":"2022-10-18T08:50:26Z","name":"not_running","parameters":{"error":"could_not_mark_peer_alive","message":"connection test failed"}}

HDTS1 commented 1 year ago

same here, running on armv71

itrustmchow commented 1 year ago

same here, running on synology nas

IPRoyal commented 1 year ago

Hey.

Please try the newest version from our dashboard dashboard.pawns.app!

itrustmchow commented 1 year ago

Tried the new version, still the same error

{"happened_at":"2022-11-15T07:00:12Z","name":"balance_ready","parameters":{"balance":"1.050 USD","traffic":"5.2547 GB"}} {"happened_at":"2022-11-15T07:01:58Z","name":"not_running","parameters":{"error":"could_not_mark_peer_alive","message":"connection test failed"}}

ifm90 commented 1 year ago

same error, managed to fix this by enabling execute container using high privilege on my synology nas but should apply to any docker installation

that said it is not recommended to run a container in high privilege

In addition to --privileged, the operator can have fine grain control over the capabilities using --cap-add and --cap-drop

@IPRoyal which capabilities are required so we don't have to enable privileged mode?

@itrustmchow works on my synology, hopefully works on yours too

Nanianmichaels commented 10 months ago

Hi, there.

Sorry for digging up this thread, but I'm also getting the {"error":"could_not_mark_peer_alive","message":"connection test failed"}} message.

I should note that this is even with the container having high privilege, and basically a "copy-paste" job from another machine running the container (minus the name, of course) which didn't need the high privilege flag.

How can we get around this issue?

fl0uf commented 10 months ago

Same here, even if i set the high privileged flag on the container, the client refuse to connect :

"happened_at":"2023-08-21T08:44:14Z","name":"not_running","parameters":{"error":"could_not_mark_peer_alive","message":"connection test failed"}}