Hi everyone,
About 1.5 hours ago, I started getting 403 failures with the following response body:
error code: 1107
Searching around I can’t find a single reference to this error code.
The access token has expired, and I can’t refresh it, since it returns the same error.
Any ideas what it might be?
In the developer portal, in the “Monitoring” tab, I’m not even seeing the requests come in (last request I see was successful, at 10:57am EDT)
Thanks,
Phil
I am having the exact same issue.
Exact same issue, began at exact time as yours. Contacted support and they recommended I come here. Anyone have any thoughts?
A little more info that makes this even more puzzling: when I make the call in Postman on my dev machine, it works fine. But when I make the exact same call on my live server via cURL on the command line, I get those 1107 errors
That really is strange!
Looks like it spontaneously fixed itself for me now, after throwing errors for past 4 hours
Still broken for me unfortunately, but glad it’s working for you now!
Still broken for me, as well.
We have exactly the same issue since yesterday 17:00 CEST.
Same for me - it seems like it could be related to Cloudflare blocking the IP address that requests are coming from. See the error description here.
Might be something like that, especially with somebody else here finding that it worked locally but not on the server.
but I can’t find that error code on the cloud flare page? (Error code 1107)
You are correct. I relied too heavily on google’s search - looking for 1107 but returned the 100x error page.
I’ve re-run the failing jobs and they’re still failing so, at least for me, the issue has not been resolved yet.
Odds are it is something like this, and it’s getting blocked before the request even gets to Hubspot, and that’s why it doesn’t even show up in the API logs? If Cloudflare (or something like that) is blocking it earlier in the chain, it would explain it.
Just frustrating and nothing we can do about it but wait? Do Hubspot staff look at these messages? Or is this just for community supporting each other, and in this case it looks like there’s actually nothing we can do?
I contacted Hubspot support via Phone. They asked for the call so they can reproduce the issue. Gave it to them and also referred to this community thread.
It’s a weird issue, because we also ran the code locally and it worked just fine. Only when we run it from our server it gets its access denied.
Either Cloudflare or Hubspot is doing some blockage.
I’m currently trying to see if I can make my requests through a proxy and see what’s happening.
Thanks for talking to them and referring them to this thread too, really appreciate it!
Let me know what you find 
With a proxy it seems to be working. The proxy I’m testing at the moment is being a bit unreliable, but when the proxy works the requests are getting through fine.
So overall it definitely feels like there’s some IP blocking going on, so other than figuring out how to get/use a different IP, it doesn’t feel like there’s much we can do (other than hope that the block magically goes away, as it did for @mainespotter)
Hello!
I have an idea that it caused by fact that their CDN provider returns error “error code: 1107” when we do query via IPv6:
curl -6 https://api.hubapi.com
HTTP/2 403
< date: Tue, 29 Aug 2023 15:04:55 GMT
< content-type: text/plain; charset=UTF-8
< server: cloudflare
When I disable IPv6 it works just fine:
curl -4 https://api.hubapi.com
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
It may be configuration error or some third party issue.
Forcing IPv4 did the trick for me. Thank you!
I think you’ve got it, I added a new static IP on my server and had to force IPv4 in order to use it, so indirectly did exactly what you said.
Removing the new static IP but still forcing IPv4 connections fixes it too, looks like the IPv6 address is getting caught up for some reason.
I’ve updated the accepted solution to your post!