-
Notifications
You must be signed in to change notification settings - Fork 120
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
Handshake failure: invalid key for user #404
Comments
Try deleting your |
I'm having this same problem with the same OS. I deleted the files, but it didn't fix it. |
@Linventor please upload your KSP.log file to pastebin.com and link it here |
@Linventor try using a different user name. |
... would it be possible to switch back to my current username later? |
Only if you contact the server administrator and ask him to delete your By the way, what username are you trying to use? Someone might have connected with your username, thus the server saved the person's public key instead of yours. |
oh, okay. thanks! |
@Linventor This is all due to attempting to sign in to a server with the same name using a different PC or new KSP install. Steps to bypass this from @RockyTV
OR
@godarklight you could close this as "non-issue" unless you plan to have different auth one day 🦄 |
Um... it's a "bit" late to be replying to this, considering I'd completely
forgotten about the problem. Hey, it's been almost 4 months.
…On Fri, Nov 17, 2017 at 12:34 PM, Logan Schmidt ***@***.***> wrote:
@Linventor <https://github.com/linventor> This is all due to attempting
to sign in to a server with the same name using a different PC or new KSP
install.
Steps to bypass this from @RockyTV <https://github.com/rockytv>
- Use a different username for the new connection
*OR*
- Contact the server administrator and ask him to delete your .txt
file in /Universe/Players
@godarklight <https://github.com/godarklight> you could close this as
"non-issue" unless you plan to have different auth one day 🦄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#404 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT4Etfy5nRr73t3Q5vYFCz_Fo49CQienks5s3cPAgaJpZM4MJZd7>
.
--
-Liam
|
@Linventor Sorry for the confusion It's never "too late" when it comes to open GitHub Issues. Keep in mind when opening issues until they are marked closed, the public is usually going to openly discuss the issue! If you need to unsubscribe from notifications you can do so here: https://github.com/settings/notifications My comment is just for others seeking information on the issue, as well as asking for resolve and ultimately the closure of this open issue. ⛱ |
fair enough.
…On Fri, Nov 17, 2017 at 1:02 PM, Logan Schmidt ***@***.***> wrote:
@Linventor <https://github.com/linventor> Sorry for the confusion It's
never "too late" when it comes to open GitHub Issues. Keep in mind when
opening issues until they are marked closed, the public is usually going to
openly discuss the issue! If you need to unsubscribe from notifications you
can do so here: https://github.com/settings/notifications
My comment is just for others seeking information on the issue, as well as
asking for resolve and ultimately the closure of this open issue.
⛱
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#404 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT4EtQSEI7RUN3LD8lx_eDQcpvXyeJ_5ks5s3covgaJpZM4MJZd7>
.
--
-Liam
|
Thanks for understanding! @Linventor
On 11/17/2017 11:54:20 AM, Linventor <notifications@github.com> wrote:
fair enough.
…On Fri, Nov 17, 2017 at 1:02 PM, Logan Schmidt ***@***.***> wrote:
@Linventor <https://github.com/linventor> Sorry for the confusion It's
never "too late" when it comes to open GitHub Issues. Keep in mind when
opening issues until they are marked closed, the public is usually going to
openly discuss the issue! If you need to unsubscribe from notifications you
can do so here: https://github.com/settings/notifications
My comment is just for others seeking information on the issue, as well as
asking for resolve and ultimately the closure of this open issue.
⛱
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#404 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT4EtQSEI7RUN3LD8lx_eDQcpvXyeJ_5ks5s3covgaJpZM4MJZd7>
.
--
-Liam
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [#404 (comment)], or mute the thread [https://github.com/notifications/unsubscribe-auth/ACPXDvbgNLfesmGQjq2fSbCO_ePlNtjgks5s3dZZgaJpZM4MJZd7].
|
you're welcome.
On Fri, Nov 17, 2017 at 1:59 PM, Logan Schmidt <notifications@github.com>
wrote:
… Thanks for understanding! @Linventor
On 11/17/2017 11:54:20 AM, Linventor ***@***.***> wrote:
fair enough.
On Fri, Nov 17, 2017 at 1:02 PM, Logan Schmidt ***@***.***>
wrote:
> @Linventor <https://github.com/linventor> Sorry for the confusion It's
> never "too late" when it comes to open GitHub Issues. Keep in mind when
> opening issues until they are marked closed, the public is usually going
to
> openly discuss the issue! If you need to unsubscribe from notifications
you
> can do so here: https://github.com/settings/notifications
>
> My comment is just for others seeking information on the issue, as well
as
> asking for resolve and ultimately the closure of this open issue.
>
> ⛱
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#404 (comment)-
345317878>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AT4EtQSEI7RUN3LD8lx_
eDQcpvXyeJ_5ks5s3covgaJpZM4MJZd7>
> .
>
--
-Liam
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [https://github.com/
godarklight/DarkMultiPlayer#404#issuecomment-345332130], or mute
the thread [https://github.com/notifications/unsubscribe-
auth/ACPXDvbgNLfesmGQjq2fSbCO_ePlNtjgks5s3dZZgaJpZM4MJZd7].
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#404 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT4Etb-sQPCYkhI_jVyUgah2l2DYRkP0ks5s3deegaJpZM4MJZd7>
.
--
-Liam
|
Environment
Description
I am trying to load a server and I even asked for them to delete the playername.txt file and they did and I still cant connect. Pls help
The text was updated successfully, but these errors were encountered: