I screwed up my Trust

The startos server is up, the services are running, The backups backup over samba. All updated to 0.4.0-beta.7 with no warnings.

Stepping through the trust instructions

Downloaded Root CA :check_mark:

Ran sudo apt update :check_mark:

Installed pkk-kit :check_mark:

Moved to the download location :check_mark:

Add your Root CA to your OS trust store :bomb:

Here’s where I made a mistake. I copied that block of commands and changed the hostname, but to the wrong name. Instead of hopeless-eggnog, I put hopeless-eggnog.local.

So it failed and the output said 0 added. But when I corrected the hostname and tried again it and got an output 1 added, it still didn’t work. All I get is the Trust instructions when I go to hopeless-eggnog.local.

What can I try next?

Trusted another device, so the server is trustable. I just have to fix this device.

What browser are you using on the client that doesn’t recognize the certificate? There is a final step for Firefox and other browsers that is easy to miss.

Also Hard Refresh (and trying in new private browsing window) can help you get around caching issues.

Thanks Jesse!

The private window on brave did solve the endless loading animation I had when going to the local IP address. Still not getting past the trust instructions with the IP or the .local address.

The problem device is a debian machine running brave browser.
The firefox final step was also done.
Restarting the browser and the computer doesn’t fix it either.
Installing firefox browser… Nope, same results on firefox.

Oh wait, I completed the final firefox instruction again, this time in firefox, not thunderbird, and it works! Haloo Hallay Oh Frabjous Day!

Thank you Jesse!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.