https://linen.dev logo
Join Slack
Powered by
I've been spending all day on an issue where our i...
# infisical-help
s
I've been spending all day on an issue where our infisical integration broke a few days ago. After much digging I determined that the URL we were using to fetch secrets and the Bearer token were definitely good, but for some reason our application was getting 403 errors and curl at the command line was getting the data as expected. Is there any reason why submitting a request with 
User-Agent: Python-urllib/2.6
is supposed to be returning a 403 error? What changed around the 10th to potentially cause this breakage? I have determined that curl also breaks when setting that header.
👀 1
✅ 1
This is the URL:
Copy code
<https://us.infisical.com/api/v3/secrets/raw?workspaceSlug=*redacted*&environment=dev&secretPath=%2F>
It was broken for all secretPaths
d
Hi @Shaun Kruger, can you please share the request ID that gets returned when you see the 403 error? The response body should always contain a request ID that will help us track this down!
And can you please verify that the access token you're using is not expired?
s
Yes, I can verify that the token is not expired because if I specify a different User-Agent the token still works.
This is what it looks like when it fails with verbose curl output.
Untitled
This is what it looks like when it works. I'm using the exact same token. The only difference between this one and the one above where I reproduced the error condition is the inclusion of the 
User-Agent
header that contains the default value used by python's urllib.request.Request as seen in the docs here: https://docs.python.org/3/library/urllib.request.html#urllib.request.Request When that User-Agent is used the result is an error.
Untitled
d
Thank you @Shaun Kruger, we'll take a look at this as soon as possible. Tagging in @Andrey Lyubavin for visibility
a
Hi @Shaun Kruger, could you please try again with the problematic user agent and let us know if it works?
s
Still no go
Copy code
< HTTP/2 403 
< date: Wed, 15 Apr 2026 17:55:14 GMT
< content-type: text/plain; charset=UTF-8
< content-length: 16
< 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
< referrer-policy: same-origin
< x-frame-options: SAMEORIGIN
< strict-transport-security: max-age=2592000; preload
< report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"<https://a.nel.cloudflare.com/report/v4?s=2a33IMZ6UDL0V%2FiO6pUNiIYGR4I5RoTRRN382md6v2bDbzM7e%2F3N8dzoEiST0qVtDYXir%2BJ7D0KVdyAzvIb8rz0n7jR3JUYYOqOaGMReYJKl2%2FdM1EE%2FIPTZTRlVIdu4R9AR>"}]}
< nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
< server: cloudflare
< cf-ray: 9eccd1f20c37b35f-SEA
< alt-svc: h3=":443"; ma=86400
< 
* Connection #0 to host <http://us.infisical.com|us.infisical.com> left intact
error code: 1010
a
@Shaun Kruger Please try again once more. We fixed the proxy for 
<http://app.infisical.com|app.infisical.com>
but I failed to notice you were using 
<http://us.infisical.com|us.infisical.com>
instead. Both domains are fixed now
s
It is working now
🙌 1
Open in Slack
PreviousNext
Powered by