We’ve recently had an employee leave the business who setup our HubSpot plugin in wordpress. Once he left I started seeing the “unable to load HubSpot There was a problem connecting to HubSpot. Please try again.” error on every form.
The plugin was showing the error that the user who installed the plugin no longer had access to HubSpot forms so, I reset the plugin using my super admin account to link to HubSpot however the forms still display the same error described above despite no issues being displayed within the plugin.
I’d like to tag in some of our Top Contributors to see if they have any tips on this one – Hi @franksteiner79@karstenkoehler@DanMYD Do any of you all have any ideas for @DHull ?
The fact that you’ve already reconnected the plugin as a Super Admin but the forms are still failing makes me think the current OAuth connection isn’t the issue. It may be that some of the old plugin configuration is still being retained.
One thing that’s worked for others is performing a full reset of the plugin’s stored configuration rather than just reconnecting through the UI:
Go to /wp-admin/options.php.
Search for options beginning with leadin_.
Clear those values and save.
Then reconnect the HubSpot plugin.
This forces the plugin to recreate its configuration from scratch, whereas a standard reconnect can sometimes leave stale settings behind.
I’d also recommend clearing any WordPress, browser, or CDN cache before testing again, just to make sure you’re not loading stale form assets.
If the issue still persists after that, open your browser’s Developer Tools and check the Console or Network tab for any 401/403 or missing scope errors. That can help determine whether it’s still an authentication issue or something else.
Hopefully that gets you pointed in the right direction.
Since you’ve already reconnected the plugin with a Super Admin account, it sounds like the WordPress connection itself isn’t the issue anymore.
I’d check a few other things:
Clear any WordPress, server, and CDN (e.g., Cloudflare) cache.
Confirm the forms still exist in HubSpot and haven’t been deleted or replaced.
Open the browser’s Developer Tools (F12 → Console/Network) and see if any HubSpot JavaScript requests are failing or being blocked.
Temporarily disable other plugins and switch to a default theme to rule out a plugin or theme conflict.
If you’re using a security plugin or firewall, make sure it’s not blocking requests to HubSpot.
If the plugin shows as connected but every embedded form still reports “Unable to load HubSpot”, I’d also try disconnecting the plugin completely, deleting it, reinstalling the latest version, and reconnecting it with your Super Admin account.
One question: are all HubSpot forms affected, or only forms that were created by the former employee? That detail could help narrow down whether it’s a permissions issue or a site-wide integration problem.
Hey, I have fully disconnected and reinstalled the plugin but found the same error, in the browser console I see no required scopes error either unfortunately.
Hi Menaveed, no such luck with your advice for clarity it is sitewide and on all forms. I f a form was already on the site before the employees permissions were removed then it still works however we can’t edit, update or add a new form
I’ve spoken with HubSpot support and after checking .har files, plugins and everything in between the issue is now being escalated. I’ll update this post with any resolution for anyone else who’s experiencing the same issue.
Thanks for the update—that’s a really useful clue.
Since the existing forms are still working, but you can’t edit them or add new ones, this sounds more like a permissions or integration issue than a caching problem.
I’d first verify that the WordPress plugin is connected to the correct HubSpot portal and that your Super Admin account has the required permissions to manage forms.
If everything looks correct and HubSpot Support confirms it’s appropriate, you could also try reconnecting the WordPress integration, as that can sometimes refresh the authorization after an account ownership or permission change. I’d just verify the setup first before making any changes.
If possible, let us know what the plugin logs or browser console show when you try to load or insert a form—that may provide a better clue as to where the authorization is failing.
Based on the behaviour you’ve described, I don’t think this is a WordPress caching or permissions issue anymore.
Since the forms that were already embedded continue to work, I’d try creating a brand-new form in HubSpot and embedding it manually using the standard embed code (Custom HTML block) instead of selecting it through the HubSpot WordPress plugin.
* If the manually embedded form works, the issue is most likely isolated to the HubSpot WordPress plugin’s communication with the Forms API rather than the forms themselves.
* If the manually embedded form also fails, then the issue is most likely at the HubSpot portal/account level rather than within WordPress.
At that point, I’d focus on the Network tab in the browser’s Developer Tools and inspect the actual API response (401, 403, 404, 500, etc.), as that response is usually much more useful than the Console for identifying where the request is failing.
Given that you’ve already reconnected the plugin with a Super Admin account, performed a clean reinstall, and HubSpot Support has escalated the case, I suspect the issue lies in the integration state between the WordPress plugin and your HubSpot portal rather than the local WordPress installation.
If the manual embed test also fails, I don’t believe there’s anything further to troubleshoot on the WordPress side. At that stage, HubSpot Support would need to investigate the account or integration internally, as it points to a backend issue rather than a site configuration problem.
It ended up being an embarrassingly simple fix, our internal support team figured it out.
On the WordPress plugin under the domain subpage there is a button to clear the cache and after clicking that it worked instantly.
It seems even when clearing the cache in your browser and deleting the plugin from WP entirely and reinstalling you need to reset the cache this way.
We don’t use HubSPot for anything on the site other than forms so naturally the domain setting within the plugin that is completely blank wasn’t our first thought.
Thanks for coming back with the resolution DHull — genuinely useful to know, and not embarrassing at all. That’s exactly the kind of thing that’s invisible until you know to look for it.
The plugin-level cache inside the Domain subpage surviving a full reinstall is the important detail here — browser cache clearing and plugin reinstallation both leave that internal cache intact, which explains why those steps didn’t work. Worth knowing for anyone who hits this in future.