Opened an email and it said http/1.1 500 internal server error

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.

I have the setup instructions posted, click on the link below and follow those instructions. If after following those instructions you are still having a problem feel free to contact me.

http://gfbm.net/selfhelp_kmacopier_scan_to_email_setup_command_center.htm

its internal server error, just try after sometime, you not getting that particular website mean use this website www.vtunnel.com , its the client website form there you can assess any site which is not opening in your server.

Good luck! if you problem is solved don't forget to rate

Go here and follow instructions

http://email.about.com/od/outlooktips/qt/et_getyahoofree.htm

Check your computer for malware, because you should be logging on with https, and not an unsecure connection. Free options i suggest are avast antivirus, www.avast.com, and ad-aware, www.lavasoft.com.

Additionally, you may want to see if you have the same error with a different browser, such as mozilla's firefox, www.firefox.com

If you are running two versions of ASP.NET, you may get HTTP:/1.1 500 Internal Server Error when creating a new Web project or opening an existing Web project in Visual Studio.

This problem may occur when IIS is not sure what version of ASP.NET to use or where to locate ASP.NET files. One of the following solutions should fix the problem.

Solution 1.

1. Remove web.config file from inetpub/wwwroot directory
2. Go to IIS, Right click on Default web site / All tasks / Check server extensions and let it run
3. Reset IIS by right click on IIS or call iisreset from Run command

Solution 2.

1. Install ASP.NET again using the following command from your Run command: C:WINNTMicrosoft.NETFrameworkv1.1.4322aspnet_regiis.exe
   Make sure to change the windows folder and ASP.NET version folder with the version what you want to install
2. Reset IIS

Solution 3. Applies to Windows Server 2003
Note: This is a Microsoft KB article:

When you try to create a new Microsoft ASP.NET 1.1 application after you change the script mapping of the existing ASP.NET 1.1 Web application to ASP.NET 1.0 on a Microsoft Windows Server 2003-based computer, you may receive the following error message:
The Web server reported the following error when attempting to create or open the Web project located at the following URL: 'http://localhost/822319ev1'. 'HTTP/1.1 500 Internal Server Error'.
CAUSE
This issue occurs because Windows Server 2003 does not allow two versions of ASP.NET to run in the same application pool.
WORKAROUND
To work around the problem, do one of the following:
Restart the IIS before you create a new ASP.NET 1.1 application. At the command prompt type the following command: iisreset
OR -
Create an ASP.NET application in a separate application pool. Create the script-mapped application (ASP.NET 1.0) in a separate application pool -- for example, in the ScriptMapappPool application pool. Then, create a new ASP.NET 1.1 application in an application pool other than ScriptMapappPool. For more information about how to create an application pool, visit the following Microsoft Web site: Configuring Application Pools http://msdn.microsoft.com/en-us/library/1kdfe21k(VS.80).aspx