It is likely that your browser’s proxy settings have been changed to use Charles and then, for some reason, not changed back.įirst try starting and quiting Charles normally to see if that corrects the problem. Note that this only works when you're using Charles as your proxy, so the above approaches are preferred, unless you specifically want requests to fail if not using Charles. If Charles is running and you're using Charles as your proxy, you can also use local.charles as an alternative for localhost. , which will also always resolve to 127.0.0.1.Īlternatively you can try adding a '.' after localhost, or replace localhost with the name of your machine, or use your local link IP address (eg. You can also put anything in front of that domain, e.g. If you use a different port, such as 8080, just add that as you usually would, e.g. This will work whether or not Charles is running or you're using Charles.
This points to the IP address 127.0.0.1, so it should work identically to localhost, but with the advantage that it will go through Charles. Some systems are hard coded to not use proxies for localhost traffic, so when you connect to it doesn't show up in Charles.
