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
I executed idoitcli init and idoitcli configtest, which told me everything is OK.
I want to execute idoitcli cache to build the local cache.
Actual behavior
Now I'm trying idoicli cache, and I get
Create cache files needed for faster processing
Clear cache files
Fetch list of object types
No proper configuration for i-doit API calls: Connection to Web server failed [60]: SSL certificate problem: unable to get local issuer certificate
So, since I set curl.cainfo and openssl.capath in my php.ini (all of them, for apache2, cli, and fastcgi), and this does not help any, where does idoitcli expect the certificates? BTW, the only certificates involved are from an offical CA (Telekom), intermediate CA and server CA (both DFN e.V.), so the settings on OS level should suffice.
Steps to reproduce the behavior
See above, please.
Environment
Question
Answer
bheisig/idoitapi version
0.9
i-doit version
1.15.2 pro
i-doit API add-on version
? has been updated along by the software partner
Logs and other useful output
The output seems to be on client side only.
The text was updated successfully, but these errors were encountered:
Expected behavior
I executed
idoitcli init
andidoitcli configtest
, which told me everything is OK.I want to execute
idoitcli cache
to build the local cache.Actual behavior
Now I'm trying
idoicli cache
, and I getSo, since I set curl.cainfo and openssl.capath in my php.ini (all of them, for apache2, cli, and fastcgi), and this does not help any, where does idoitcli expect the certificates? BTW, the only certificates involved are from an offical CA (Telekom), intermediate CA and server CA (both DFN e.V.), so the settings on OS level should suffice.
Steps to reproduce the behavior
See above, please.
Environment
Logs and other useful output
The output seems to be on client side only.
The text was updated successfully, but these errors were encountered: