I am trying to run an Asp.net Core application using Visual Studio 2019 in Chrome browser but i'm getting the following error:
"This site can’t provide a secure connection
localhost uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH Unsupported protocol The client and server don't support a common SSL protocol version or cipher suite."
I tried
repairing IIS Express 10,
clearing browser data and certificates cache,
deleting .vs folder,
But My .NET Core web apps are not working in Chrome.
How to solve this??
Try putting this URL in your Chrome browser to turn this flag on and then relaunch Chrome:
chrome://flags/#allow-insecure-localhost
Related
I have and old app made it in VB.NET 2010.
The App have a GUI and connect to a SOAP service(asmx) on a remote server that runs on HTTPS connection.
A few weeks ago the service provider just changed the web address so I updated the app and works ok in my PC, where VB.NET is installed, and also on a PC that never had that App installed before. But when I try to run the App in the PC that has had that app running for years; it does not work; instead I get this error.
Could not establish secure channel for SSL/TLS with authority....
I think that probably is a .config or a .xml file that the older App created and is messing something.
I also tried disabling the Windows 7 firewall with no luck.
Any clue please?
EDIT:
I just sniffed the connection and the PC that doesn't validate the certificate is trying to get some cab from
.GET /msdownload/update/v3/static/trustedr/en/authrootstl.cab
You probably think that this is a misbehaving crawler problem but this CloudFlare website:
Blocks Internet Explorer on Windows 10 desktop (uses Windows API for HTTP)
Allows Edge on Windows 10 desktop (uses Windows API for HTTP?)
Blocks my crawler on Windows using WinInet Windows API for HTTP
Allows my crawler on Mac using Mac API for HTTP
Accordingly to this Internet Explorer 7 on Windows Vista should be support on even free CloudFlare:
https://support.cloudflare.com/hc/en-us/articles/203041594-Cloudflare-SSL-cipher-browser-and-protocol-support
I am in preliminary research phase, but it feels like a certificate issue. I have not experienced this problem before on any website when using Windows 10. (But yes, older versions of Windows can have similar problems to certificate problems)
Any ideas? I have not implemeted HTTP2 part of Windows API - is that a possible explanation? Would just be a bit odd to require that so.... But could possibly explain why Edge and not IE works.
I asked the website owner and the website was setup to only support TLS 1.3 and not accept TLS 1.2 --- TLS 1.3 support is still experimental in Windows 10 (internet options)
All Mac computers at my job were upgraded to macOS Mojave four days ago. Since then, no Mac users have been able to connect to any MarkLogic WebDav servers. PC users are able to connect no problem and so are Macs that are still running older versions of macOS.
Also, now when trying to connect to the WebDav server through Finder, we get this pop-up message:
"Do you want to send your name and password in a way that is insecure?
The baseURL provided uses an unsecured method for network communication. To use a secure connection, you must use a server that supports SSL."
Has anyone else encountered this issue? Is there a setting in MarkLogic that we need to change?
Thank you!
It sounds like the primary change is that macOS now issues a warning when you are connecting in a way that could send your password in clear text.
MarkLogic supports WebDAV over SSL, so to remove the warning, you will need to enable SSL on your WebDAV app server.
The MarkLogic Security Guide goes into the details of Configuring SSL on App Servers.
You can also check the WebDAV Server Configuration Help for a complete list of the available options for a WebDAV app server.
It was an Apple issue. We installed the Mojave 10.14.6 supplemental update and the problem fixed itself. We're able to connect to the WebDav servers no problem. Thanks!
I am trying to integrate sonarqube(version 5.1.2) with intellij(2016.2). I have added sonarLint plugin.
when I am trying to add a sonar server to the sonarLint settings it asks for username and password for sonar server and other details like url.
But it somehow is unable to connect to the sonar server and gives error :
Fail to request : https://example.com/api/system/status
The latest version of SonarLint only supports SonarQube 5.6+ (5.6 is the current LTS version).
Apart of that, you might also be facing a problem with server SSL certificates. SonarLint will try to validate the server's SSL certificate using the JVM's truststore. So if your SonarQube server uses an SSL certificate, you might need to install the CA certificate in the trustore of the JVM used by IntelliJ.
Due to a limitation in SonarLint, certificates configured within IntelliJ aren't supported by SonarLint: https://jira.sonarsource.com/browse/SLI-75
I ran into something similar myself using SonarLint 3.1 and SonarQube 6.7.
In IntelliJ I kept running into this error message
Failed to connect to the server. Please check the configuration.
Error: Fail to request https://<SONARQUBE>/api/system/status
However I could access that URL through my browser without any issues.
When you WireShark the requests coming from the browser and the IDE you can see that the cypher suite is quite different and that the IDE plugin gets a TLS handshake failure.
That lead me to discover that Java still ships with limited strength cryptographic functions. That’s either because of US export policy or because nobody has gotten around to fixing it. The internet isn’t quite sure.
Either way, you can download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files from Oracle: http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
Once I installed those onto the IntelliJ JVM, I no longer got the underlying TLS handshake failure when trying to connect to SonarQube and the connection works.
I just had the same error. After many tries, it turned out that I had to enter my login (it's a domain account) in the upper-case. Looks like login is case-sensitive.
It's my work account and I was using it always in lower-case, so it's quite surprising, but worked nonetheless.
Sorry for late response, but you can try to follow this instruction.
You can find it here. Download the Zip and follow the instructions in the pop-up after you click download.
Versions: SonarLint - IntelliJ IDEs Plugin | Marketplace (jetbrains.com)
I'm working on a web application in JSP and my web container is Apache Tomcat 7.0.2 (Its portable cross-platform version). As I've made extensive use of HTML5-CSS3 and my target browser is Google Chrome, I'm able to run the the Apache server only in Opera web browser, neither of the remaining installed browser run it.
Here's the steps I have followed to start the server in my Windows 7 machine.
-Installed the Apache Tomcat service in Windows from apache-tomcat-7.0.2/bin/service.bat
-Started the service with tomcat7w.exe
-As my default port is 8080, I open 'http://localhost:8080/' in various web browsers, and I could see Apache Server Homepage with same address only in Opera Web Browser (11.01), neither of other browsers installed can open it (Chrome 9, Firefox 4 Beta 11 or IE8) and show standard page not found message.
-I also tried other port numbers, but none of them worked.
What can I do to make Apache run in every browser installed in my computer?
I have my computer dual boot with Windows 7 and Ubuntu 10.10, and in Ubuntu, every web browser installed can run Apache once I start it, but same is not working in Windows.
Update:
I have also tried apache's windows-only installer of version 7.0.8 and changed the port number during installation, but still I can't run it on any other browser expect for Opera...
Any help will be appreciated............
Thanks.
Check your hosts file under C:\Windows\system32\drivers\etc\hosts to make sure that the entry for
127.0.0.1 localhost
is intact. Also see that if you are behind a proxy server, the settings allow for localhost to be bypassed.
Congo!! finally got it done, instead of localhost, it works with 127.0.0.1 (which is localhost anyway)
So those who are facing similar issues, as suggested by adarshr, go through your hosts file to see if localhost is correctly addressed to 127.0.0.1, or if you don't want to edit that file, you can still get it done by simply using http://127.0.0.1:8080/ instead of http://localhost:8080/. Please be sure about port number you are using, in my case it was 8080, it might vary depending on how you've configured.