You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The binary downloaded in the docker file seems to be invalid. When attempting to execute the file from docker-exec it prints in the console that the binary can't be executed.
To Reproduce
Steps to reproduce the behavior:
Try to configure a OpenVPN over Cloak using defaults.
Expected behavior
The client should be able to execute the binary
Smartphone (please complete the following information):
Device: Nokia 6.1
OS: Android
Version: latest
Server (please complete the following information):
This is the version supposedly used in the Dockerfile. After exchanging the binary with this one, you can go on the client to update the config of the Cloak server and restart it. It will restart properly. If it doesn't it might be necessary to manually generate and add the private key in the config file in /opt/amnezia/cloak/ck-config.json.
What's strange is that technically the url I used and the one used in the Dockerfile should be the same. So maybe the Curl corrupted the file somehow or there would need for a checksum to check that the file we downloaded is the expected one?
The text was updated successfully, but these errors were encountered:
Describe the bug
The binary downloaded in the docker file seems to be invalid. When attempting to execute the file from docker-exec it prints in the console that the binary can't be executed.
To Reproduce
Steps to reproduce the behavior:
Try to configure a OpenVPN over Cloak using defaults.
Expected behavior
The client should be able to execute the binary
Smartphone (please complete the following information):
Server (please complete the following information):
Additional context
While the docker file seems to download the wrong binary for the ck-server, the url pointing here has the right binary. https://github.com/cbeuw/Cloak/releases/download/v2.5.5/ck-server-linux-arm64-v2.5.5
This is the version supposedly used in the Dockerfile. After exchanging the binary with this one, you can go on the client to update the config of the Cloak server and restart it. It will restart properly. If it doesn't it might be necessary to manually generate and add the private key in the config file in /opt/amnezia/cloak/ck-config.json.
What's strange is that technically the url I used and the one used in the Dockerfile should be the same. So maybe the Curl corrupted the file somehow or there would need for a checksum to check that the file we downloaded is the expected one?
The text was updated successfully, but these errors were encountered: