How do I start afresh, completely afresh, with a new, virgin installation?

Help
1

How do I start afresh, completely afresh, with a new, virgin installation?

I have been unable to get atuin to work on my Arch Linux 6.19.14 system with a ZFS root filesystem. No matter what I do, I can’t log in. I am able to import my Fizsh history file, control-r brings up a list of CLI commands, and I can edit and run these commands. But when I try to log in and I’m given a URL to complete authenticating on the Atuin Hub, I am then unable to log in, no matter what I try. Using my Arch system loginname, various possible Atuin usernames, my email address, all end up with the same result: “Invalid credientials”.

The only forum topic that seems related to my issues is “Help:Cannot login to my account”. It was posted in July 2025 and no one has offered no solution. Unless there is an easy fix for “Invalid credentials”, I think I want to delete everything related to atuin and start afresh. Besides

pacman -R atuin atuin-server
rm -rf ~/.atuin
rm -rf ~/.config/atuin
rm -rf ~/.local/share/autin
rm -rf /etc/atuin

what do I need to do? In particular, what do I need to do to get the Atuin Hub to forget about me so I can restart from scratch? Of course, if there is an alternative that gets me a working Atuin Hub working login, I’m game for that.

Thanks.
— Vladimir

2

Could you try logging in on the hub again please?

You should be able to login with the same username/email/password as whatever you registered on the CLI.

We have a small migration step that is supposed to run automatically when a cli user logs in to the hub, but for some reason in your case this isn’t happening. I’ve triggered the migration manually.

In case you are having issuees with your password, you should be able to reset it.

3

Ellie,

Thank you for a quick response!

What you suggested allowed me to log into the Atuin Hub, but only by ignoring a “500 Oops” error. What the sequence of steps I actually followed is hazy because I didn’t expect to receive an error. (Sorry.)

I think what happened is that I issued atuin login from the CLI, got the Hub login screen, asked for a password reset via email and got the password reset email, reset my password, and that’s when I got the “500 Oops” error in my browser. I ignored the error and went back to the Hub login screen and logged in successfully.

To be clear, I’m all set, but you might want look into the “500 Oops” error (in your free time :wink:

Thanks again for fixing things and thanks for creating Atuin!