I installed WebStorm on my PC and started NodeJS server. I am able to access it from Chrome and Firefox browsers using localhost but not with my PC's IP address.
I followed instructions given here. I verified whether extension is enabled or not in Chrome as well checked the port no in WebStorm's Build, Execution, Deployment -> Debugger. My PC's firewall has been turned off. Still I am unable to access it using IP address.
Can anyone guide me how to go about this?
I am running WebStorm in my PC and trying to access it from the same machine through above browsers.
Using WebStorm 2016.3.3 version.
Here are my findings when connecting to WebStorm's internal web server via Chrome using the following:
WebStorm 2018.1 Build #WS-181.4203.535
Windows 7 6.1, 64 Bit Pro
Chrome Version 65.0.3325.162 (Official Build) (64-bit)
Chrome connected to localhost:63342 but returned connection refused when attempting to connect to WebStorm at <ip address of machine>:63342, even with Windows Firewall disabled.
I first configured WebStorm to listen at port 63343 instead of 63342 and still had the same result. Unexpectedly, with this setting WebStorm answered at both localhost:63342 and localhost:63343, even after restarting WebStorm.
I then noticed that with either of these ports, WebStorm's Can accept external connections checkbox was grayed out and unchecked. Changing WebStorm's port to 1338 alone still resulted in Connection refused at http://<ip address of machine>:1338. Turning off Windows firewall did not affect this.
Since WebStorm's Can accept external connections checkbox became usable after I changed its port to 1338, I now checked the box. Chrome was now able to reach WebStorm at http://<ip address of machine>:1338.
So it seems that it is not the port itself that makes a difference, but WebStorm's Can accept external connections checkbox. Note that checking this box may be a security risk if you are using a shared network since WebStorm will now serve pages to other stations as well as your own.
Got answer for this in this post I changed the default port no to something else and now i am able to access the page from the browser using ip address.
Related
I was requested to configure IIS for an internal website on Windows 2019 server where Windows Admin Center is installed already. Since 443 was used by Windows Admin Center, I tried to configure a custom port such as 4433 and opened a firewall rule for the port as well as my subnet. The website opens fine locally, https://mywebsite.com:4433. However, when it is attempted externally, it times out with the following errors:
Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT
What could be an issue? Any idea?
There are many reasons for this error, you can try below steps to slove this issue:
Check if your internet connection is working properly. Check the status of the network connection and see if it is stable. You can disconnect and connect to the internet to see if the issue is resolved.
Disable firewall
Go to Windows > Settings > Updates and Security > Windows Security > Click Firewall and Network Protection and try to disable
Also try clearing your browser's cache and see if the issue is resolved
I have an ASP.net MVC application that I've developed using Visual Studio 2015 Enterprise that is not behaving nicely in IE8, and as much as I'd like to just declare IE8 as unsupported, this is unfeasible from a business perspective at the moment.
So, to test in IE8, I downloaded a VirtualBox containing an instance of windows with IE8 from here.
I've been successful in using this instance of IE8 to connect my organization's dev server (which is running Windows Server 2012r2, IIS 8.5.9600), so I've been able to reproduce the issue. I'd really like to be able to step through what's happening in the debugger, though.
So, I believe I have two options.
Connect to the IIS instance on our dev server using Visual Studio's remote debugging feature.
This is kind of intimidating to me to attempt, because there seem to be a lot of options and I'm unsure how to proceed. It would be nice to be able to figure this out, though, as being able to do remote debugging on the dev server would be very helpful for future development. I tried using the default transport and putting the host for the dev sever in the "qualifier" box in VS, but it just told me the debugger service wasn't running on the remote machine, even though I'm fairly certain it is.
Connect to my local workstation running Visual Studio from virtualbox
This seems like it would be the simplest solution, but I can't figure it out. I tried a few different network modes from virtualbox -- NAT, bridged, and Host-Only, but I could never get the page to load in IE inside the virtualbox. I tried using the ip of my workstation as reported by ipconfig /all (the IP of the normal network adapter for bridged and NAT mode, and the IP of the "Host Only" special adapter in Host Only mode) and the port VS was configured to use. No dice.
Any ideas on how I can move forward with either of these options? Or some third, better option?
I have been using VMWare Fusion 7.1.0 on my MacBook Pro with OSX Mavericks (10.9.5) without a hitch for several months. It was also working fine this morning until about an hour ago when I suddenly started getting an error message for any URL I tried: "Unable to connect to Proxy server."
I've tried both NAT and Bridged network adapters with no success.
There are no new software installs or updates (that I'm aware of), and I've tried restarted both the VM and the Mac itself twice.
Any suggestions?
I'm not sure how it happened, but my Network Proxy settings had gotten changed and set to use a manual proxy setup. I turned that off, and it resolved the error.
Here's how I found and fixed the settings:
Hit the Windows key (to get to the home page and do a text search)
Type "proxy" In the search results, click "Network proxy settings"
On the lower half of the screen under the Manual Proxy Setup, make sure the switch for "Use a proxy server" is turned OFF.
I'm doing web development in (primarily in Visual Studio Express 2013), so I wonder if the it jacked with my settings to allow for localhost development?
Check your VM's OS networking settings and ensure auto-detect proxy settings is not enabled.
Is there any way of inspecting element on a Samsung tablet using the default Internet Application? I have some bugs that need sorting that only appear in the native Samsung / Android 'Internet' application.
Samsung Internet can be debugged remotely using Chrome on the desktop. Any pages you have open in Samsung Internet should be listed for inspection under chrome://inspect:
As Ada shared here, you can also enable port forwarding and connect to a server running on your desktop machine. You will need the Chrome app running on your desktop. If your localhost URL does not resolve, visit chrome://inspect and ensure port forwarding is enabled. You may also need to open the Chrome app on your mobile device.
Update: There is a page in the Dev Hub docs about remote debugging here.
Developing an MVC application, i now need to have test other browser versions.
Installed the VM XP on win 7. That is running good. Got IE8 installed and FF 3.6. I know IE9 has a compat mode for 8 and 7, but read some articles that these may not run exactly as their stand alone versions. I got IE8 installed on the VM XP, so now i need to connect to my IIS Win7 localhost.
IS there anyway to do this? and How?
You need to configure your HOST PC's firewall to allow the VM (and perhaps other machines) to connect on port 80.
You can then navigate to http://hostmachinename in the VM.
Although my firewall was off, i was able to connect using the local machine name or ip address, as stated above by SLaks. So, if anyone has there firewall on, you may have to allow the VM to access the ports.
I did set the VMXP >> Tools >> Settings >> Networking to my Nic/ethernet card.
Not sure if this had any effect.
I also had trouble at first not getting the .NET MVC website to run. But then realized our web.config is setup to take only https. I had my website running on 2 ports, one for is for SSL. When i use the https secure port, it connected. So iguess the web app was seeing the VM as another computer tryingto coinnect, that was not local, so it required it to connect by https.