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
Incorrect generation of server public key #58
Comments
AAA...AA= is a base64 encoding of an array only zero bytes. This is the server public key. You have that a bit confused. The client private key seems fine from the little piece in your screenshot. Seems like the server pub key got wrongly generated. |
@arctica where do I enter the server pub key? I only entered a private key by:
|
@mnil the public keys are generated from the private keys, you don't enter them anywhere. In terms of keys all you specify is the server's private key. How did you generate that one? |
@arctica I generated it by |
Hey @mnil sorry for the slow reply. I'm unable to reproduce this so far but I did identify some issues with how wg-access-server reports configuration problems that might have caused this. Could you give the new version 0.2.4 a go and let me know :) |
@Place1 I tested the latest image the other day with the same problem. I have since switched to using just wg and since you can't reproduce the problem I will close this issue. Keep up with the good project though! 🎉 |
The client key generates to AAA...AA= but after the QR code is gone, the public key is not AAA...AA=.
My docker-compose
The text was updated successfully, but these errors were encountered: