Skip to main content

Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.


I was consistently getting this error in chrome for a webpage that was loading just fine in safari. I managed to fix the problem by doing the following in chrome;

  1. Go to History > Show Full History

    Type the site domain to filter the results to show all recent attempts to load the page. Select all entries in filtered results and click "Remove Selected items."
  2. In the same History window, select "Settings" from a list menu in the left bar of the page. Click "Show advanced settings ..." .

    Then, under Privacy click "Content settings..."

    Click "All cookies and site data..."

    In "search cookies" textbox type the domain name of the website where the page is hosted.

    Click "x" to delete all cookies associated with the domain.
  3. Exit the settings window by clicking "Done" and try reloading the page. 
I hope this fixes the problem. If you followed the same steps, please let others know whether it worked or not by leaving a comment. 

Labels:

Comments

Post a Comment

Popular posts from this blog

Creating no-reply@domain.com account in Postfix

If you wanted to send emails to users but did not want to receive any replies to the email, you would need to setup a no-reply@domain.com email account. These kind of email ids are useful when sending emails containing forgotten passwords or activation code. Below are the steps for creating such account in Postfix. 1. Identify the file containing alias for Postfix First, make sure the following line in the ALIAS DATABASE section of the /etc/postfix/main.cf is NOT commented out: alias_maps = hash:/etc/aliases 2. Create an alias that redirects messages to /dev/null Edit /etc/aliases and add following entry devnull: /dev/null 3. Create a virtual email id Edit /etc/postfix/virtual and add following entry no-reply@domain.com devnull 4. refresh postfix alias and postfix cache Execute following commands. (You may require root privileges) > newaliases > postfix reload
4 comments
Read more

jupyter notebook execution error: "http://localhost:8889/tree?token=xxx" doesn’t understand the “open location” message

I got this error when I tried to launch jupyter notebook on a mac. It is not a fatal error. I could still go to browser directly and copy/paste the url manually. The error indicates that when the command automatically tried to launch a browser, it couldn't find the default browser in jupyter configuration file. The easy fix is to specify the browser. Here are the steps to do so; 1.   Open ~/.jupyter/jupyter_notebook_config.py in an editor.       If the file does not exist then you can create a default config file by typing the following command;       jupyter notebook --generate-config 2. Search for a word "browser" to locate a following line.     #c.NotebookApp.browser = ''     By default it is commented. You can uncomment it and use one of the following values depending on your browser preference.     # set default browser to chrome     c.NotebookApp.browser = 'chrome'     ...
Post a Comment
Read more

.ssh/config: “Bad configuration option: UseKeychain” on Mac OS

After upgrading Mac OS to Mojave I started seeing this error when doing "git pull". I was able to follow the steps below as described here ; 1. open ssh config vi ~/.ssh/config 2. Add the following lines to ssh config to keep your configuration compatible with both new and old versions of openssh. IgnoreUnknown UseKeychain UseKeychain yes That fixed the issue for me. Try running git pull again.    More details about the issue are available here . 
Post a Comment
Read more