[adamb]

Hi,

Thank you for confirming what we’ve been trying to say to our webhost. We’ve been getting nowhere so far, although must admit our webhost have been doing their best to help. However, they are reluctant to accept that it may be their server at fault.

As you suggested, I tried to send the IPN to our homepage using the Sandbox IPN tool and again receive the message “IPN delivery failed. Unable to connect to the specified URL. Please verify the URL and try again”.

The website is currently in development but here’s the URL [http://www.royaltyfreemusic.uk.com]

Thanks very much for your help and any additional thoughts you may have about this would be most appreciated.

Many thanks

Adam

[adamb]

Hi,

Still having no luck with this.

I upgraded to the new version this morning, but to double check I just did a fresh install and did another test transaction in Sandbox and the ipn retries about 8 times and then fails.

Any other ideas you can think of? Really appreciate the help on this.

Many thanks

Adam

[adamb]

Hi,

Thanks for your reply.

I tried the advice in that post the other day and just tried it again with no luck.

I get to step 5 where I put the IPN URL in the Sandbox simulator and I receive the message “IPN delivery failed. Unable to connect to the specified URL. Please verify the URL and try again”.

I told this to our webhost but they still aren’t convinced it’s their server as they say they have checked everything they can possibly think of.

They even contacted PayPal themselves and PayPal asked us to do test sales in the Sandbox environment and from the failed IPNs they said “This indicates that most likely your script is not closing the fsock session correctly. You will need to adjust you script and make sure that it is closing hte fsock session”.

This is where we are up to now with both PayPal and our webhost thinking it’s to do with the script. I even tried putting our website URLs in the IPN notification field within PayPal account but a message appears saying the URL can’t be validated.

I also know that PayPal advised our webhost to whitelist some of their IPs but even that didn’t solve the issue.

Any further help would be really appreciated.

Many thanks

Adam

[adamb]

ah ha… manage to see the error again… here it is, hope it helps

Awarding commission

Warning: Cannot modify header information – headers already sent by (output started at /home/ohmessag/public_html/wp-content/plugins/wp-cart-for-digital-products/eStore_manual_gateway.php:125) in /home/ohmessag/public_html/wp-content/plugins/wp-cart-for-digital-products/eStore_manual_gateway.php on line 131

[adamb]

Hi Amin,

I have cleared my cache and cookies but still have the problem.

Here is the page, http://www.onholdmessagingdirect.com/packages/

Just add any product. Does the error happen for you?

Cheers

Lee

[adamb]

Hi Amin

Thanks for the update, however there is still a problem. On the first attempt testing the manual payments I got an error. The same as the initial problem. I repeated the process to try and get a copy of the message but since then the manual payment is always sending me to PayPal.

Cheers

Lee

[adamb]

Hi Amin

Thank you for your quick response. I understand what you are saying about the example sites, it would be a lot of work to keep on top of those.

The update has resolved the problem but the affiliate system does not add the commission to the affiliate account for manual payments. I have checked the following boxes so would expect this to be sending affiliate commissions.

*Automatically Update Customer & Products Database

*Automatically Award Affiliate Commission

It works fine with paypal payments.

Any ideas?

Cheers

[Author]

Posts