Im having problems with logging into Github Co-Pilot from within the IntelliJ co-pilot plugin.
Its without a doubt the certificate issue when im behind corporate firewall because when i try to login on an external network it works fine. I also tried to "Accept non trusted certificates" in intelliJ but that did not change anything
The network guy im working with is asking for a FQDN (Fully Qualified Domain Name) or something dynamic to work with in the firewall which im unable to give him as i cannot see anything in the intelliJ logs.
Does anyone have any info on this ?
Related
I followed the documentation on page and not able to make it working,
https://checkmarx.atlassian.net/wiki/spaces/SD/pages/1339490445/Setting+Up+the+IntelliJ+Plugin+v9.0.0+and+up
Got it working after adding required certs on machine.
PhpStorm version 2017.2.3:
I am suddenly getting notifications such as the screenshot below, and they're persistent:
I believe (as you may be able to gather from the image), that what is happening is that PhpStorm is trying to connect to the http://www.viridor.co.uk domain and then is being presented with an untrusted certificate from the (https) domain varient.
I keep telling PhpStorm to reject this certificate. I don't want it saved. But PhpStorm keeps bringing up this notice.
What I've tried:
I have read through the settings menu to see if I can find a way of sorting this but have not found anything suitable:
What I'd like to achieve:
Why does PhpStorm reject the certificate, can we edit these rejection criterias? this is the first time I've seen this and I'm sure PhpStorm has been checking a multitude of links from various project sites I work on. (please see below some certificate diagnostics)
How can I get PhpStorm to remember my rejection for this certificate?
If not, how can I turn off PhpStorm checking URLs outside the project scope (hopefully for just this project rather than all projects)?
Extra info:
I have run the url (viridor.co.uk) through the Qualys SSLTest and it came back
This server's certificate chain is incomplete. Grade capped to B.
source.
I would like to think that this certificates problems are the direct cause of this issue, but now I'd like to know how I can solve this issue.
I use Chrome in macOS Sierra 10.12.3. I guess I have already set up ssl for localhost long time ago. Now, both http://localhost/ and https://localhost/ in Chrome return the list of folders under localhost. I have created a nodejs app. So after typing npm start in a command line to run the server, we could open http://localhost:3000/#/home as frond-end in Chrome.
Now, for some reason, I need to make https://localhost:3000/#/home work in Chrome. At the moment, it gives This site can't be reached; localhost unexpectedly closed the connection error.
Does anyone know how to amend this? Should I set up something in mac or in the code of my app?
Edit 1: I have found this page: SSL/HTTPS server with Node.js and Express.js. So I generated the files and modified the node code. Now loading https://localhost:3000/#/posts/editor/ displays the page, but I want to remove the annoying Not Secure warning.
As the above screenshot shows, I was able to view its certificate (though there is an error ERR_CERT_COMMON_NAME_INVALID). I copied the certificate to the desktop and dragged it to login of the Keychain Access tool and modified its setting to Always Trust. I restarted Chrome, reloaded the page, but the Not Secure warning is still there.
Could anyone help?
There are actually lots of threads about this issue, which are quite confusing. I write the way that works for me.
I have finally followed this page to generate the files http://blog.mgechev.com/2014/02/19/create-https-tls-ssl-application-with-express-nodejs/. Note that I set localhost as Common Name (not sure if it's really mandatory).
In www of my MEAN project
var fs = require("fs");
var config = {
key: fs.readFileSync('key.pem'),
cert: fs.readFileSync('cert.pem')
};
var server = https.createServer(config, app).listen(3000);
In Chrome, I open https://localhost:3000/#/new, then I go to the Security tab of Dev Tools to view its certificate. Then drag the certificate to the desktop.
Double-click the certificate on the desktop, which opens Keychain Access. Make sure the certificate is in login (not necessarily system). If it's not, then drag the certificate in login.
Change everything to Always Trust
(maybe restart Chrome), after npm start the application, enjoy surfing https://localhost/#/new with Green Secure Light.
Are you sure you setup a Certificate Authority? Perhaps you only setup https in your code but forgot to setup a local Certificate Authority for your app to validate a certificate with. If this is the case please reference: http://www.techrepublic.com/blog/apple-in-the-enterprise/create-your-own-ssl-ca-with-the-os-x-keychain/
I have started looking into testing our site with BrowserStack.
However, I'm having issues with live-testing (as opposed to automated testing with Selenium, which mostly works fine) a site we're developing as we're serving it with a self-signed certificate.
Manually approving the certificate doesn't bother me as much as the fact that some Ajax request are failing (at least on IE10) due to security issues and this makes it impossible to actually manually test the site.
An acceptable solution would be to somehow add our self-signed cert. into the list of trusted root CAs. However, I haven't found out how to upload files into the BrowserStack test environment (not sure if that's even possible, really).
Any ideas ?
I contacted BrowserStack about this issue, and their formal response is:
"We currently do not support installing client certificates on the remote machines. However, this is on our list, and we’ll keep you posted."
Hopefully this issues will be resolved soon and I'll post a different answer here.
April 2021 update:
BrowserStack has shipped a toggle to trust self-signed certs.
It is available on iOS and Android devices for now.
When it happens, open the "Network" tab, and open in a new tab the request which is failing. If it is "just" a certificate issue, you would then be able to bypass the warning. Then, your request should work correctly.
When the "Cannot Verify Server Identity" dialogue pops up, click details, then 'Trust'. This will work if all calls are to the same domain as the website.
I have a live site running on cPanel. I would like to write some WHM plugins to extend WHM functionality. But the problem I am facing is I don't seem to find a way to get cPanel as a developer version - which I can run on a development environment, test it and then install it to production.
Any idea anyone?
There isn't a developer cPanel available, you could try having a test server/environment with cPanel installed, making the plugin etc and just testing live on that.
you could always open a support ticket with cPanel and see what the have to offer, they might have something which would work for you, but just isn't publicly displayed as such.