Amazon broke the proxy settings on the fire stick. It seems that the settings are being ignored and not applied.
Try setting the proxy with Charles (or whatever MIM proxy you are using) switched off. I had the same issue and once I switched Charles off the fire stick finally saved the settings.
You can set the proxy from adb shell and it will save but it will not show in the proxy panel of the firetv stick and it will still work.
I'm trying to disable the IIS localhost from Windows, without success. The only thing I'm finding is, that you have to disable the IIS option that's found in the Windows-Features. I disabled it and restarted my computer multiple times, but each time the localhost is still the default IIS...
Is there anything else I can do? I'm a complete newbie on this topic, so please tell me if there's information missing in my question.
Also tried the advice in this article, without success. The terminal does say, that the service has stopped, but localhost is still the Windows IIS. https://www.names.co.uk/support/1607-how_do_i_stop_iis_via_command_prompt_.html
Seems clearing the browser cache solved the problem.
I've been working on a web app (front Angular, back Node/Express/Mongo) for a few months now.
I run Angular on localhost:4200 and Node on localhost:3000
Some people in our team are running the backend in a VM that runs on their computers.
So that the app works in both cases we've edited the windows hosts file to make the app point to the correct place (either the VM or the back on the local machine)
127.0.0.1 mysite
Developers using the VM changed 127.0.0.1 with their VM's IP.
Everything worked smoothly.
A few days ago, our company installed bitlocker on every PC and I believe it caused our setup to break for everyone not using the VM (which is not subject to bitlocker)
People working on localhost started receiving from the front app:
OPTIONS http://mysite:3000/auth/login 426 (Upgrade
Required)
The requests are not even hitting the Node server. Looks like they're redirected to a websocket server?
If I change the requests to target localhost:3000 the app works again but we lose the setup for people working on the VM. (thus committing code becomes annoying if we need to change the base url each time)
I could make an environment for each case but it's not clean and I'd like to know why it suddenly broke.
Try changing the port from 3000 to something else.
I just ran into this issue when a coworker tried running an express app we've been building on a Windows machine for the first time, as opposed to an EC2 instance. I've been using a Mac during development.
The issue seemed to be that 0.0.0.0:3000 was already mapped on company Windows machines. If you run netstat -an in a command prompt you may see it in use already.
hello mate this usually happens due to protocol mismatch between the PC and server.TLS 1.0 and 1.1 were permanently deprecated on June 4 2018. I suspect you’re using something that still uses and old version of TLS.
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.