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
Related
I downloaded Xampp in my Mac for first time, the server is working but when I want to go to my application show that safari can not connect to server.
does any one know where is my problem ?
I assume that you have the latest version of XAMPP.
You can reach your application by clicking on the button "Go to Application" or writing your IP address showed in XAMPP followed by "/dashboard/" or your browser (e.g 192.168.64.2/dashboard like the image shows)
general tab xampp
If you have already tried this, the problem might be related to the network configuration in XAMPP.
Create a new rule that forward the LocalPort 80 to the RemotePort 80, and check the "Require Local" checkbox.
After that, enable the rule and test it using "localhost/dashboard/" in your browser.
network tab xampp
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
I got a weird situation this week where I lost my access to WAS admin console/Servlets using inner browser or internet explorer suddenly.
I'm sure, WAS is running and my applications is started because i can access the server via Chrome.
To sum up,
IE doesn't open:
localhost:9082/SomeInputServlet or http:///SomeInputServlet.
The same case is true for admin console and inner browser.
Chrome can open only: http:///SomeInputServlet, not with he localhost.
Additionally, Chrome connects with https, not http.(Security is enabled on the server)
And also, server can be reached from other computers in the newtork with Chrome too.
Everything was ok before and i don't what can cause such a situation.
I reset my all ie settings, but it didn't work.
Any idea?
Thank you!
Problem Solved.
When I remove ie 8, and install ie 9, problem is solved.
I don't why but, it seems things are messed up in ie 8.
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.
I am developing a website locally using wamp. The site uses ssl and works completely fine in firefox. In Google Chrome, I get an error:
https://example.local/ gives me this error
This webpage is not available
The connection to example.local was interrupted.
Here are some suggestions:
Reload this webpage later.
Check your Internet connection. Restart any router, modem, or other network devices you may be using.
Add Google Chrome as a permitted program in your firewall's or antivirus software's settings. If it is already a permitted program, try deleting it from the list of permitted programs and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the wrench menu > Options > Under the Hood > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.
http://example.local/ works fine in chrome.
I should note that in IE I get Internet Explorer cannot display the webpage error, but again, it works fine in firefox...
Any help?