Error: JSONP request

I am unable to replicate this error at this time through my own WordPress installation around the Advanced Domain Search functions.

I am currently running WordPress 6.1 on plugin version 2.2.7.

Can you provide more information around the error you are getting? Which version of the plugin are you using, which version of WordPress you are using?
Have you tried to uninstall and reinstall the plugin into your WordPress installation?

The error message I posted occurs when I try to do a domain search via the plugin.

I’m using Godaddy reseller plugin version Version 2.2.7

WordPress version WordPress 6.1.1

Using Elementor Pro.

On Siteground.

I have tried rolling back my server backups to a point from a while ago that I know worked at the time, and this has made no impact on the error.

I have also tried clearing my cache. No impact.

I’ve tried phoning Godaddy support and they are utterly unhelpful and have no idea what I’m even talking about.

I’m furious. I pay good money to uphold my reseller account (the annual subscription fee) and unless this is fixed then the reseller account is worthless.

I am chasing this with Godaddy support and I will post updates here as soon as I have anything useful.

I opened a premium support ticket and I’m forcing them to use it towards resolving this.

The problem is that the Reseller team don’t seem to have a clue about the WordPress plugin but I’m currently being assured that someone who knows what theyre talking about will pick this up in short order.

• This reply was modified 1 year, 11 months ago by Quentinius.

Hey, I think i found the issue with some changes lately on some firewall settings. We are working on getting this updated right now. Ill post back once we have gotten this resolved.

Hey thanks for the update. I just got the same response via Github as well. Appreciate you guys looking into this.

I just checked out my domain search and it appears to be working. So I’ll keep you posted, but this is definitely positive progress.

Thanks for your efforts.

We have pushed out a fix for the Firewall issue that was causing this error.