We are getting error “Invalid reply from server endpoint” When clicking TagDiv Cloud Template with ‘Add New’ button.
Could please help us to resolve the same
Hi,
Try to increase the WP-memory parameter, this is a guide
– https://forum.tagdiv.com/requirements-for-newspaper/
If needed contact your hosting provider for assistance with the preferred method. If there is still a problem, please send us an email at contact@tagdiv.com and provide admin login access, FTP and cPanel if possible as well. We will take a look at the issue. Include a link to this topic in the email.
Thanks
Same issue, you guys better keep testing. lol
Thanks, FWIW, I tried I safari and chrome in case it was just a browser issue. I’m all good on the server specs u need, I checked.
This was a browser (or chrome browser cache?) issue with me too, thanks to the above poster, I could access it through Microsoft Edge but not Chrome.
Hi,
@nervusvagus So it does not work in Chrome and works in Edge or other browsers? What if you clear the Chrome browser cache, does it work then? let me know.
Thanks
Sorry I just saw your reply now. It definetely seemed like a chrome (or browser cache) issue unless I’m missing something.
I didnt get a chance to test by clearing browser cache immediately but I did try accessing it with Chrome in Incognito mode (which should be same as clearing cache I guess) and it still didnt work, while working in Microsoft Edge.
But right now I can access it with both Chrome and Chrome incognite mode, everything seems to work fine.
As the first step I had also increase the WP-memory parameter.
ALSO as someone mentions here https://forum.tagdiv.com/topic/invalid-server-endpoint/ my site did not have a secure connection while I was trying as well. But that was still no reason why it worked with Microsoft Edge and not with Chrome for sure.
Thank you for the feedback, most appreciated. So the issue was resolved by increasing the wp-memory. We recommend a value of 256M which would be enough for most users.
still in investigation???
Hi sam24.info, the situation was resolved by increasing the WP memory. This can be done by your host, and this should be at least 256M. If you currently have it set to a bigger number, then ask your host to double it.
