-
Notifications
You must be signed in to change notification settings - Fork 1
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
Curl errors out in the handshake phase #1
Comments
I have updated the docker-compose.yml file with an updated configuration. Could you please try again? Please issue a docker pull first. |
Thank you for the lightning fast response :) |
I cannot reproduce but I suspect it's due to the self-signed certificate being created with an obsolete cipher which is no more supported by your curl versions. I will try creating new certificates and see what happens. |
I updated both key and certificate, please issue a "git pull" and tell me if it makes any difference. |
I finally got it to work by making the following changes to the docker-compose file that was present at the repo prior to your first commit since I posted this issue, in addition to incorporating the new key and certificate:
To prevent this issue from re-appearing in the future, can you recommend a way in which I can create the key and certificate myself? |
I have followed the README section (i.e. git clone repo -> docker-compose up -> curl --insecure https://localhost/ping) in order to set up the complete NGINX, RESTHeart and MongoDB stack.
I can access the RESTHeart server via http://localhost:8080/ping in an unsecured way.
However, as soon as I use curl --insecure https://localhost/ping, curl errors out both in Windows 10 Enterprise and a Ubuntu 20.04.2 LTS VM.
Windows 10 Enterprise
Ubuntu 20.04.2 LTS VM
Unfortunately, neither nginx or restheart recognize the https call (i.e. do not log an exception in both normal and debug logging mode).
In case you know of a way to solve this problem, please attach a response to this issue report.
Regards,
Bram
The text was updated successfully, but these errors were encountered: