2Checkout.com » error

Why do I get an HTTP Error 500 (Internal Server Error) on Passback?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

An HTTP Error 500 (Internal Server Error) indicates that there is a problem inside of your script or the servers configuration. This error is most likely caused by a typo in the code or an invalid or illegal use of a function within the script. For the pass back to function correctly, then your script must be correctly set up.

HTTP errors are not generated specifically by 2Checkout. They are a part of the HTTP protocol and are common amongst all web servers. It is therefore beyond the realm of 2Checkout’s support to provide you with specific instructions for making these changes as every server is set up differently and 2CO does not provide server administration services as part of our support plan.

For assistance with debugging your scripts, we suggest that you contact your server’s administrator, webmaster, or hosting provider’s technical support staff.

We have observed that this error is experienced in certain web browsers more than in others, in particular within Internet Explorer. If your return page or script does not output at least 530 characters, this can potentially cause a MIME header error. Mozilla based browsers such as Firefox seem to be able to handle these pages and will display either the real error or the small output when Internet Explorer has problems. Since this issue is an issue with the browser software itself, there is little 2Checkout can do to control this. If you are receiving this error, please try to increase the output that your return page generates to more than 530 characters or try a different web browser to see if you observe different results. Note that this is not a solution for all HTTP 500 error messages, but it is meant to be a useful step in debugging your script and has been reported as a successful step by some of our other users.

Why do I get an HTTP Error 404 (File Not Found) on Passback?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

An HTTP 404 File Not Found error indicates that the URL specified as for your script is incorrect. For the pass back to function, 2CO must be able to locate and access the script and post the variables to it.

HTTP errors are not generated specifically by 2Checkout. They are a part of the HTTP protocol and are common amongst all web servers. It is therefore beyond the realm of 2Checkouts support to provide you with specific instructions for making these changes as every server is set up differently and 2CO does not provide server administration services as part of our support plan.

To correct this issue, follow these steps:

Login to your account.
Click on the Account tab and then select the Site Management sub-category.
Check the URL that is currently entered under the Approved URL field and make sure that it is correct.
Click Save Changes.

Why do I get an HTTP Error 403 (Forbidden) on Passback?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

An HTTP 403 Forbidden error indicates that due the set up of your script and/or server, the viewer does not have permission to view this page. For the pass back to function, 2CO must be able to access the script and post the variables to it.

To test and see if your file is working correctly:

Open your web browser.
Type in the full URL to your script or return page (including the http://www. part) and press enter.
If you receive the message again, the problem is in your script and/or on your server. Note that the exact wording of the error message may vary slightly depending on your browser and your server. But if you see something about ‘forbidden’ or ‘error 403′ then the information above pertains to your situation.

Why do I get an HTTP Error 405 on Passback?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

This is a problem with your script and/or your web server. The error means that you are attempting to pass back to a file does not have the necessary permissions on the server to receive Post information from another script. If you have administrative or root access to your server, be sure that this file has been set up to be treated as a script and that the appropriate user accounts have read and execute permissions on the script. If you are in a shared hosting situation, please contact your server administrator or the support department for your host.

To test and see if your file set up is correct:

Create a new text file using a text editor such as Windows Notepad.
Paste the following code into this new file:
Replace “[full URL to Your Script Here]” with the URL of the script you are attempting to pass back to. Remember that this should be the full URL of your script, including the http:// portion.
Save the file as an HTML file, such as “test.html” or “test.htm” to your desktop and close your text editor.
Open the file in your web browser and click the “Test Script” button that is displayed.
If you receive the message again, the problem is in your script and/or on your server. Note that the exact wording of the error message may vary slightly depending on your browser and your servers configuration. If you see something about “method not allowed” or “error 405″ then the information above pertains to your situation.