mlamacchia

Hello @thehinesgaphideaway

Thanks for raising this issue. We have identified the issue and will be fixed in our next release

Hey there,

We haven’t heard from you in a while, so we’ll mark this as resolved.

Feel free to reply to this thread if you are still having problems!

Best regards

Hello,

Since the last update, we are not adding the chat for logged-in WordPress admins, to reduce noise on your portal data.

If you try to open your website in incognito mode, you will see the chat is available.

Hi @factitious, the second link refers to an issue with a 400 that is generated on the backend, which is fixed now

Would you mind following these steps:
– open app.hubspot.com and log in if you haven’t already
– capture a HAR file while you load your WordPress site on the HubSpot plugin page

Could you then send the HAR file to [email protected]? It would be also great if you could send us the list of extensions that you have on your browser so that we can try to reproduce

Hi @laetitia-godet, do you have a link to the form?
You can also send it via email to [email protected]

Hey there,

Apologies for this issue. There was an API call that was supposed to be fired only in some scenarios but got fired at every page load instead.

We deployed a patch version (8.6.15) this morning to fix the problem.

Once we understand the cause, we’ll be able to fix it soon.

The problem is that there is something that prevents cookies from being passed. Our code is tricked by thinking that they are enabled, but they are not being passed.

Do you have any chrome extensions that could be doing that (eg privacy extensions)? We managed to reproduce a similar scenario using Privacy Budger for Chrome

One workaround you could try is to disable third-party cookies altogether in your browser. This way the plugin will act like they are disabled and won’t rely on cookies for the connection. We normally don’t suggest this, because a lot of features will be disabled, but at least you can connect and have the tracking code embedded in your website

Hey all, an update on this.

We have found some cases where the authentication cookies are not read by the iframe in WordPress, causing the login to not work. We’re currently investigating this issue.

Regarding accounts getting blocked, we believe users that keep logging in due to this error are triggering a security measure that temporarily blocks their IP. If you are authenticated into HubSpot on another tab, you should not need to log in again from WordPress.

If you can’t log in from WordPress, please double-check that your third-party cookies are either disabled or that you have an exception set for *.hubspot.com (more info here).

Thank you all for the help in investigating the issue and for your patience. We’ll keep updating this thread as we progress.

• This reply was modified 3 years, 1 month ago by mlamacchia.

I can’t see anything suspicious after looking at our logs

Can I ask you both to send a HAR file of the failed connection to [email protected]?

Hi, thank you for your message!

I’ve added this to our backlog, I’ll update this thread when it’s ready.

In the meanwhile, if it’s helpful, HubSpot allows blocking traffic per IP:
https://knowledge.hubspot.com/reports/exclude-traffic-from-your-site-analytics

Hey there,
What do you mean when you say accounts were blocked? What kind of error message did you get?

Not sure how the ajax content is set up on WordPress, but I would have expected that script to be there. The best solution is to understand how why scripts are not enqueued there. Are you using any plugins for that?

A hack to get you sorted in the meanwhile is to add a hidden form on the main page (the one that loads the ajax content). Adding any HubSpot form there will force the form script to be loaded.

Hi @cedriccharles

My guess would be that the script that should be embedded here isn’t. Can you see a script pointing to https://js.hsforms.net/forms/v2.js?

Hi @shenalorlof, not sure I understand your question.

You can read here how to use our forms analytics tools to analyze forms.

Let me know if that doesn’t have what you’re looking for!

Hey there, thank you for pointing that out.

That bug should have been fixed a while ago. What version are you on?