You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to authenticate or "list_vault" I am getting the below error. Direct copy below:
"request library compatibility issue, check that the your environment uses compatible versions: reqwest library: error sending request for url ()"}
Initially was getting this with "Client.authenticate", now getting this with Client.Vaults.list()
Unsure if this is coming from AWS & status page that shows 1Password website, but none for Service Acounts
Actual Behavior
client = await Client.authenticate(
auth=env_token,
# Set the following to your own integration name and version.
integration_name="",
integration_version="v1.0.0",
)
returned the above error
now "await account.vaults.list()" where account is the returned Client object.
File "...\Lib\site-packages\onepassword\core.py", line 41, in _invoke
raise_typed_exception(e)
File "...\Lib\site-packages\onepassword\errors.py", line 24, in raise_typed_exception
raise Exception(message)
Exception: request library compatibility issue, check that the your environment uses compatible versions: reqwest library: error sending request for url ()
Expected Behavior
Should be able to get listing of vaults accessible to this service account. (worked on Saturday)
Also, can you let us know whether it works now? I'd like to make sure we draw an action item to at least improve the error message, if this was indeed caused by the AWS outage from 2 weeks ago.
Activity
hculea commentedon Nov 5, 2025
Hi @jnickell, thanks for reporting this!
What Python version are you using?
hculea commentedon Nov 5, 2025
Also, can you let us know whether it works now? I'd like to make sure we draw an action item to at least improve the error message, if this was indeed caused by the AWS outage from 2 weeks ago.
jnickell commentedon Nov 5, 2025
I'm using 3.12.10 on Windows. It is working now, and at this point I would attribute it to the AWS outage. Apologize for not following up afterward.