I have a weird situation here. I have an Amazon EC2 instance running Windows Server 2012. I installed Google Chrome on the volume. Everything works fine but one very annoying thing. When I'm using Google Chrome if I click on the address bar or any text input Windows Explorer pops up to a folder with the path C:\Program Files(x86)\Google\Chrome\Application\XX.XX.XX.XX\ (these X's seem to be in the format of an IP address). Has anyone else ran into this and if so what is going on and is there a fix? Everything works fine, but it's just annoying me for this window to pop up. Thanks
Related
I have a Windows 2016 Server with IIS 10.0.14393.0 installed that is maintained within an isolated VM environment. (The entire VM environment is isolated from the real-world.)
The web server is configured with three websites through IIS, and each website is assigned a dedicated IP. The contents in each of these websites is a single "hello world" html page that can be accessed via a browser from from my development workstation using Microsoft Edge, but I cannot access these pages using Chrome. The simple hello world html page was created only to assist in troubleshooting this issue.
The error received in Chrome is ERR_TIMED_OUT and based on the IIS logs, the request is never reaching the web server. IIS logs do indicate the request/reponse when accessing using Edge.
From my workstation, I can successfully ping the web server, traceroute output does not indicate any unexpected hops, etc. From all indications, the problem appears to be isolated to Chrome and only when accessing the sites on that server. I have other servers (W2016 and W2019) in the real-world with a similar configurations and real applications deployed there that work as expected with any browser.
I am using the latest Chrome Version 105.0.5195.102 (Official Build) (64-bit) and can access other web based content within this VM environment using Chrome, just not on that one server.
I am almost to the point of deleting that VM instance and starting over so any ideas/suggestions are appreciated.
The error received in Chrome is ERR_TIMED_OUT
This is a communication problem indication that there is a problem with the user's local network connection. It can appear when your internet is too slow or your connection is taking too long, or the page or website you are visiting may be too busy, or when the website in question is not set up correctly, or even if the website is trying to perform more than your server can manage.
I'm not sure if you've seen the following methods, but you can try.
Method 1: Browse in Incognito Mode and Remove Extensions.
You should first browse the website in incognito mode to check if you
can open the website normally, if so then the culprit of the
ERR_TIMED_OUT error may be your plugin or extension. Therefore, you
need to enable extensions one by one to check for errors, and if there
is an error enabling an extension, you need to remove it from your
browser.
Method 2: Delete the Default Chrome Folder
Press Win + R keys at the same time to open the Run
Type %LOCALAPPDATA%\Google\Chrome\User Data\ in the box and click OK.
Close your Chrome if it is opened.
A new window pops out, find the folder named Default. Backup the folder anywhere else, then right-click the folder to choose Delete.
After you have deleted the folder successfully, open your Chrome and
then visit the webpage again that you searched before to check if the
error still appears.
Method 3: Update Network Drivers
If your network driver is out of date, you may encounter ERR_TIMED_OUT
errors. Here's how to update network drivers.
Right-click the Start button to select Device Manager.
Scroll down to find Network Adapters and click on it to expand it.
Right-click on your network device and select Update Driver.
Select Search automatically for updated driver software option to start to search and update your network driver to a new version.
After that, restart your computer and open the sites again with Chrome
to see if you can open them.
Method 4: Disable Firewall & Antivirus Software
Sometimes, your firewall or antivirus software may cause trouble.
Therefore, you should try to disable them and check if the problem can
be solved. If you find it helpful to disable these programs, you can
check the firewall settings. Allow Chrome to connect to public or
private networks. If it doesn't work. Permanently delete these
programs, and then use other antivirus software or firewalls.
Method 5: Check Hosts File
When you meet the ERR_TIMED_OUT error accessing a specific website,
you can check the Hosts file to see if the website has been blocked.
Here is the way to do that:
Press Win + E keys at the same time to open File Explorer and then go to the Local Disk C: > Windows > System32 > Drivers > etc.
Open the host file with notepad. If you see the web address that you cannot visit, delete that entire line from the host file and save.
After that, open the Chrome and see if you can open the specific
website.
Method 6: Reinstall Chrome Browser
If none of the methods above fix the ERR_TIMED_OUT error, then you
should try reinstalling Chrome. Here is the tutorial:
Press Win + R keys at the same time to open the Run box, then type appwiz.cpl and click OK to open a new window.
Find Google Chrome in the list, and then right-click it to choose Uninstall.
After uninstalling Google Chrome successfully, you also need to delete its leftover files. Open the Run box again, then type %appdata%
and click OK to open a new window.
Find the Google folder and then right-click it to choose Delete.
Go to Google Chrome’s site to download the latest version of the browser, and then install it.
The above methods are from the web article. To avoid link being unavailable, I have also presented the details. I am not sure if the above methods can help you, but I hope you can solve the problem soon.
I'm running Google Chrome on Windows 10, latest editions. Chrome refuses to open any pages, returning "Aw snap" error messages. To resolve this I've:
Removed all extensions.
Uninstalled and reinstalled Chrome.
Tried Chrome on a different user.
Ran Chrome Cleanup Tool.
Deleted my Google folder in Appdata.
Incognito pages don't work either.
None of these worked. Firefox at all times is working perfectly so its not an internet problem.
Anyone have any ideas on how to fix this?
Please follow below steps, to resolve "Aw snap" error messages with Chrome browser.
Steps To Resolve:
Go to Chrome shortcut in the Desktop (If not exists create one)
Right click -> Properties
In the target field, At the end add a space followed by the below -no-sandbox
Apply-Ok
Launch chrome using the shortcut
Follow the below steps
Go to windows task manager
go to details tab
kill all the chrome process
run the chrome it will open
It is likely that malware is trying (and failing) to modify the page that is loading. I've also seen this as a symptom of machines that had nasty redirect malware removed, as the redirects that the malware creates no longer have anywhere to resolve.
I highly recommend a fresh Windows 10 install, only way to be sure you're fully free of whatever may have infected your current Windows installation.
I have a vagrant (Debian 7 + LAMP) box available via http://localhost:8087 I use it to develop a site.
I start the box connect to it via Chrome (v37.0.2062.120 m)
Then I connect to it via IE and browse the site normally.
After this, if I go back to Chrome and refresh the page I get Error code: ERR_NAME_NOT_RESOLVED , and I can't connect back to it (via Chrome) meantime, the site works fine in IE or Firefox.
If I do a restart all goes back to normal. However I can reproduce the issue every time.
BTW: I am on windows 7 with vagrant 1.6.3
I have been having an issue lately with Google Chrome. Some sites, seems to be completely random, are returning a 503 Service Unavailable error message. The last one I received was from my hosting provider when trying to access my CPanel. I can access the same URL completely fine in Firefox or IE. It seems to be isolated to Chrome.
I have tried the following:
Disabled all extensions
Logged in/out of my Google account
Cleared all cache and history
So far, nothing seems to correct the issue. It's becoming more and more aggravating from what was once a pretty reliable browser.
I am running:
Windows 7
Chrome Version 36.0.1985.143 m
I was hitting the same issue. Mostly, it would occur on intranet sites at work, but it happened with a few exterior sites. Loading in IE Tab would work fine.
I was able to solve the issue by upgrading to 64-bit Chrome. I'm not sure why that fixed it, but I think it had something to do with a conflict between Java and Chrome (It looks like I have both 64bit and 32bit Java installed side-by-side).
My solution:
Uninstall Chrome with clear personal data option selected
Install Chrome again but without admin right (install for your personal
user)
Use Chrome as normal
I've installed lemmingzshadow / php-websocket on my Win7 machine, which was pretty simple to do:
unzipped the content into my htdocs folder.
executed server.php from command line.
requested the file /client/status.html from a browser that supports Websockets.
Now here's what I get on the local machine running Google Chrome 19 / Windows 7
click to enlarge
It says "connected" for 30 seconds (displaying no info from the server) then says "disconnected", and here's the related command line output:
Exact same issue when accessing the script through LAN from another computer with Firefox 12 / WinXP
click to enlarge
It only seems to work when accessing it from my VirtualBox Ubuntu, using either Firefox 7.0.1 or Chromium
click to enlarge
It's been days since I've trying to figure out why this is happening, tried other Websocket scripts and they only work when I access them from Ubuntu. I even installed this same script on Ubuntu / XAMPP and was still stuck with the same issue (script running fine on Ubuntu but not on the other operating systems).
I'm going crazy over this, any idea why it's happening??
In that code (lemmingzshadow), the default behavior is for the server to mask the data it sends to the client:
Connection.php:
public function send($payload, $type = 'text', $masked = true)
For some reason this will work in Chrome 18, but it is against the latest websocket spec and does not work in Chrome 19.
RFC 6455 Sec 5.1:
A server MUST NOT mask any frames that it sends to
the client. A client MUST close a connection if it detects a masked
frame.