Free Support Forum - aspose.cloud

Convert WordPress Post to DOCX with Aspose.Words Exporter WordPress Plugin throws 502 Bad Gateway error

I installed the Aspose.Words Exporter to export my content. I was able to install it and activate it once, but I kept getting a WordPress critical error every time I tried to export my content. I uninstalled and reinstalled the plugin, but I have to reactivate the API and now can’t do that. I’m getting a 502 Bad Gateway error now. Please help!

@cjwerth

I am afraid we are unable to reproduce the issue at our end. Please ensure you are using the latest version of Aspose.Words Exporter WordPress Plugin. However, if you still face the issue then, please try to enable debugging and share error details/screenshot along with the APP SID from the Plugin setting page. We will try to investigate it further.

Hi Tilal,

Here is the error I am getting:

Fatal error : Uncaught Error: Call to undefined function GuzzleHttp_idn_uri_convert() in /home/govirgin/public_html/wp-content/plugins/backupbuddy/vendor/guzzlehttp/guzzle/src/Client.php:220 Stack trace: #0 /home/govirgin/public_html/wp-content/plugins/backupbuddy/vendor/guzzlehttp/guzzle/src/Client.php(113): GuzzleHttp\Client->buildUri(Object(GuzzleHttp\Psr7\Uri), Array) #1 /home/govirgin/public_html/wp-content/plugins/backupbuddy/vendor/guzzlehttp/guzzle/src/Client.php(130): GuzzleHttp\Client->sendAsync(Object(GuzzleHttp\Psr7\Request), Array) #2 /home/govirgin/public_html/wp-content/plugins/aspose-doc-exporter/vendor/aspose-cloud/aspose-words-cloud/src/Aspose/Words/WordsApi.php(48344): GuzzleHttp\Client->send(Object(GuzzleHttp\Psr7\Request)) #3 /home/govirgin/public_html/wp-content/plugins/aspose-doc-exporter/vendor/aspose-cloud/aspose-words-cloud/src/Aspose/Words/WordsApi.php(48352): Aspose\Words\WordsApi->_requestToken() #4 /home/govirgin/public_html/wp-content/plugins/aspose-doc-exporter/vendor/aspose-cloud/aspose-wo in /home/govirgin/public_html/wp-content/plugins/backupbuddy/vendor/guzzlehttp/guzzle/src/Client.php on line 220

@cjwerth

We are sorry for the inconvenience. We have logged a ticket WORDPRESS-207 in our issue tracking system for further investigation. We will share our findings with you soon.