A working site suddenly shows "No Shipping Method Found" with FedEx configured

  • Posts: 268
  • Thank you received: 7
  • Hikamarket Frontedition Hikamarket Multivendor Hikaserial Standard Hikashop Business
7 years 3 months ago #275943

-- url of the page with the problem -- : aquacorals.com
-- HikaShop version -- : 3.1.1
-- Joomla version -- : 3.7.4
-- PHP version -- : 7.0.19
-- Browser(s) name and version -- : FireFox 53.0.3
-- Error-message(debug-mod must be tuned on) -- : No Shipping Method Found

Our site suddenly has started to not work with the FedEx shipping method. Debug shows "Could not connect to host"
Other shipping methods seem to be responding appropriately.
Last known order using FedEx was August 3rd
Updated tonight to HikaShop Business 3.1.1 [1708111031]
Previous build/download was dated August 2nd

Any thoughts why this should suddenly start happening?

Please Log in or Create an account to join the conversation.

  • Posts: 82863
  • Thank you received: 13372
  • MODERATOR
7 years 3 months ago #275949

Hi,

So if I understand you mean that it started not working right after you updated HikaShop on the 2nd of August ?
Which version of HikaShop did you had before that ?

Since the release of the 3.1.1, we've added only 1 patch to the Fedex plugin: correcting the handling of the "use dimensions" setting and improving the display of error messages.
So in both cases, it shouldn't change anything for the plugin being able to connect to the Fedex server.
Do you have more information than just "Could not connect to host" in the debug ? How did you configure your Fedex shipping method ? Could you provide a screenshot ?

Please Log in or Create an account to join the conversation.

  • Posts: 268
  • Thank you received: 7
  • Hikamarket Frontedition Hikamarket Multivendor Hikaserial Standard Hikashop Business
7 years 3 months ago #276006

Hi,
I can not guarantee that it started immediately after that update dated August 2nd, just that the last successful order was on the 4th. I may have updated the installation on the 5th or after, just don't remember.
The version of Hikashop prior to that would have been dated 7/27 or 6/21

I've attached screenshots of the shipping configuration and the debug report with the account numbers etc removed.

Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 268
  • Thank you received: 7
  • Hikamarket Frontedition Hikamarket Multivendor Hikaserial Standard Hikashop Business
7 years 3 months ago #276015

Just found this announcement on FedEx's site referencing new urls for web services. Could this be the culprit?
www.fedex.com/us/developer/announcements.html

Please Log in or Create an account to join the conversation.

  • Posts: 26158
  • Thank you received: 4028
  • MODERATOR
7 years 3 months ago #276016

Hello,

No I don't think that's really related because

If you are currently using undefined/non-standard URLs (SOAP) for the services, please check your URLs prior to January 2018 to ensure your services with FedEx continue and will not be interrupted. See below the corresponding URLs for the impacted FedEx Web Services WSDLs.

So I don't think they closed down the "old" URL and if it was the case, I think that we would have a lot of feedback on it.
But, it is sure that it would be good to get the new WSDL file before January 2018.

Right now, I really recommend you to contact your web hosting in order to see what is the issue for contacting the fedex server.
Because, even if the URL will migrate in the future, the "could not connect to host" cannot be related since the domain "fedex.com" still exist and won't disappear ! So if it was really the fact that the services are not more on the fedex.com server, you would have another error message giving you an incorrect server answer, not a "could not connect to host".

Regards,

Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.

Also helping the HikaShop support team when having some time or couldn't sleep.
By the way, do not send me private message, use the "contact us" form instead.

Please Log in or Create an account to join the conversation.

Time to create page: 0.206 seconds
Powered by Kunena Forum