Solve the problem of Kloxo-MR error message: Error 404 – Not Found

Solve the problem of Kloxo-MR error message: Error 404 – Not Found

The requested page could not be found but may be avaiable again in the future

The requested page was not found, but may be available again in the future

If you are seeing this page, it means that web has not been configured for this domain on this server.

This could be due to the following causes:
Kloxo has not restarted the web server yet after you added the domain. Please wait for the web server to restart.

The domain is pointing to the wrong Kloxo server. Ping the domain and make sure that the IP matches one of the IPaddress seen in admin home -> ipaddresses

If you are seeing this page when you try to access an IP like http://192.168.1.1, then that means that the IP has not yet been mapped to a domain. Go to client home -> ipaddresses -> ipaddress home -> domain config and map an IP to a domain.

Once you map an IP to a domain, then you have to make sure that the domain pings back to the same IP. Otherwise, if you try to access the domain, you will get this page. So IP -> domain.com should mean that domain.com pings to the same IP.

If you see this page, the server has not yet been configured with networking for this domain.

This may be due to the following reasons:

• Kloxo has not restarted the web server after adding the domain.Please wait for the web server to restart.
• The domain points to the wrong Kloxo server.
• Ping the domain, and make sure the IP matches one of the IP addresses seen in admin home -> ipaddresses.

If you see this page when trying to access the IP http:// 192.168.1.1 , it means that IP has not been mapped to a domain.

• Go to: admin - IP Addresses - {configure domain name} and map the IP to the domain.

Select update for eth0

domain name:UFO.org.in, img.UFO.org.in

• try to refresh ufo.org.in, img.ufo.org.in
• If there is still an error, switch the domain name selection in turn or select "Disabled"

Restart httpd:

service httpd restart

After restarting httpd, select "Disabled" to take effect.

After mapping the IP to the domain, you have to make sure the domain pings back to the same IP.Otherwise, if you try to access the domain name, you will get this page.So IP -> domain.com should mean domain.com calls to the same IP

The above method has been tried many times, but there is still a problem, please enter the following repair command:

yum clean all; yum update -y; sh /script/cleanup