Good morning,
Here is an example of a simple get with CURL which is successful on other servers and my laptop but fail on this specific server. I don’t even need to make a real call to the API to get a 403 that’s why I had the feeling the IP was banned and it was not due to malformed API Call or missing permission on the API token.
* Expire in 1 ms for 1 (transfer 0x5611abe9b110)
* Trying 104.17.203.204...
* TCP_NODELAY set
* Expire in 149997 ms for 3 (transfer 0x5611abe9b110)
* Expire in 200 ms for 4 (transfer 0x5611abe9b110)
* Connected to api.hubapi.com (104.17.203.204) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Cloudflare, Inc.; CN=hubapi.com
* start date: Apr 7 00:00:00 2023 GMT
* expire date: Apr 6 23:59:59 2024 GMT
* subjectAltName: host "api.hubapi.com" matched cert's "*.hubapi.com"
* issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x5611abe9b110)
> GET / HTTP/2
> Host: api.hubapi.com
> User-Agent: curl/7.64.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 403
< date: Thu, 27 Apr 2023 06:54:08 GMT
< content-type: text/plain; charset=UTF-8
< content-length: 16
< x-frame-options: SAMEORIGIN
< referrer-policy: same-origin
< cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< expires: Thu, 01 Jan 1970 00:00:01 GMT
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=4UOIpfVp%2BGnnLZEhI1X4rEaLraDkhxoNUZmxC4JdrFBv580u1S3%2F26S5mYDToVNgNTV5ONhqsHNr%2BL7UI8zINaXfNnbGeFH13XSP8ayE6H2n35FcSikUffoft2%2B5y5k%2F"}],"group":"cf-nel","max_age":604800}
< nel: {"success_fraction":0.01,"report_to":"cf-nel","max_age":604800}
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< server: cloudflare
< cf-ray: 7be52709f9eb9b88-FRA
< alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
<
* Connection #0 to host api.hubapi.com left intact
error code: 1006
It is an account with a paid subscription.
Regards,
Aloïs
Thanks for reaching out. I’m sorry to hear you have been dealing with this issue. Let’s collect some more info and I’ll work on our next steps.
)