CP broken

B

bro

Perch
I got a message from Paypal yesterday saying IPN wasn't responding for my client hosting payments.

"Please check your server that handles PayPal Instant Payment Notifications (IPN). IPNs sent to the following URL(s) are failing:
http://cp.xxxxxx.net/psoft/servlet/psoft.hsphere.payment.PayPalServlet"

Neither could I get to the admin section through the CP.

The response I got on my ticket was unhelpful. Not only did support simply change the CP URL to http to get it to work, but they told me I had not set up the Paypal gateway, apparently without checking to see if it was set up or not. (It's been working for 3 years or so.)

The problem seems to have been caused by the port for my Reseller CP URL (which has always been on https) having changed to 80 (by hsphere?) I've now changed it back to 443 and that seems to have fixed it. Hopefully that will fix the Paypal problem, too, and support will recognise the real problem next time.
 
Bro,

The CP URL can be changed in the first screen as you login, we do not change that unless the URL in MOST cases (there are a few like service domain expired, where it simply has to be changed for the CP to work, it would then move to the temp url that is a subdomain of the main CP url). When there is an SSL port ocnfigured, we don't change it to non SSL, if an SSL cert is expired, the connection is still technically encrypted and secured, just not from a 'verified non expired' certificate, which can easily be added to exceptions on firefox and allowed to continue.

If the URL was set at paypal as https:// then being http:// would be a wrong URL for PayPal and cause a problem.
 
Stephen,

It's been set to https and 443 for a long time. The cert has been expired for a year or so, so that's not a problem. I first noticed it had changed to https and 80 when I went to make a manual credit, and of course couldn't get into the admin section because of that. I hadn't changed it, so I assume it was done automatically by the system.

I couldn't recall what it should be at the time so put in the ticket, and support changed it to http, then told me I hadn't set up Paypal. I don't mind being told when I'm doing things wrong, but it would be better for all concerned if they'd actually tried to diagnose the problem.
 
bro said:
Stephen,

It's been set to https and 443 for a long time. The cert has been expired for a year or so, so that's not a problem. I first noticed it had changed to https and 80 when I went to make a manual credit, and of course couldn't get into the admin section because of that. I hadn't changed it, so I assume it was done automatically by the system.

I couldn't recall what it should be at the time so put in the ticket, and support changed it to http, then told me I hadn't set up Paypal. I don't mind being told when I'm doing things wrong, but it would be better for all concerned if they'd actually tried to diagnose the problem.
Click to expand...
Actually they'd be right is paypal wasn't matching to the http and https URLs that 'paypal' hasn't been setup, to reflect this change in ports from non ssl to ssl.

However, what you did was change it back to what you did have setup, so it works properly again.

I have not heard of the port changing automatically, I am running it by some others as well to see if we've seen this before.
 
You must log in or register to reply here.
Back
Top