View Full Version : All sites down for days
cheesypeas
17-05-09, 02:12
Since Friday all v1 and v2 sites have been down displaying the following error for v1:
WSDL access check: NO (The WSDL file cannot be loaded from [http://api.productserve.com/v1/ProductServeService?wsdl])
and for v2:
WSDL accessible: NO ( The WSDL file cannot be reached at http://api.productserve.com/v2/ProductServeService?wsdl )
They had been working fine for years and I haven't made any changes, any advice?
My V1 sites were all over the place the last few days - some working - some not.
Contacted my host and the productserve was being firewalled for some reason. They cleared that and all is lovely again!
May just be worth contacting your host.
Hello,
Just to reiterate what Bud has correctly said...
When this error comes up it means that you cannot contact our WSDL. Meaning either you are not connected to the internet :D or that you are being firewalled.
Check with your host and if that fixes the problem please post back the fix so that other users can take note.
Regards
Who are you hosting with cheesypeas?
It's not Eukhost is it (they're mine)?
cheesypeas
18-05-09, 13:15
You're both absolutely correct; it was a problem with my host. And to answer your question Bud no I'm not with Eukhost but with micfo. I sent them a message, didn't get a response but about ten minutes later the sites were up and running again.
Our site is down and reporting:
WSDL access check: NO (The WSDL file cannot be loaded from [http://api.productserve.com/v1/Produ...eService?wsdl])
We have contacted our host regarding firewall issues - but does anyone know what has changed that is causing the problem.
We too have not encountered any problems with the site following the initial installation.
Why are these problems arising now
The problem has arisen again
Our site is reporting
ShopWindow Client v1.0 status
WSDL access check: NO (The WSDL file cannot be loaded from [http://api.productserve.com/v1/ProductServeService?wsdl])
PHP check: OK
Template folder writable: YES
USER_ID set: YES
USER_PASS set: YES
We have checked with our host who have stated that it is a script issue
Hello,
This issue is all about your script not being able to contact the WSDL.
It is normally down to either not being connected to the internet (which I doubt is the problem) or that there is a firewall blocking access.
How did it get fixed last time?
Cheers