For some reason, Firefox today started issuing warnings about the SSL certificates on our web applications, but supplies very little information. Everything works fine in IE/Edge and Chrome. The application is at https://ps.ecco.com
How can I find out more about what's going wrong with the certificates and how do I solve the issue?
Related
I am trying to capture https traffic from a specific application on IOS. It's not working. I went through all the legit steps and 1. Installed Bouncy Castle, installed IOS compatible certificate on IOS device, then told it to use my computer as a proxy, and trusted the certificate on IOS. I can now decode "some" https traffic but it isn't decoding the traffic from the app i'm trying to sniff the api from.
I did this exact scenario on android with mixed results because android stored the certificate in the "user" storage so i had to actually patch the apk i was monitoring. I was under the impression that jumping through hoops like that weren't necessary on IOS though. Any ideas?
Note: A fiddler everywhere answer is fine too. I have a trial set up to test it.
I installed SSL letsEncrypt via Heroku dashboard. Everything works perfectly fine on Mac.
However, if you use Windows, the status bar shows that it is NOT secure which ultimately breaks the site when you try to submit forms and access jquery features...
Anyone experience this before? Is there a solution or should I just buy an SSL ticket to resolve this?
The site is https://www.givingdocs.com
I am running a local development website. The certificate securing it is issued by my own internal certificate authority. I have added the certificate authority to the MacOS keychain and marked it as trusted.
This used to work. Over the weekend, it stopped working. I would love to say that I've changed nothing, but obviously something has changed. Nothing specific comes to mind (perhaps a Chrome auto-update after a restart?)
I am on Chrome Version 59.0.3071.115 (Official Build) (64-bit)
I have checked the local site with Opera and Firefox and it loads securely as intended. (I have added the CA cert to the respective trusted roots for each browser). Safari works well too. Only Chrome is giving me grief.
If I look at the developer tools, the security panel is sending mixed messages. It says the cert is valid, but complains that the page is not secure. It is not possible to view the cert:
#dorian is right. The issue is explained in https://bugs.chromium.org/p/chromium/issues/detail?id=715969 . It was not the TeleText string bug that is described in the beginning. Rather, it was that I had generated a version 1 SSL cert, while it should have been a version 3 cert.
Instructions for creating version3 certs with OpenSSL:
Creating an x509 v3 user certificate by signing CSR
I'm facing an issue with self-signed certificate in Windows Phone 8 app. I have installed the certificate (.p7b) manually and it works fine when I browse through the site in IEMobile.
But when I visit the same, using the WebBrowser control in my hybrid app, The certificate error still shows and can't be ignored, even after tapping Continue. Isn't the Certificate installed System-wide or is it just for IE?
I have referred many links regarding this but in vain. Any help would be jighly appreciated. Thank you.
I had the same issue, and it turned out to be a hostname mismatch between what the certificate contained and the address I was using to connect to the server. If those match, and you install the P7B file on the Windows Phone device, then you should no longer see certificate warnings.
For the full details of my issues and solution, see this thread on MSDN.
Hello people from the web,
I am experiencing a weird issue with self signed certificates. Since I upgraded to OSX 10.9 (Maverick) I am not able to connect to an HTTPS site protected by a self signed SSL certificate. The only remaining browser on my computer able to do the trick is Firefox (24). Chrome (30) and Safari (7) cannot.
Have you experienced the same issue? Have you found a solution?
On my quest for a solution I found this article:
http://curl.haxx.se/mail/archive-2013-10/0036.html
However it seems to me this is more the webkit common engine causing the issue. Is it possible that Webkit has become more picky with SSL Certificates? In which case how to generate a cutom one that would suit Safari 7 and Chrome 30+?
Thank you for any help you could provide :)
Oscar