-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V1.31 - Libsodium error #19
Comments
The problem is the mismatch somewhere on your install between 32-bit and 64-bit installation. I'm not sure where exactly, as it is your installation. I've had this problem years ago, I just tried compiling it on a fresh VPS running Ubuntu 18.04 without trouble. I used:
I'm sorry, you might have better luck recompiling it. |
Thanks for the reply!
Unfortunately, still the same error on register :( |
Well I'm dumbfounded, there was a way to solve this but I literally cannot remember. If you can wait, I can add an option to use a different type of password hashing. |
No hurry, I have the time! |
Hello, Can you check out v1.32 release? Delete your server.ini and then after its recreated, edit password.hashing.library from argon2 to bcrypt https://github.com/Quackster/Kepler/releases/tag/v1.32 Please don't change it back to argon2 in future, otherwise no one will be able to login. |
I downloaded the pre-build version, and I rebuild the source again myself, but both give the same issue:
Build using: |
My apologies, can you try and build from source again? Also remember what I said about server.ini I'll fix the compiled version soon. |
I cloned the master after your latest update and manage to compile it.
|
How are you running Kepler specifically? In a container? What distro?
|
I am running Kepler on my raspberry pi 4B+ I cloned the repo into my etc folder with: And run the command 'gradle fatJar' with the settings mentioned above. |
What's the output of |
The output of the output of
|
Try configuring a tmpfs in RAM and see if that changes things. Then execute |
I changed the settings according to @emansom his comment, and tested with the prebuild version 1.31 (because I could not build 1.32). Unfortunately, I still have the same error:
And an other question:
@Quackster, did you already manage to fix the compiled version of V1.32? |
The compiled version was fixed the same day as release. Anyways, as far as I'm concerned, there will have to be a special build for you to remove libsodium, but I am not going to do that. |
Add me on Discord my name is Quack#1337 and we can probably work something out. |
Thank you! I'll search for you on discord! |
When running the server from the precompiled jar in a Debian server, the following error occures on the server, when a users want to make a new account.
Also a manual install of libsodium does not solve the problem.
When a user wants to login, also an error will be raised:
The text was updated successfully, but these errors were encountered: