I am trying to build a Blazor application and I always get the following error :
"This site can’t provide a secure connectionlocalhost 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."
My Chrome browser is up to date. I tried with Edge but the same error !
I tried the following link, too :
https://phoenixnap.com/kb/fix-err-ssl-version-or-cipher-mismatch
Until a day all was working fine and I don't know what happened...
If I run the same application on another Windows 7 PC, it is working fine...
Can you help me, please ?
I will put here a screen capture :
Same problem for me.
Working with VS19
Tried a lot of things such as:
deleting localhost certificates,
repairing IIS Express 10,
clearing browser data and certificates cache,
deleting .vs folder,
allowing every TLS and SSL options in the browser
My .NET Core web apps are working under IE. So my guess is also that it's a Chrome update problem. But I haven't found how to fix that. :-(
Experienced the same issue. Managed to get it sorted by downloading IIScrypto and enabling the Best practices TLS and Cipher versions.
You can use firefox
Firefox: about:config "tls" > security.tls.version.min=1. Reset to 3 after completion.
Install Firefox.
Type "About:config" in the address bar and hit return.
Click "Accept the risk" and continue.
Type "tls" in the search bar and hit return.
Click the pencil icon at the far right of "security.tls.version.min" to edit the cutoff setting prevening your login, which is currently 3.
Type "1" and hit return.
I have the same problem. I work with Windows 7 Visual Studio 2019 browser chrome. The problem was solved in this way:
Open the project properties - debugging - uncheck the box "use SSL".
Related
I'm trying to setup webdeploy on IIS8, but why am I getting 404 when accessing both https://[servername]:8172/msdeploy.axd and https://localhost:8172/msdeploy.axd locally.
I've installed management service.
I've installed webdeploy 3.5 using web platform installer. In Program and Features a changed the instalation of webdeploy to include all features including the handler.
In IIS Manager I've chosen Configure Web Deploy Publishing for default website's context menu.
I've restarted management service.
when i tried https://[servername]:8172/msdeploy.axd I was asked to enter credentials and accept the certificate. after that I got 404.
I've uninstalled webdeploy and installed using MSI manually including all features.
restarted entire server.
getting 404.
I don't believe you can open the service from a browser. I attempted that against a dev server that we deploy to many times a day and also received a 404. I would try deploying from VS instead as a test.
Also if anyone comes here and is using Visual Studio Publish dialog and the "Validate Connection" button fails: do NOT use the button when creating. Just click Ok, then Edit (in More actions menu).
In the Connection tab, click Validate Connection. This time it will asks you to accept an invalid certificate (since you likely self-signed it on your server). Accept it and the connection should go through.
I have set-up my Windows 10 Home PC as a web server to do some development work. I need to use Anonymous Authentication but I'm having issues with 401.2 errors.
401.2 Error
The IIS log gives me:
2015-11-01 18:29:12 192.168.1.14 GET /temp/index.html - 80 - 192.168.1.14 Mozilla/5.0+(Windows+NT+10.0;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/46.0.2490.80+Safari/537.36 - 401 2 5 0"
It's a simple index.html page containing just "Hello World!
I've been through the MS troubleshooting article here but it doesn't help support.microsoft.com/en-us/kb/907273
I have posted the IIS set-up, folder set-up, Access control list on the folder and the AppPool Settings:
Link to settings
Thanks
Jeff
I had the same problem and struggled for couple of days. Finally figured it out that one of the reason to get the 401.2 error was because Authentication modules were not installed.
Make sure you have your desired Authentication modules(i.e. Anonymous Authentication) installed in IIS.
To verify go to IIS Manager -> Select root -> Select Authentication.
If it's not showing your Authentication type then go to control panel -> Add/Remove program or goto Run -> type "appwiz.cpl" -> enter to open the add remove program wizard.
Go to windows features -> IIS -> Authentication
Note: If you only want to fix this error in Visual studio for development purpose then you don't need to install those modules. In case you're using IIS express simply go to project properties by pressing "F4" and change the Authentication type from there.
So I gave up on trying to resolve this. I ended up uninstalling all IIS features and re-installing from scratch. After re-installing Anonymous Authentication now works!! :-) If turning it off and turning it back on again doesn't work then try uninstalling and reinstalling! IT support at its best!!
I have a site set up locally to do development on it and I have added it to iis and edited my host file with the url (see below). However, when I browse to the url I only get the "hmm, we can't reach this page" message.
The site works well in all other browsers including ie 11 so I was wondering if there are any settings to get local sites to work on edge.
I have been searching and could only find this related post, but the accepted answer on that makes no difference to me as the option is already checked on my edge. I have also tried the rebooting and flushing my dns but both didn't work.
I am using windows 10 and iis version 10 build 10240
Hosts File
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 localhost loopback # tried with and without this as thought it may have something to do with the loopback option in edge
127.0.0.1 test.local
127.0.0.1 dev.local
Other links I have managed to find - no solutions though and the second one seems to suggest that we just use ie11:
Why does Microsoft Edge open some local websites, but not others, where the domain name is routed to 127.0.0.1 in hosts file
https://social.technet.microsoft.com/Forums/en-US/246298d8-52c1-4440-8d7f-05329d50e653/edge-browser-hosts-file?forum=win10itprogeneral
Update
Could it be something to do with the fact the site app pool is running under my work account instead of IIS or Network services (I cannot run under the latter 2 as they don't have the correct privileges to browse certain folders on my computer)
Update 2
For anyone coming to this who has tried everything below. I have found out it may be something to do with my windows 10 installation - My first install on the machine was windows 8. I then upgraded this to 8.1 and the up to 10 when that came out.
Having had issues with a few other things, I bit the bullet and did a completely fresh install of windows 10 and voila, everything works perfectly!
May be a bit drastic, but if all else fails...
Update 3
I recently got a new work machine and had this problem all over again, tried everything but still couldn't get it to load - turns out that the work proxy was causing the issue so if you try everything below and have a proxy, check the proxy is not blocking it
The network is blocking loopback as a security measure in Windows 10, you need to make an exception by running this command for IE Edge in elevated privileges
CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"
This worked for me;
Open the Internet Options dialog
Go to the 'Security' tab
Select the 'Local intranet' zone
Click the 'Sites' button
Check the 'Automatically detect intranet network' box
Edge can now find my local website (with a single word name!)
I figured it out and posted the answer over at my question: Why does Microsoft Edge open some local websites, but not others, where the domain name is routed to 127.0.0.1 in hosts file
(Assuming your issue isn't simply the loopback checkbox in about:flags)
The fix is to remove the domain names from your trusted sites list for the trusted zone. That's it. It took me two weeks to figure this out.
Open the Internet Options dialog (just ask Cortana or use windowskey+s)
Go to the Security tab
Click on the Trusted Sites zone
Click the Sites button
Remove the troubled domain names from the trusted sites list
Click Apply and then close the dialog
Open Edge (or restart it if it is already running) and try your site
Follow these steps:-
Step 1: Run Command Prompt as Administrator
Step 2: Write command "CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"" and press enter. It returns OK.
Step 3: Restart Microsoft Edge or Internet Explorer to view your web page
I hope, this helps you.
Thanks!!!
Internet Options / Local intranet sites
This works for me:
On my Windows 10 machine with Edge these are my results:
127.0.0.1 local # Hmm, we can't reach this page
127.0.0.1 my.local # Works :)
127.0.0.1 my.local.ca # Works :)
127.0.0.1 test.local # Works :)
127.0.0.1 dev.local # Works :)
In your hosts file, use a fully qualified domain name (FQDN) instead of a nickname. In other words, include a dot. Then it will work in Edge.
My environment is also Windows 10 with IIS 10.0.10240.16384 installed.
And these are my settings within Windows Features > Internet Information Services > World Wide Web Services
The Application Pool that I am using has its identity set to the account with which I log into my computer. It also works, though, when the identity is ApplicationPoolIdentity. In other words, both the EdgeHostsFile and the DefaultAppPool in the image below work on my machine.
And as you have already posted, my about:flags look like this with the allowance of the localhost loopback.
My Edge version is 20.10240.16384.0
After you have tried all instructions or settings from other users but it doesn't work, try this:
Open Internet Options. (type "in" in "Search Windows/Cortana" if you using Win10)
1. select "Security" tab.
2. click on "Local intranet"
3. click "Sites" button.
4. Uncheck "Include all local (intranet) sites...."
5. Uncheck "Include all sites that bypass..."
- click "Advanced" button, remove all site address which defined in %windir%\System32\drivers\etc\hosts
6. & 7. OK
8. Restart Microsoft Edge or Internet Explorer.
In addition to adding the hostname to the hosts' file, go to Internet Options and add the URL to the trusted sites under the Local Intranet. That works for me.
I faced this error when i try to run my application locally using IISExpress. I have changed below configuration it fixes the issue.
Go to IISExpress config file which you will probably found in Documents-->IISExpress-->config--> applicationhost.config
Move the NTLM provider value above Negotiate like this
<windowsAuthentication enabled="false">
<providers>
<add value="NTLM" />
<add value="Negotiate" />
</providers>
</windowsAuthentication>
It fixes my issue. And i was able to browse my application with out any error in microsoft edge.
For IE specifically, on this page...
I found an answer similar to others, but a slightly different command:
CheckNetIsolation LoopbackExempt -a -n=windows_ie_ac_001
...As admin, like the other solutions.
I don't know if I found a different answer because I was searching for Internet Explorer specifically, but it worked anyhow.
I tried all the options mentioned , but no success with IIS Express !!!
BUT
just a small thing i did (i don't know why) . and the stuff started working for me
I deleted the entire .vs solution folder. which has the applicationConfig for solution , to be used with IIS Express ....
IT Worked !!! i am not sure if its the combination of above mentioned stuff and this file, or just this file...
Up until recently, everything worked just fine.
However, now, I can no longer connect to Team Foundation Service unless the Fiddler is opened?!
A couple days ago, I've setup the Fiddler according to the configuration tips DecryptHttpS and tip2 and the issues began to occur.
This is the message I get when I try to connect.
I've tried
turning off decrypt https
removing all Fiddler certificates
uninstalling Fiddler
removing all cookies from IE
...
and many other things that crossed my mind, but with no success.
Seems like VS just can't get to TFS without it.
Meanwhile, I can view the TFS perfectly from browser. (And yes, opening a new instance of VS from home page of TFS doesn't work either)
Any suggestions?
Finally managed to get to the bottom of this.
The issue was caused by the following entry in the machine.config in C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config and C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config
<system.net>
<defaultProxy enabled = "true" useDefaultCredentials = "true">
<proxy autoDetect="False" bypassonlocal="False" proxyaddress="http://127.0.0.1:8888" usesystemdefault="False" />
</defaultProxy>
</system.net>
Once I got rid of it, everything started working again.
Typically, this would indicate that the client is configured to use a proxy at 127.0.0.1:8888 even when Fiddler isn't running. Typically, .NET clients get their proxy settings from the system whenever they start.
Without Fiddler running, what are your proxy settings inside IE's Tools > Internet Options > Connections > LAN Settings?
If you start Fiddler, then untick File > Capture Traffic, then start your TFS client, do you see Fiddler capturing the client's requests even though capture is disabled?
VS 2012 does not make this easy. Try the following.
1. Shut down VS
2. Open IE
3. Clear your cache
4. Shut down IE
5. Open VS
In VS 2013, you would need to remove the URL from the connection dialog and re-add it.
I am facing a strange error in xpages. Whenever i preview any xpage in internet explorer I get error 500. I've tried this with new nsf, I created only one blank xpage with no elements and tried to preview, I got the same error.
I've also checked the "Display Xpages runtime error page" in xpages tab in Application Properties section but got the same 500 error.
(I am working on my local machine)
Url of my xpage:
http://localhost/test/testdb.nsf/testxpage.xsp
For every preview attempt log.nsf has below entry
04/17/2012 03:24:10 PM HTTP Web Server: Command Not Handled Exception [/test/testdb.nsf/testxpage.xsp] Anonymous
Below is the error on ie.
Error 500
HTTP Web Server: Command Not Handled Exception
Step 1: Go to the application properties and tick "Show standard error page"
Step 2: Make sure that your application is build (default autobuild in project is ON, but you never know)
Step 3: Try project clean
Step 4: Check the errorlog in data/domino/workspace/log
Step 5: Post your code here to have a look
Based on your description most probable reason is security: you have no right to run XPages on the server. Either sign with proper ID or manage to be in "Sign agents or XPages to run on behalf of the invoker:" field of server document (in Security tab).
Anyway, you should always look for the log mentioned by #Simon McLoughlin.
Try looking at the stack trace in C:/domino-Data-Directory/IBM_TECHNICAL_SUPPORT and the most recent xpages_...log file, generally a lot more helpful than the one line errors you get in other places
If you are working on Windows Vista/7 then for starting your Lotus Notes, right click on Lotus Notes icon and click on "Run as administrator". It works this way on my local machine. I guess this is due to UAC (User Account Control).
I guess that it is your Notes client. Then you need to check with your admin.
Some of the time, We do not have a sufficient privilege for data folder. I am also faced this issue.
Check your server port, probably it may 80. So some your application takes port 80 like face book, skype... So quit that process and try :)
Are you using Extension library in the application ?
Then you need to do a double installation, both the designer and the Client installation to be able to preview.
I'm experiencing the same issue with my server, I only did what #stwissel suggested and then restarted my server and it all worked, but in your case your running it locally try restarting you PC and hope it works.
Are you running Quicker? I found this article and thought it might help, http://www.zarazaga.net/web/z.nsf/dx/getting-error-500-on-opening-an-xpage