Chrome Slow on Local IIS Sites - google-chrome

I've seen this problem reported by other people whereby Chrome is incredibly slow to respond on local sites hosted in IIS. This is whether I'm using localhost or a specific host file entry (like mysite.local).
Existing fixes suggest removing the IPV6 entries from the host file, but that doesn't sort it out on my machine.
I'm running windows 8.1, vs2013 and IIS 8.5.
Can anyone help - its driving me crazy!

open 'worker processes' in features view of IIS panel and see if an earlier request is holding up rest of the queue. This can occur if the previous process waits for I/O to complete for instance.

Related

An Internal error occured error code 0x4 remote desktop connecting to google cloud Compute Engine VM

When tyring to login to RDP the "old" remote dekstop connection gave "an internal error occured"
And the new modern UI remote dekstop from windows store with version 10.2.1810.0 gave: error code 0x4 remote desktop
It seems a colleage has been logged in with wierd screen size. How can I resolve this without rebooting the machine?
I found a solution.
In the new GUI untick:
"Uppdatera fjärrsessionens upplösning vid storleksändring" in Swedish
Which translates to: Update the resolution of the remote session when resizing
Update remote sessions resolution when size change
Actually, even moving the port off 3389 doesn't help (for long)
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
if there is an open port allowing RDP they will find it eventually and you will need to implement one of the above programs noted by Daniel. That was exactly my issue as well. You can usually tell if the problem is intermittent since it's just luck to get by the constant pounding on the open port...
For me, it was the graphic choice. No idea why but as I swap between the 4 options, only one works
I needed to set it to Highest Quality (32 bit)
However, I then restarted the server, and it no longer worked but True Colour (24 bit) did work! So, hopefully by toggling through each will get you through
In my case the cause was AVG Firewall blocking some RDP connections. I had to configure AVG Remote Access Module to allow RDP connections from some known IP addresses.
Hope this helps someone.
Looks like this error code pop up for many things... from screen resolution resize to colour depth to firewall and more... Which is quite odd. You have to check what is your specific case.
In my case, when I had problems with error code 0x4, it was related to unprotected RDP port.
In my case, it was caused by open, unprotected, RDP port 3389. As many would guess, this is a highly targeted port by bots. If your port is open to anyone in the internet, it's just a matter of time that your server or computer will be targeted.
The best solution would be to only allow connections from trusted IP addresses, the ones you use for connecting to your server.
Of course, that can't always be possible, so another solution would be something like the fail2ban utility used on many Linux servers.
The two solution I've found are EvlWatcher which is free and open source, and IPBan that have a free and open source version, but also a paid version.
You only need one of them, as they do the same thing. Do not install both. They will scan your logs and will temporary or permanently block any IP address with repeated fail connections. I suggest you always have your main IP address whitelisted, so you don't lock yourself out.
Best regards to you all.

Headless Chrome fails under IIS but works on command line

I am wrapping headless chrome using the excellent ChromeHtmlToPDF library. This we are using to dynamically render PDFs from a website. This works locally under IIS express, and also works on the server when recompiled as a console app, so the technology works. However running under IIS, chrome always exits immediately and a error of "one or more parameters are invalid", is returned.
You can fix this by passing Chrome a custom user profile directory:
chrome.exe --user-data-dir="C:\NewChromeProfile" ...
This directory will be created by the account under which Chrome is running, and therefore the account will have the permissions it needs.
After many many hours looking into this I finally solved it by running it under my own user, the restricted IIS user, then comparing the activity logs generated by the excellent microsoft process monitor.
I tracked it down to file permissions on one directory: C:\Windows\System32\config\systemprofile\AppData\Local\Google\Chrome\User Data
The app pool user needs write + modify permissions to this directory. It's up to you if you feel this is an acceptable security risk; however for us it is, for now.
This is where headless chrome stores it's crashpad directory. No amount of parameter fiddling seems to be able to dissuade it of this. That seems to be a bug.
Hope this helps someone else, I couldn't find anything on this anywhere.

Localhost not loading in any browser

I have asked a similar question before here I sort of fixed it but im still facing a similar issue. Every time I try to load localhost, port 8095, I receive this error message in Google Chrome:
Google Chrome's connection attempt to localhost was rejected. The
website may be down, or your network may not be properly configured.
If there is a way to fix it, please tell me,
If not, please could someone inform me how to reset IIS to its original settings. Or if I can reset Windows Features so I can re-install ISS from scratch.
My website uses ASP with a connection to a SQL Server database (2012). Basic HTML pages also don't load under the URL, localhost:8095/
The servers were stopped because 2 services within administrative tools had stopped. World Wide Web Publishing Service and Web Management Service

Windows Phone 8 Emulator Deployment Issue with Internet

I am facing an issue with windows 8 phone emulator.
Windows Phone emulator wasnt able to connect to Windows Phone
operating system. Phone didnt respond to connect request
This is the error that I get. When the emulator starts with internet but my application doesnot deploy. The ip that gets assigned is 192.168.137.1. Previously it worked fine,
but then suddenly it started giving this issue.
Below is the list of troubleshooting that I have performed:
169.254.xxx.xxx address set to internal emulator via dhcp, Application deployed successfully with NO internet connection
Have tried MAC address spoofing but nothing works when I use these settings.
Have changed External Virtual Switch in Sharing mode this starts the internet with ip 192.168.137.1 but application doesnot deploy
In debugger errors shown are:
Invalid pointer error
App deployment failed
Have tried Network bridging but still it doesnt work.
Created all settings manually including the internal switch and external swithch. But same issue faced when it gets 192.168.137.1 ip then internet works but application doesnt deploy.
And when it gets 169.254.xxx.xxx ip series application deploys but no internet connection.
No firewall are turned on or no antivirus is blocking any connections.
Wireless router used for network connectivity, still not successfully
Have also tried clean installation of everything but still no go.
Need help with this issue as I have been trying to get it resolved since a week.
This issue is not faced if installation is done on the same pc through a virtual machine.
What I did was :
Have allotted 4gb ram, 60gb hdd & 4 cores to the VM.
1)I installed a virtual machine with default settings.
2)Then I stopped your virtual machine (shut Windows 8 down, DO NOT suspend it).
3)At the VMWare Virtual Machine list, right click Windows 8 machine then click "Show in Finder".
4)Right click the file then click "Show package contents", then find and open with a text editor a file with the extension .vmx
5)Go till the end of the file and add this two lines (first check whether they were previously added):
hypervisor.cpuid.v0 = "FALSE"
vhv.enable = "TRUE"
6)At the VMWare Virtual Machine list, right click Windows 8, click "Preferences" then "Advanced". Choose "Intel VT-X with EPT" as "Preferred virtualization engine".
And then when I started the windows in the virtual machine it seems to be working fine without any additional setting change. However it is still not running on a physical machine
I recommend if someone is facing a similar issue then to use a Virtual Machine till this kind of issue is resolved.
Struggling with the same problem for 3 days I finally solved my issue by disabling windows firewall for "Guest or public network". I have yet to figure out what application/service to allow through so I can re-enable it.

Hosting subdomains separately with and without SSL while using a wildcard certificate

I'm having a strange problem with a separately hosted subdomain I have. I'm running an application on Engine Yard, let's call it mysite.com. I have a wildcard SSL certificate installed there which covers all the subdomains (things like api.mysite.com). We recently decided to migrate our blog to be hosted independently (right now it lives on wordpress.com). Because I can't run the blog alongside our Rails app with ease on Engine Yard, I decided to grab some cheap hosting space from Dreamhost to host our Wordpress blog there. I set up the server there to fully host our subdomain (let's call it blog.mysite.com), and updated the DNS A record on Hover (our DNS provider) to point blog.mysite.com to the Dreamhost server. So here's the issue:
If I go to blog.mysite.com via Firefox or Safari on my Mac I see the basic Wordpress install which I set up. However, if I try to view things with Chrome I get the following error:
This webpage is not available
Error 118 (net::ERR_CONNECTION_TIMED_OUT): The operation timed out.
This happens on all Macs running Chrome I could get my hands on. I tried both clearing the cache and flushing the DNS but nothing. The weirdest part is Chrome keeps looking for https://blog.mysite.com instead of http://blog.mysite.com. There is no SSL cert installed on the subdomain for the blog on Dreamhost because it's not necessary.
Has anyone ever come across this before? And in case anyone wants to try the actual address is http://blog.frestyl.com.
sounds like you have a 301 permanent redirect that Chrome registered http://blog.frestyl.com -> https://blog.frestyl.com. Besides clearing the cache I'm not sure what else can be done.