Chapter 2. Known issues
This version is affected by the following newly identified and previously known issues. A known issue is listed in all future release notes until resolved, at which point it is published as a fixed issue. If you encountered an issue that is not listed in this section, report it by using the button in the top right corner of this page.
2.1. Web pages on localhost do not load in Google Chrome Copy linkLink copied to clipboard!
Issue: If you are using Google Chrome, you might not be able to load http://localhost:8080 or https://localhost:8443. This is caused by a combination of the operating system settings and Google Chrome which results in the IPv6 address ::1 being selected instead of the IPV4 address 127.0.0.1. Google Chrome attempts to resolve localhost to IPv6.
Actual result:
-
Web pages on
http://localhost:8080orhttps://localhost:8443do not open in Google Chrome. Google Chrome displays one of the following messages:
- "This page isn’t working"
- "localhost didn’t send any data"
- "ERR_EMPTY_RESPONSE"
- "This site can’t be reached"
- "ERR_CONNECTION_RESET"
Expected result: Web pages open as expected on http://localhost:8080 or https://localhost:8443.
Workaround: Use http://localhost4:8080 or http://127.0.0.1:8080 to force IPv4 resolution to the local address. localhost4 and localhost6 have been available as aliases for the IPv4 and IPv6 localhost addresses respectively since Red Hat Enterprise Linux 6. Use these aliases to ensure the address of the desired protocol is resolved. However, if your system does not have the localhost4 alias defined in the /etc/hosts file, you can use 127.0.0.1:8080.
For more information, see the webpages on localhost do not load in Google Chrome browser Knowledgebase article.