If you have received an email saying your server registration key has been leaked on GitHub and is now available for everyone to see. It means your registration key has been committed to a public GitHub repository by either you or someone you shared it with.
Server registration keys are meant to be private, only for the account owner to see. To regenerate your registration key, follow these steps, or read our dedicated article.
-
Go to the Servers page on Portal.
-
Inside the list of your server registration keys, click on the Server ID of the key you wish to regenerate.
-
A modal will open, displaying details about your server key.
-
Click on the Regenerate button.
- A confirmation modal opens, click Yes.
Once regenerated, your server registration key is no longer at risk. 🙂
You will now need to replace the key on your server’s config file. Additionally, make sure to not commit your server registration key in a public git repository.