IPN error -- IPN URL encoded -- where do I find this?

[jgold723]

We've been getting error messages saying PayPal's IPN service can't connect with the page it's supposed to (ipn_main_handler.php).

The URL that the PayPal error message gives us is:
"https%3A%2F%2Fbrooklyntweed.net%2Fstore%2Fipn_main_handler.php"

GoDaddy (our host) says it's because the the URL is encoded. But where would I find this? I've checked the PayPal admin interface for IPN and it appears to be correct (no encoding). I've checked the admin interfaces for the PayPal modules on the cart and I don't see that url (or any url) in there.

I've also used the developer tool kit the search for this url and it comes up blank.

Can someone tell me where this url would be living?

Thanks,

John

[cvhainb]

Try to go to admin - modules - payment- paypal

and edit it.

[jgold723]

Do you mean via the admin interface, or the files themselves?

[cvhainb]

Yes, admin interface.

[lat9]

We've been getting error messages saying PayPal's IPN service can't connect with the page it's supposed to (ipn_main_handler.php).

The URL that the PayPal error message gives us is:
"https%3A%2F%2Fbrooklyntweed.net%2Fstore%2Fipn_main_handler.php"

GoDaddy (our host) says it's because the the URL is encoded. But where would I find this? I've checked the PayPal admin interface for IPN and it appears to be correct (no encoding). I've checked the admin interfaces for the PayPal modules on the cart and I don't see that url (or any url) in there.

I've also used the developer tool kit the search for this url and it comes up blank.

Can someone tell me where this url would be living?

Thanks,

John

When I go to brooklyntweed.net/store, I'm redirected to brooklyntweed.net. I don't know where the redirect is coming from, but my guess is that that's the source of your problem. What is the full text of the PayPal error message? It might help to identify the solution.

[jgold723]

When I go to brooklyntweed.net/store, I'm redirected to brooklyntweed.net. I don't know where the redirect is coming from, but my guess is that that's the source of your problem. What is the full text of the PayPal error message? It might help to identify the solution.

I believe there's a redirect that the original designer put in to send people who try to go straight to the store site. But I don't believe that has any effect if you use the full url to the ipn_main_handler.php file.

[jgold723]

Hi CVINHAIB -- I looked in the admin interface -- none of the PayPal modules have an entry for the url to the ipn_main_handler.php file. At least not that I could find.

[cvhainb]

I think when you edit the paypal that you are using, you will see url of ipn main handle.

[jgold723]

I did and it isn't there -- there's no field for the Instant Payment Notification URL -- unless I'm looking in the wrong spot.

[mc12345678]

Hi CVINHAIB -- I looked in the admin interface -- none of the PayPal modules have an entry for the url to the ipn_main_handler.php file. At least not that I could find.

I think when you edit the paypal that you are using, you will see url of ipn main handle.

Look at the paypal information on the "page" before you click the edit button, or at the top of the window after you do, there is some information about the path that should be setup for the store to function with PayPal.

Somewhat surprised that no one has talked about the settings in your configure.php files related to where your store really is (subdirectory of shop, or in root directory), or about .htaccess redirects, but almost more impportantly, if you the store owner log into your host account/ftp into it, does the ipnhandler.php file exist in a subdirectory of shop off of your public_html folder? We need to verify the basics to help chase down this error. I think it was asked earlier also to provide as much of the error message as security allows. Like if need to obscure the admin directory or similar, please do.

The encoding that was referred to, may have only been done at the "last moment" in order to store the content of the URI in a fully readable format. If presented decoded, then it may be that a space or some other character would look right, but would process wrong. By showing the standard replacement values for forward slash, colon, etc, the link canbe verified to be correct. But... I could be wrong about that as well. Just thinking of most likely reasons to have this issue