The intuitive mistake in this problem is that the access is different. The first reaction is related to the firewall, but after thinking that I am visiting a local project, it has nothing to do with the firewall. Later, I thought it might be the wrong address. The IP number is 127.0.0.1, so it must be the wrong port. Sure enough, the front end was accessing port 8000, but the server was listening on port 9999. Just make it consistent.
Read More:
- Failed to load resource: net::ERR_CONNECTION_REFUSED
- Solve the Google Chrome Failed to load resource: net::ERR_FAILED problem
- Failed to load resource: net::ERR_CONNECTION_RESET
- Failed to load resource: net::ERR_ INSECURE_ Response problem solving record
- The browser console reports failed to load resource: net :: ERR_CONNECTION_RESET, which results in unable to log in
- failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
- Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR
- Failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING
- Chrome console reports Failed to load resource: net::ERR_BLOCKED_BY_CLIENT one of the solutions
- Nginx proxy appears Failed to load resource: net::ERR_NAME_NOT_RESOLVED
- Chrome Failed to load resource: net::ERR_CACHE_MISS
- Failed to load resource: net::ERR_ CACHE_ READ_ Failure solution
- chrome: Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID
- solve java.net.ConnectException : Connection refused:connect report errors
- Solution: DevTools failed to load SourceMap:… net::ERR_HTTP_RESPONSE_CODE_FAILURE problem
- How to Fix java.net.ConnectException: Connection refused: connect
- Zookeeper connection timeout problem, and refused to connect to solve the problem
- JMeter performance test monitoring server resource reported error: java.net.ConnectException : Connection refused: connect
- hdfs 192.168.2.19:9000 failed on connection exception: java.net.ConnectException:Connection refused
- Solve the browser err_proxy_connection_failed problem