Login
You're viewing the mastodonapp.uk public feed.
  • Apr 12, 2026, 2:17 PM

    Last update to nextcloudpi version 1.57.0 destroyed my valid, not self-signed certificate (from letsencrypt) and now it is using this invalid certificate for all clients !
    I replaced the "snake-oil" certificate with the correct one in the apache2 settings but each client still complains about this certificate and needs an exception.
    Yes, I restarted apache2 and there is no visible problem on the server.
    Do I have to reboot the server in order to get the correct certificates into the clients ?
    Any hints ?
    #nextcloudpi #nextcloud #fedihelp

    💬 1🔄 0⭐ 0

Replies

  • Apr 12, 2026, 2:31 PM

    Yes, just restarting apache2 after changing the "snake-oil" configuration in apache2 to the letsencrypt certificate is not sufficient.
    You have to reboot the nextcloud server.
    I don't know where the server stores the certificate information and how to restart nextcloud and remove all "cache" entries.
    Feels like Windows NT 4.0😯

    💬 0🔄 0⭐ 0