-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenSSL errors when connecting proxy #151
Comments
Hello, I believe #126 fixed this issue and added a |
I'm seeing the same behavior with the latest tag as well
|
There may be minute differences between the Ubuntu images depending on the arch, which may not end up giving openssl enough context about which cert stores to use for verifying server certificates. Can you try appending |
adding |
closing this issue, feel free to reopen if you have any other inquiries. |
Wouldn't it make sense to update the container so the default args work? |
I stumbled on this and got lucky with @awwithro 's answer. Something maybe is still not updated. Wouldn't it be a bad idea to update the documentation? |
Hi @utezduyar . Thanks for pointing this out. We'll update this to the README documentation as well. |
I also found out about this flag: --destination-client-type V1 that is needed to make the current aws console work. Maybe consider adding it too to the documentation. |
@utezduyar That is already present in the documentation at appropriate places, but feel free to let us know if you want it to be highlighted at some other place as well |
Describe the bug
The proxy throws a SSL handshake error when connecting
To Reproduce
docker run --rm -it --entrypoint=/root/bin/localproxy --network=host public.ecr.aws/aws-iot-securetunneling-localproxy/ubuntu-bin:arm64 --region us-west-2 -s 5555 -t <my_token>
results in
Expected behavior
I would expect this to connect successfully
Also, the entrypoint is pointing to /root/bin instead of the proxy
Actual behavior
The above error is thrown repeatedly
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: