-
Notifications
You must be signed in to change notification settings - Fork 123
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
SSL routines:ssl3_get_record:wrong version number #573
Comments
Hey @mpalourdio, it looks like you try to access the proxy using HTTPS instead of HTTP. Thanks |
The preflight checks actually do not use request but Axios instead. So might be something else going on here. |
Hi, Sorry for my late reply (holidays). I wanted to send a request, but I do not have a Snyk Organization ID for the moment. We'll be onboarded next week. Before that, I wanted to anticipate the installation :/ FWIW, I have just set the |
Hello, The token has been provided. Now the trace, when testing the connection from snyk to our broker is
Note that we have set too Because we need to bypass our proxy to reach |
Update, We still have the followings traces at the very start, but it seems OK anyway. So not sure if this is relevant or hiding something weird.
|
@mpalourdio, thanks for keeping us updated. If the issue is solved on your side, we can close the issue. |
Thanks for feedback. I am confident this will be ok now. |
Hello,
docker image :
broker:4.157.1-bitbucket-server
We have installed the snyk broker on our Openshift instance (We do not have a token yet). Outbound connection to snyk is performed through our enterprise proxy (the url is whitelisted as expected)
But the broker fails because of
SSL routines:ssl3_get_record:wrong version number
Running the docker image outside of Openshift leads to the same error.
The proxy configuration is OK, because running this from the node cli works as expected from the container itself
Response
Thanks
The text was updated successfully, but these errors were encountered: