What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi guys, i want to configure our wildcard ssl certificate in local docker env.... i replaced the def
Hi guys,
i want to configure our wildcard ssl certificate in local docker env.... i replaced the default.crt and default.key with our crt and key files... and adjusted some dn information in v3.ext but when i run the bootstrap command i get always the following error:
Generating a RSA private key ............................+++++ ..............................+++++ writing new private key to '/data/deployment/context/nginx/ssl/ssl.key' ----- Signature ok subject=C = US, OU = [www.digicert.com](http://www.digicert.com), O = DigiCert Inc, CN = RapidSSL RSA CA 2018 Getting CA Private Key C = US, OU = [www.digicert.com](http://www.digicert.com), O = DigiCert Inc, CN = RapidSSL RSA CA 2018 error 20 at 0 depth lookup: unable to get local issuer certificate Taking predefined CA certificate Generating PFX file for CA to import on client side Checking certificate chain error /data/deployment/context/nginx/ssl/ssl.crt: verification failed
I just miss/forget something?! any help would be appreciate.. thanks!
Comments
-
Hello Giovanni,
What problem do you solve?
0 -
Hi Mike, we want just use own ssl certificate for our docker instance... and not the spryker one...
0 -
Hi Giovanni,
Sorry for delay - a lot of work last days.- It would be interested to see the changes you’ve applied.
- It would be good to see the solution if you have the final one already.
- Would you be able to give background of the issue and acceptance criteria for the solution for us to implement in docker/sdk?
0 -
Hi Mike,
no problem 😉as already described i wanted just run our local docker env with ssl but with own wildcard ssl certificate...
i replaced the crt and key files under
docker/generator/openssl
and changed the informations in v3.ext but something not working properly... the verification failed..i write in channel if maybe there is a docu how to make this or what we have to take care...
0 -
Certificate you’ve replaced is CA certificate. And I assume that you’ve replaced it with SSL certificate that should be wrong.
0 -
So if you have your own SSL certificate - just replace generate.sh with a script that copies them as “${DESTINATION}/ssl.crt” && “${DESTINATION}/ssl.key”
0 -
As resume, I would propose the changes in docker/sdk:
deploy.yml
docker:
ssl:
enabled: true
certificates:
- mypath/ssl.crt
- mypath/ssl.keyWe will consider to put such changes in our backlog
0 -
@UPZH5HHEV Please, note the case. Thank you very much.
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 69 Spryker News
- 894 Developer Corner
- 757 Spryker Development
- 83 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 22 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 68 Spryker Safari Questions
- 50 Random