Hello! Thanks for looking into this for me, and the advice to create the new SSL certificate. I’ll look into how to do that. I have to admit that at this point I’m just wondering if I shouldn’t clean install TrueNAS to fix this. It might be easier, as I’m just starting out.

I really appreciate y’all looking into adding an option to wipe the encrypted fields.

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Thanks for the ticket. Unfortunately there isn’t much for us to do here because this isn’t a bug. In your situation, you would need to create a new SSL certificate and then attach that to the UI. However, we have opened up a related ticket to add a new feature to the UI that allows the user to wipe all encrypted fields in the database without wiping the entire config. Unfortunately, that would be a non-trivial change and will require careful design and consideration before we move forward. The ticket is linked to here if you’d like to follow progress of it. Otherwise, we’re closing this one for now.

@William Gryzbowski , yes, I figured out that was the problem pretty quickly.

I made the report because there’s nothing in the UI or the docs that I was able to find to figure out how to fix it. At the moment my install is partially broken and I can’t figure out what to do.

I know I can’t restore the original secret, but I’d at least like to be able to reinstall TrueNAS' default TLS certificate. I know I could use a self-signed CA and certificate from that, but (1) I don’t understand enough about certificates to understand how to do that; (2) that adds a level of complexity I think I should be able to avoid, as it should be possible to repair a damaged default TLS certificate.

That seems to be expected since you forgot to include secrets, no?