This problem seems to be caused by the failure to resolve DNS, but it is difficult to restart after checking various configurations. Finally, it is found that there is a problem with the forwarding rule configuration. Just execute the following:
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
iptables -F
Read More:
- Solution of server connection reused (test environment)
- Remote sshd prompt: server unexpectedly closed network connection
- Online problem solving analysis
- Driver failed programming external connectivity on endpoint quirky_ allen
- Error — failed to start docker container, error iptables — wait – t nat
- Cannot connect to MySQL server on “host” (113)
- ssh port forwarding
- Frequently asked questions about docker
- Idea svn connection https error report: E230001: Server SSL certificate verification failed: certificate issued
- Failed to enable APR appears when the cmder of ubutun system in win subsystem installs Apache_ TCP_ DEFER_ ACCEPT
- Vue3 uses element plus package to solve the problem of occasionally disordered code on the icon after it goes online
- The web application [ROOT] appears to have started a thread named [RxIoScheduler-1 (Evictor)] but ha
- The solution of centos7’s inaccessibility after installing nginx
- Record an error that the Tomcat resource publication cannot be updated:
- CIN in C + + cin.get ()、 cin.getline (), getline(), gets() function
- The solution of centos7 in VMware virtual machine unable to access after installing nginx
- docker: Error response from daemon: driver failed programming external connectivity on endpoint
- Xcode 5 solves the operation could’t be completed
- [Solved] react sass Error: SassError: Expected newline
- Deep understanding of async await asynchronous programming synchronization