

If public key is denied forgejo is setup, but you have an old connection in your authorized_keys file probably form using gitea. Remove the line, it should prompt you to accept public key on next ssh session. This is a basic ssh functionality probably why you were downvoted I guess.
Gitea and forgejo configs were 100% same at some point, check forgejo news for when the last version that supported gitea migrations. That said it should still be pretty close.
My core one did fail once in the first week. I was on support chats for multiple all nighters like 12-15 breaks each. Finally someone said its probably bad parts and sent me a bunch of likely parts, I got preassembled so they guided me how to disassemble and replace the parts. Its been working ever sense, but it was killing me them going “well have you tried recalibrating?” And other basic tasks that they should have had notes on that were already done.