WiscWeb - 127.0.0.1 “This site can’t be reached” error

The following document will discuss what the 127.0.0.1 error is, what it looks like, and what you should do when you see it.

The error reads: "This site can't be reached. 127.0.0.1 refused to connect."

Issue

127.0.0.1 is a special IP address known as the localhost or loopback address. In WiscWeb, this error is usually an indicator that Modsecurity is flagging the page for some reason. Modsecurity thinks that the action you were taking could have been a hacking attempt and stops the action from occurring.

There are a few common times you might see this error:

Editing a page

If you were editing a page when this error occurred, it is likely that something you added to the page is getting flagged by Modsecurity. The typical reasons this could occur are:

  • Attempting to enter code into a page element (like a Text Block) 
  • Copying and pasting content into a page element (like a Text Block)

Tip: Try omitting any special code and update the page again.

Submitting a form

If you or one of your users was filling out a form when the error occurred, it is likely that something added to a form field was getting flagged by Modsecurity. The typical reasons this could occur are:

  • Copying and pasting content into a form field (like a Paragraph field) 
  • Using special characters in a form field (ex: percentages % and quotes " ")
  • Including mathematical expressions with logical keywords (ex: "1 and 1-1")
  • Carriage returns in the text

Tip: Try typing in the content into the form (rather than copying/pasting) and/or omit any special characters like quotes (" ") or percentages (%) and try submitting again. You may also need to try rephrasing input that includes numbers and logical key words.

Resolution

If the tips above did not work for you, please notify the WiscWeb support team via our Customer Support Form. Include a description of what you were doing when the error occurred.



Keywords:
127.0.0.1, site cannot be reached, error, refused to connect, checking connection, checking proxy and firewall, err_connection_refused 
Doc ID:
113654
Owned by:
Jenna K. in WiscWeb
Created:
2021-09-13
Updated:
2024-06-04
Sites:
DoIT Help Desk, WiscWeb