A few days ago, a yellow banner started to appear in Fiddler reporting that my proxy settings had changed and that if I clicked the yellow banner, I could re-enable Fiddler traffic capture.
Upon clicking, the banner and the error message wouldn't go, and Fiddler had stopped capturing all traffic.
I searched the Web and found how to change the proxy settings back to 127.0.0.1 and port 8888.
However, when I do that, something keeps setting the port number back to 63758.
The version of Fiddler I am using is v2.4.9.9 on a Windows 7 Home Premium PC.
Please see picture attached. What should I do?
This probably belongs on Superuser rather than StackOverflow.
You don't need to "search the web" to change your proxy settings, just click the big yellow bar.
You'll need to find what is changing your proxy settings. My guess is that you're infected with Adware like BrowserSafeguard or GeniusBox. You can either use netstat -a -o to find the process listening on the port in question, or you can use SysInternals' Process Monitor to watch the Proxy Server registry key and see who is changing it.
Related
I use a local Python web server on my Windows machine. It’s simple, but good enough while in the static web page development stage. I just run it with something like this on my WSL command line:
python3 -m http.server
I can also access it on mobile devices on the same network, by going to my local address, e.g.: http://192.168.1.12:8000. All was good, until suddenly I could no longer access it on external devices, I got a “server not responding” type of message. Also, I could clearly see that when I refreshed the page on my phone, there was no GET request on the logs.
Immediately I tested on the local machine, and it was still working fine. This obviously smelled like a Firewall. In Linux, I’d know what to do, but it’s the first time I had to deal with this on Windows. This is what I’ve tried, without resolving the connection problem:
I opened the Event Viewer but could not see any obvious logs to check
I stopped the server (CTRL+C) and started it again on another port (5000). The Windows Firewall message popped up again asking for permission for Python3 to access the “Public network” and the “Private network”. Normally I just tick the “private network” but this time I checked both, as a troubleshooting step, in case my Wi-Fi was incorrectly being considered “public”.
I went to Windows Firewall and temporarily shut it down on the private network.
I installed and tried running nmap on the WSL, but it failed to run and prompted me to install the Windows version instead.
I installed and ran the Windows version of nmap but it told me that port 5000 was open.
What is the recommended way to troubleshoot and fix this issue?
Still suspecting the firewall, I tried something new, I switched off the “public network” firewall. I tested on my mobile and the page loaded as normal again! I immediately turned the firewall back on. Tested the page on my mobile once more, still fine. So, the solution was to toggle the public network firewall. I would make it more generic and toggle all firewall categories on Windows. And of course, I would make sure that the firewall stays on, this was a very quick operation.
I thought I’d put this here rather than ServerFault or SuperUser as it could potentially be more useful to developers, and it took a precious hour of my time. I still don’t know why it stopped working on its own in the first place. Better troubleshooting steps or suggestions are welcome, but I probably won’t be able to verify it as I don’t know how to purposely induce the issue.
Another solution that worked another time, was to delete all instances of Python 3.8 from the list of allowed apps (I don't know why Windows shows the same app multiple times) then (re)start the Python server and allow it through when the Firewall question pops up again.
In windows firewall you may have 4 options to configure your local web server when you are creating new Inbound connections rule.
1 Program
2 Port
3 Predefined
4 Custom
Try to use port only in "TCP protocol" and the custom port.
Allow connection.
Select: all checks: domain, private and public.
Enter a name.
Thats all.
I am following this instruction http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureForiOS. Everything works until section Set the iOS Device Proxy.
Once I set the proxy on my iPhone, I can't connect to the internet from the phone anymore. Not even accessing the echo page, which I could access before turning on the proxy on the phone. I already installed the root cert on my phone, the makecert add-on on Fiddler
Could someone help with ideas to diagnose the issue here? Thanks,
What might be stopping your iphone from reaching your Fiddler machine on the port specified, usually 8888?
Have you a firewall on the Fiddler machine? You might need to open
the port.
Does your LAN have an automatic redirect to a login page? Ours
does, so I have to disable the proxy on the iphone while I login,
then reenable it.
Does your LAN expose the IPs of cable-connected machines to WIFI
users? Not all do.
Can you browse a simple web page on your Fiddler machine from your
iphone, before starting fiddler or doing any proxy configuration?
You might need to get really serious and install a ping utility on the iphone.
I installed usbwebserver
everthing is running, I am trying to reach the root page index.php?
I read everything I possibly can and sorry but I still cant figure out how to reach my localhost
I reach my page with localhost:8080 and the page I want shows up but if I replace it with IP:8080 it does not.
I am trying to reach this page outside of my local network.
I'm sorry, I need to provide you a separate answer for your reformatted question for the "down the street" scenario. I can troubleshoot a few of the issues you're probably having.
ISP's don't typically allow residential internet connections to serve resources over port 8080, or 80. Even if you were to configure your computer as needed, if you're on a standard internet service provider they're probably blocking you in the middle even if you have punched holes all your local security in an attempt to serve assets over port 8080/80.
Assuming they don't allow that you're going to have to first configure your outbound middleware(php in your case) to listen to calls into your ip on a different port. ( You can do this in your C:\WAMP\ folder, in the "wampserver" configuration file. Here's a good walkthrough here: (http://forum.wampserver.com/read.php?2,13744)
Now, you're going to have to drop any firewalls windows/ubuntu/macOS are providing on that port. (This is the part where you've rolled out the red carpet for hackers to get into your box(es) so be careful!) Here's a link for a short and sweet explanation on windows here: (http://yourbusiness.azcentral.com/turn-off-windows-firewall-19396.html) Note that you can open individual ports, you don't have to drop your entire firewall.
Make sure you have opened up access to any folders/mySQLdb's/resources to outside requests as well (seriously, this is a REALLY bad idea from an #home server if you don't know what you're doing)
Then figure out the correct ip and the correct port and give it a go! If it still doesn't work you can download a program like [wireshark] (https://www.wireshark.org/download.html) or [fiddler] (http://www.telerik.com/download/fiddler/fiddler2) to debug your inbound/outbound traffic and see what the machine's seeing before your browser/server gives you any user visible information.
One thing to note, if you are an amateur web developer your homepage is called "index.html" not "home.html" "home.html" only works fine locally, but internet browser engines look by default, for "index.html"
Lastly, and I really can't stress this enough don't host through your personal ISP and serve files from your own machine. Hosting through Fatcow, or hostgator, or any of the other hosts is really honestly dirt cheap and they know far better than you or I do about security.
That said, I hope very much that you succeed in using my answer, or at the very least learning something from it. Happy Coding!
http://www.canyouseeme.org/
--
Read the Background session
go to a command line, type "ipconfig"
Hit Enter.
Under "Ethernet adapter Ethernet:
It should be the third line down, has your following:
IPV4 Address : 192.168.1.xxx where "xxx" is your ip
address.
USE "//" + "the ip address shown for (ipv4)" plus ":8080" and your default page
should show just fine.
For example, if your cmd "ipconfig" for this process reads: "192.168.1.12"
your total URL in your browser will be "//192.168.1.12:8080"
Note that I used 2 forward slashes prior to using an IP address on your
local network. That let's your computer know it's using your network, not
the actual internet. The slashes alone may solve your problem. Also note, if you're accessing a database through your webapp, you will also need to properly configure your db settings to allow access.
First find your outside ip adress not local ip. After that go into router panel and open to use from apache server. Anyone able to access that port now. You can connect outside your local website now. If you can't do that. Try again. This is the way to doing this.
When I right click on my Hg folder and choose TortoiseHg > Web Server, I can start the web server on port 7999 without a problem. I then shut that dialog box. If I go and run netstat -a -o from a command prompt, I can see that an instance of thgw.exe is running and listening on port 7999 (even after closing the dialog box). It's ironic that in Task Manager the thgw.exe process is called "TortoiseHg GUI tools for Mercurial SCM" even though there's no GUI running.
Problem
If I open that dialog box again via TortoiseHg > WebServer, it reports that the status is "stopped", and the Start button is enabled. This is incorrect because the port is still listening. If I click the start button I get this message in the log as I'd expected:
abort: cannot start server at ':7999': Only one usage of each socket address (protocol/network address/port) is normally permitted
Questions
So why does TortoiseHg not realize that an existing thgw.exe is running on the port?
Is there a better way besides netstat and task manager to check if TortoiseHg is listening on a web port? And also learn which port is representing which folder?
I can't stop the web server so how are you supposed to gracefully shutdown a TortoiseHg web server without killing it from Task Manager? That seems like a scary thing to do to my production source control system!
When the Close button of the Serve window is clicked, the window does not actually close, but minimize itself into the notification area. See the globe icon in the screenshot below:
If you click the icon, the original Serve window appears, where the Start button is actually disabled, and Stop enabled. You can stop the server from there.
This behavior was tested on TortoiseHg 2.4, Windows 7.
The only problem I see here is that the original window is not opened when you choose the appropriate menu item.
See also issue 1845 on the TortoiseHg bug tracker.
I am using VirtualBox in Ubuntu with WindowsXP as the guest OS.
In Ubuntu I have a PHP/MySQL server running as localhost and with the VM network set to bridged I am able to connect to localhost from the VM.
However, I would like to limit the VM Guest to be able to continue connecting to localhost but NOT be able to connect to the internet.
This is a security thing - I don't want to have to install firewalls and virus checkers in the VM just to keep it safe - It is being used as a testing platform and only needs to connect locally.
Does anyone know how to do this? Iv spent time searching, but all I find are articles etc that show how to connect the VM to the internet, exactly the opposite to what I want to do.
Okay, so that doesn't exactly do what I needed, but this is:
1) Networking for VM set to 'Host Only'
This creates a new adapter called vboxnet0
2) On the command line 'ifconfig vboxnet0'
This should give you a bunch of stuff, but in there somewhere is an IP address. Make a note of it.
3) Control Panel->Internet Options->Connections Tab->LAN Settings
Make sure both items in automatic configuration at the top are NOT checked then click 'Use a proxy server for your LAN'
Enter an imaginary address and click 'Advanced'
At the bottom of the next window, in the Exceptions panel, type the address that you got from part 2 (ifconfig vboxnet0)
Click all the okay buttons to get out.
4) In all browsers the Ubuntu localhost can be reached by:
http:// [IP from part 2]
Phew! I think that did it. I hope this might help someone else.
M
Ill answer this myself just in case anyone else wants to know:
In the Windows guest:
Control Panel->Internet Options
Select the 'Connection Tab'
Make sure that 'Automatically detect settings' is off
Click 'LAN Settings'
Check 'Use proxy server' and add an IP that does not exist
Click 'Advanced'
Add your localhost IP to the section at the bottom: 'Do not use Proxy server for.....'
Your browsers should still be able to reach localhost for testing, but cannot reach the internet. Since there seems to be no connection Id hope that it works both ways (and I'm happy for someone to point out if that is not correct)
Cheers
M