I'm trying to push my project into my Bitbucket repository but it doesn't let me do it, it throws the following error message:
fatal: unable to access 'https://arfi#bitbucket.org/arfi/quaba.git/': SSL certificate problem: unable to get local issuer certificate
What must I do? I don't understand why is this falling now, before it used to work without any problem. Anyone can help me?
I've already solved my issue.
I had to open Sourcetree, go to Tools -> Options -> Git, and activate the option 'Disable SSL certificate validation'.
Now I can push my project and everything into my Bitbucket Repository.
Related
I have been going around and around with this issue. I can create a dev-cert using dotnet dev-certs https --trust but the certificate only appears in the Personal certificates folder. If I try copying it to the Trusted folder it disappears on refresh. I have watched videos of people doing this on YouTube and it works so I'm not sure what is wrong with my PC/install.
Running my code and hitting the route in Postman returns a 500 error and UntrustedRoot.
I have tried this using a local user account and my admin account. I have also tried creating a certificate and importing it using OpenSSL following guides I have found, but still no luck.
I am running Windows 10 Pro on a new build PC. Windows was a clean install with a new licence.
I really don't want to have to purchase a signed certificate just to do development on localhost as that seems a bit overkill.
Any suggestions?
tl;dr try disabling your anti-virus before creating certificate!
I finally stumbled upon the answer; my anti-virus, WebRoot. I was following a YouTube tutorial on how to add a custom certificate to Kestrel and in doing so I discovered that WebRoot was blocking access to the hosts file. Disabling the av allowed me to update that file but also, it then allowed trusting of the dev-cert generated by dotnet dev-certs https --trust.
Not sure how I can prevent this in future other than temporarily disable the av before creating a certificate. Frustrating that the av doesn't warn me and there doesn't appear to be an obvious setting to allow this to happen.
I'm struggling to use AWS Cloud Former to generate a CloudFormation template. I have already launched the Cloud Former stack twice and attempted to connect to the associated DNS for the EC2 instance generated each time and keep receiving the error pictured below.
I have already tried to create a new SSL certification for the EC2 instance via AWS Certificate Manager, but AWS does not allow this for EC2 instances. I'm not very familiar with SSL/HTTPS processes and would appreciate any guidance on next steps I should pursue to address/troubleshoot this.
Upon further research into this, I have found the following issue:
Specifically, I'm seeing the following SSL certification issue:
Has anyone else seen this yet with CloudFormer recently?
CloudFormer uses self signed certificates that are generated by the stack. This is the normal browser warning when the browser encounters a self signed certificate. For your purposes, you can simply click on the link at the bottom (Proceed to EC2-xxx (Unsafe)) of the warning page, and ignore the warning. You will connect successfully in spite of the warning.
SSL certificates require a domain. On AWS you can set one up with the certificate manager, but it will still have an issue until you correctly configure Route 53 on AWS as well.
I am posting this question on SO instead of ServerFault, because all my previous efforts to get Magento 2 issues sorted out, ended up being hacking some or other code in the Magento or template source.
I have configured a basic install of Magento 2 with a theme for a client.
Magento is running on IIS and Windows. (Not WAMP), shared IIS hosting on windows (My own server).
I configured the shop to use SSL, and the complete shop runs over SSL without any issues.
However, when trying to use the market place, I get a weird SSL issue:
"SSL certificate problem: unable to get local issuer certificate"
This error is shown on the Magneto shop (which is currently running over ssl), when trying to sign in to the market place.
I have found lots of hits on this issue, but all answers seem to lead to a self-signed certificate that isn't trusted or adding intermediary and/or root certificates. This is all based on XAMP, WAMP or native 'nix installations.
I do not understand what the exact issue is. I also do not know how to troubleshoot this further as the error description is very vague.
I would appreciate some feedback.
Thanks
This error happens because cURL cannot find a cacert.pem file from which take the trusted signatures.
There are some ways to set this file in cURL:
• Pass the cacert.pem file path directly to cURL when making the call;
• Set the path to the cacert.pem file in the php.ini.
You could follow below post:
• https://serverfault.com/questions/633644/adding-a-self-signed-cert-to-the-trusted-certs-within-curl-in-windows
• https://magento.stackexchange.com/questions/97036/magento-component-manager-ssl-certificate-problem-unable-to-get-local-issuer-c
• https://mage2.pro/t/topic/988
Regards,
Jalpa.
I'm trying to use charles SSL proxying on my Huawei Honor Bee phone. When I try to install the certificate from charlesproxy.com/getssl, I get an error toast saying, "Couldn't install because the certificate file couldn't be read". I've tried on different browsers, but no luck. How can I install the charles certificate? Please help.
Thanks
On your phone, Go to Settings > Security > Install from storage.
Locate your certificate file and install it.
You can go to help menu and choose "export root certificate" then just send this file to the device.
An image to exemplify what I mean: https://tppr.me/ymh8W
For Mi4i, Go To Settings -> Additional Settings -> Privacy -> Install From Storage -> Install certificate which is present in your Downloads
To verify if it's installed Go to Trusted credentials -> Click on User tab -> Check if certificate exists or not.
I want to push to an internal (inside the LAN) nuget repository (hosted on Nexus version 3) from a Windows 2012 R2 server. Is it possible to push to this repository and ignore ssl verification like you can with git push?
for example with git you can do git config http.sslVerify false, can a similar thing be done with nuget push command? I had a Google but nothing came up.
My nuget command is:
nuget push my.nuget.package.version.nupkg -Source https://nexus.repo.local/repo -apikey {apikey}
I currently get this error: The remote certificate is invalid according to the validation procedure.
I haven't found a way to do what you want (boy would I like to), but if you can install a self-signed cert with your own CA, you can install that CA as trusted on the client to circumvent the issue.