-
Notifications
You must be signed in to change notification settings - Fork 16
Issues with self signed Certificates in Dev Environments #9
Comments
Hi, Are you using an old version/config files? Take a look at this issue, does this help? #7 |
You're right. I was using an older version, since I'm using your great tool until you presented it in DevCon last year. Unfortunately it still won't work in my current environment. Setting the "allowSelfSignedCerts" parameter removed the "DEPTH_ZERO_SELF_SIGNED_CERT" but now I get an "java.lang.IllegalStateException". On the production server (with the officially signed certificate) there's still the "Unable to check CSRF token" Error. Sorry for bothering you, but I'd really like to use your tool again in my current project as we massively use ddm stuff in that project. |
Am I understanding you correctly if I say that:
Correct? Will you be joining DevCon this year? |
Correct! BTW: When I install you Tool using “npm install –g “ there are lots of Maybe we’ll find a view minutes next week in Darmstadt, then I may show you Kind regards Peter Von: Emil Öberg [mailto:[email protected]] Am I understanding you correctly if I say that:
Correct? Will you be joining DevCon this year? — |
Cool! Let's solve this as DevCon! Grab a hold of me if I don't get to you first! |
I'm unable to use your great Tool in our Project Setup, because all our Servers use SSL Certficates. On our Dev Servers with self signed Certificates I see this Error Message:
Getting data from server
Downloading id's
Error
Unknown error: {"code":"DEPTH_ZERO_SELF_SIGNED_CERT"}
On the Prod Server, which uses an official signed Cetificate I see this one:
Getting data from server
Downloading id's
Error
Unable to check CSRF token
Any Ideas on how we could use the Tool with secured Connections?
The text was updated successfully, but these errors were encountered: