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
My Setup: NextcloudPi Installation on Debian - reachable via freedns-domain, Portforwarding on 443 and 80
My Problem: Passman Android App wouldn't connect to my Nextcloud instance due to "Network Error: Chain validation failed"
Everything else ist working fine, Chrome Extension or normal Access via Browser.
I Solved the problem following this instructions, but it might be only temporarily and will be overwritten when the new Certificates are generated.
nano /etc/apache2/sites-enabled/nextcloud.conf
then replaced
SSLEngine on
SSLProxyEngine on
SSLCertificateFile /etc/letsencrypt/live/mynextcloud.domain/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mynextcloud.domain/privkey.pem
with
SSLEngine on
SSLProxyEngine on
SSLCertificateFile /etc/letsencrypt/live/mynextcloud.domain/cert.pem
SSLCertificateChainFile /etc/letsencrypt/live/mynextcloud.domain/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mynextcloud.domain/privkey.pem
Maybe Passman is missing support for the Combined Certificates? Could this be added in a future Release, since this is the standard letsencrypt way of installation? This would be great!
I hope my fix helps other
The text was updated successfully, but these errors were encountered:
My Setup: NextcloudPi Installation on Debian - reachable via freedns-domain, Portforwarding on 443 and 80
My Problem: Passman Android App wouldn't connect to my Nextcloud instance due to "Network Error: Chain validation failed"
Everything else ist working fine, Chrome Extension or normal Access via Browser.
Lets Encrypt Certificates got automaically installed via NextcloudPi's Adminpanel Letsencrypt-App (Certbot?)
I Solved the problem following this instructions, but it might be only temporarily and will be overwritten when the new Certificates are generated.
nano /etc/apache2/sites-enabled/nextcloud.conf
then replaced
SSLEngine on
SSLProxyEngine on
SSLCertificateFile /etc/letsencrypt/live/mynextcloud.domain/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mynextcloud.domain/privkey.pem
with
SSLEngine on
SSLProxyEngine on
SSLCertificateFile /etc/letsencrypt/live/mynextcloud.domain/cert.pem
SSLCertificateChainFile /etc/letsencrypt/live/mynextcloud.domain/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mynextcloud.domain/privkey.pem
Maybe Passman is missing support for the Combined Certificates? Could this be added in a future Release, since this is the standard letsencrypt way of installation? This would be great!
I hope my fix helps other
The text was updated successfully, but these errors were encountered: