Store will not reconnect.

0
Answered

I'm running into issues getting my store to reconnect to shipping easy. It appears the wsdl is loading when I access https://www.filteright.com/index.php/api/v2_soap/index/?wsdl=1 and I've configured the shipping easy user/api token. Is there something else causing the store connection to fail? 

Please let me know if you need additional details.

Thanks,

Mike

Official Comment

Hi Mike,

Thanks for posting in our forums! I took a look at your connection for your URL and it appears your SOAP is not loaded: https://www.filteright.com/api/v2_soap

You or your developers will need to load your SOAP for you to be able to connect. You will also want to make sure that your WS-I is disabled under System > Configuration > Services [Left-Nav] > Magento Core API in Magento (instructions in the link above).

For your reference, once you load your SOAP, we do have a guide on how to integrate Magento with ShippingEasy.

Please let me know if you are able to connect! 

Warm regards,

Taylor Painter

 

Comment actions Permalink
0

Thanks for the reply Taylor! I confirmed that the WS-I Compliance is disabled in our settings. I'm able to load the wsdl via https://www.filteright.com/api/v2_soap?wsdl, so it appears that I have SOAP enabled. Do you happen to have a php script or some other mechanism that I could use to test how shipping easy is invoking the SOAP methods on filteright? 

Comment actions Permalink
0

Hi Mike,

When we load your SOAP here: https://www.filteright.com/api/v2_soap we are getting this error: Soap? SOAP-ERROR: Parsing WSDL: Unexpected WSDL element <operation>

We typically only see that if WS-I is turned on. It may be worth a second look on your end to make sure it is disabled. That said, we did a search and found that this may be helpful for your developers: http://stackoverflow.com/questions/5873520/wsdl-error-soap-error-parsing-wsdl-couldnt-bind-to-service

In addition, this is not a Magento API error, but looks like an Apache security module error. As far as my developers can tell, it looks like your site is being hosted at InMotion. They have a support page for this error here: http://www.inmotionhosting.com/support/website/error-numbers/406-error

Let me know if that works!

Warm regards,

Taylor Painter

 

Comment actions Permalink
0

I finally managed to figure out why my WSDL could not be parsed, and I believe I've found a workaround for that issue. I also updated the mod security settings so that the request would no longer result in a 406. Unfortunately I'm still experiencing the issue where my store will not integrate with shipping easy. Would you mind letting me know what the latest error is when trying to parse/connect to https://www.filteright.com/index.php/api/v2_soap/index/?wsdl=1.

Thanks,

Mike

Comment actions Permalink
0

Hi Mike,

When I go to load your SOAP here: https://www.filteright.com/api/v2_soap

I still see this error: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://www.filteright.com/index.php/api/v2_soap/index/?wsdl=1' : failed to load external entity "https://www.filteright.com/index.php/api/v2_soap/index/?wsdl=1"

We only see this occur when WS-I compliance is turned on, we suggest you make sure that is turned off in order to integrate!

Warm regards,

Taylor Painter

Comment actions Permalink
0

Howdy Taylor,

How are you loading the WSDL? I just want to make sure I can reproduce the same error you're seeing so I can hopefully figure out what the issue is. I double checked the WS-I compliance and unfortunately it's not turned on, so my hope for an easy fix is gone.

Comment actions Permalink
0

Hi Mike,

That's too bad! I was hoping for an simple settings issue as well.

This is what my developer found:

1. It looks like you entered the incorrect url when you integrated: "https://70.39.147.108/index.php" raises an SSL error, since the IP address doesn’t match the domain on the SSL certificate.


2. Once we updated stores url to "https://www.filteright.com/index.php", our integration started getting the error that was mentioned in the description:
SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://www.filteright.com/index.php/api/v2_soap/index/?wsdl=1' : failed to load external entity "https://www.filteright.com/index.php/api/v2_soap/index/?wsdl=1”
A search for ‘Magento "SOAP-ERROR: Parsing WSDL: Couldn't load from”’

This leads us to think this is a likely solution: http://stackoverflow.com/questions/14822866/magento-soap-api-working-locally-but-not-remotely?lq=1/#answer-14823827

It looks like Magento is making a request to itself to lookup the WSDL, but the servers request to itself is failing with that error.


You will need to fix the configuration issue that is causing the problem on your end and to be able to get: https://www.filteright.com/api/v2_soap to load without the SOAP-ERROR before you can reconnect.

Warm regards,

Taylor Painter

Comment actions Permalink

Add a Comment

Please sign in to leave a comment.