[SOLVED] Agendav Error - Internal Server Error

Support
,
1

I just installed a fresh Yunohost instance and so far everything works perfectly except AgenDAV. I have it installed to a subdomain at / and whenever I launch it I just get a “Internal Server Error” and nothing else. No errors in any of the logs at all.

EDIT1: (found this in the agendav log)
myapp.CRITICAL: GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: self signed certificate in certificate chain (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) (uncaught exception) at /var/www/agendav/web/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 187 {“exception”:"[object] (GuzzleHttp\Exception\RequestException(code: 0): cURL error 60: SSL certificate problem: self signed certificate in certificate chain (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) at /var/www/agendav/web/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:187)"}

EDIT2: (According to the error page)
CURLE_SSL_CACERT (60)

Peer certificate cannot be authenticated with known CA certificates.

Any advice? I’m not sure how to resolve this. I do have a cert with Let’s Encrypt. Not the self-signed one.

Thank you,
J

2

Oui, tu semble avoir un souci de certificat.

Soit tu passe par là, soit tu utilise directement Let’s encrypt.

:slight_smile:

3

Suprisingly I was able to get agendav to work by modifying my hosts file on my server. But i have a different problem now. I cannot login. It just states access denied after clicking on app in dashboard.

Can anyone be so kind to explain to me the proper hosts file setup? It seems maybe agendav can’t find the sso or something? I’m not sure.

Thank you,
J

4

Well, I changed the Baikal auth from Digest to Basic and it made AgenDAV authenticate. BUT now my roundcube won’t connect to Baikal cardDAV anymore. I can access it directly using the link and authenticate but roundcube throws me a 504 Gateway Timeout when trying to add a contact.

Anyway I still think maybe my hosts file isn’t setup correctly… Idk…

Thanks again.

5

Ok, I ended up just disabling the preset from Baikal contact, and set it back up and its working again if anyone else has this problem.

Thanks.

1 Like