1
HTTP/1.1 500 Internal Server Error
Question asked by Michel Blais - 3/16/2021 at 3:36 PM
Answered
We are doing an re-design of our website and are trying to test the eCommerce Import/Export interface for WooCommerce, with Atrex 19.1x, Import Version 1.0.0.1, build date 2020-10-19.

We are getting an error when testing the settings.  

Unable to connect to the API URL, Error Message: HTTP/1.1 Internal Server Error.

The URL is up and running and accessible.  The eCommerce interface does work fine with our current live website.

Any ideas what the issue could be?

4 Replies

Reply to Thread
0
Terry Swiers Replied
Employee Post
Enter the following into a browser after replacing <domain> with the domain of your site:  


Do you see a big chunk of json that starts with something like {"namespace":"wc\/v3","routes":{"\/wc\/v3":{"namespace":"wc\/v3","methods":["GET"],"endpoints"   or do you get the internal server error?

0
Michel Blais Replied
When entering the information above, I do get this error: 

"There has been a critical error on this website."

0
Terry Swiers Replied
Employee Post
So, that tells us that there is a problem with the API layer, either at the WooCommerce or WordPress level.   The first step to try and track this down would be to disable the Atrex - SyncHelper plugin and run the same check again.  
If you see the json response after removing the SyncHelper plugin, that means we've done something in our plugin that isn't working, which needs to be tracked down and fixed.

If you still see the error, then the problem is something in the WooCommerce or Wordpress installation that isn't working correctly, which in turn will prevent our utility from working. Your site admin should be able to view the server logs to see more detail on the error.

Two additional places where you can look to see if there are any obvious issues are available from the main Wordpress admin page. The first is "Tools - Site Health" which has both a status and info page. The status page may show you any critical errors that need to be resolved. The second is "WooCommerce - Status". The first tab shows a lot of information about the WooCommerce status, and should show any obvious errors in the site.


0
Michel Blais Replied
Marked As Answer
Hi.  The Web developer saw your question above and found the issue.

There was some conflict in the main WooCommerce translation plugin.

Problem has been resolved and export is working now.  Thanks for your help.

Question can be close.

Reply to Thread