When i bowse the web it often says internal server error and wont display the screen, why?

The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.

The Web server (running the Web Site) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.
This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse these logs.

500 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:

• Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
• Open an IP socket connection to that IP address.
• Write an HTTP data stream through that socket.
• Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '500'. (Last updated: March 2012).

Fixing 500 errors - general

This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error.

Fixing 500 errors - CheckUpDown

Please contact us (email preferred) whenever you encounter 500 errors on your CheckUpDown account. We then have to liaise with your ISP and the vendor of the Web server software so they can trace the exact reason for the error. Correcting the error may require recoding program logic for the Web server software, which could take some time.

The Error 404 "Page not found" is the error page displayed whenever someone asks for a page that's simply not available on your site. The reason for this is that there may be a link on your site that was wrong or the page might have been recently removed from the site. As there is no web page to display, the web server sends a page that simply says "404 Page not found".The 404 error message is an HTTP (Hypertext Transfer Protocol) standard status code. This "Not Found" response code indicates that although the client could communicate to the server, the server could not find what was requested or it was configured not to fulfill the request.
The 404 "Not Found" error is not the same as the "Server Not Found" error which you see whenever a connection to the destination server could not be established at all.

Thanks for using FixYa!

Retry the web page by clicking the refresh/reload button or trying the URL from the address bar again. Even though the 500 Internal Server Error is reporting a general error on the web site's servers and not your computer, the server error may only be temporary. Trying the page again will often be successful. http://moritsolutions.com/

That is a rather general error from an internet server. They usually occur when you are visiting a web page that can't be displayed properly due to errors in the code, in this case, they were trying to display HTML code from their system directly in your email. If it came in a spam email, you don't need to worry about it.
If it came from a company or person that you needed to see what they were sending you, contact them and tell them you got a 500 server error, and forward them the email so they can figure it out. It will have to be fixed on their end

HTTP Error 500 means the code that is rendering the web page for the web site you are using has failed for some reason (Server Error). It is not the phone itself.

just refresh...if that doesnt work Re-type the youtube address if that doesnt work try a different brower...if u dont have another browser download some
konquerer, opera, firefox, flock, chrome

If your having an internal server error it usally means that There Servers are playing up

you cant really do anything about this dirctly but UBI is bound to be fixing it at this moment in time

if you wait a few days they will have fixed it for you.

please rate "

The ProLiant DL380 G3 server requires that both primary and redundant fans exist in a specific configuration in order to perform optimally. Any deviation from the specified configuration will cause one of the above error messages to occur and the internal Health LED to illuminate. In a ProLiant DL380 G3 server without the redundant fan option, the server will shut down after the error message is displayed. In a server with the redundant fan option, the internal Health LED will illuminate and the appropriate error message regarding fan redundancy will be displayed. The purpose of this document is to detail the required configuration for both primary and redundant fans.
DETAILS Both primary and redundant fans in the ProLiant DL380 G3 server must be configured to meet specific requirements in order to avoid the error messages above and in some instances, subsequent shutdown of the server.
All primary fan locations (2, 4, 5, 6 and 7) must be populated with a fan before the redundant fan locations (1, 3, or 8) are populated. If a primary fan location is left unpopulated, the server will display one or more of the error messages shown above. In addition, the internal Health LED (the top LED on the front panel of the server) will display the status of the fans.
When the redundant fan option is used, all redundant fan locations must be populated. ProLiant servers do not support partial population of redundant fans. If any redundant fan location is populated without also populating all other redundant fan locations in the server, the fan system will not be fully redundant and one or more of the error messages above will be displayed.
Figure 1 below illustrates a ProLiant DL380 G3 server configured with all eight fans installed for fan redundancy. The server airflow is divided into three zones: processor, I/O and power supply. Shared fans 4 and 7 each provide airflow for two zones. If a shared fan fails, the failure is experienced in both zones.
Figure 1: ProLiant DL380 G3 server configured with all eight fans installed for fan redundancy
The internal Health LED (the top LED on the front panel of the server) indicates failed or missing components. The internal Health LED should be observed to determine the status of the fans as follows:
RED LED: A red LED indicates that the minimum fan requirements have not been met. Minimum fan requirements indicate that all primary fan slots must be populated with functioning fans.

• If the 1611 fan "x" is not present (where "x" is the fan location) error message is displayed at POST and the internal Health LED is red , then a primary fan is missing.
  
  
• If the 1611 fan "x" failure (where "x" is the fan location) error message is displayed at POST and the internal Health LED is red , then a primary fan has failed.

AMBER LED: An amber LED indicates that the minimum fan requirements have been met; however, requirements for redundant fan configuration have not been met. This means that all primary fan slots are populated with functioning fans, but at least one redundant fan has either failed or is missing.

• If the 1611 fan "x" is not present (where "x" is the fan location) error message is displayed at POST and the internal Health LED is amber , then a redundant fan is missing.
  
  
• If the 1611 fan "x" failure (where "x" is the fan location) error message is displayed at POST and the internal Health LED is amber , then a redundant fan has failed.
  

Note: In a redundant fan configuration, the error message fan system not fully redundant will also be displayed at POST if any redundant fan slot is left unpopulated or if a redundant fan has failed.