Skip to content
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

Multiplayer suddenly not working #227

Open
1 task done
xnnox70 opened this issue Aug 6, 2022 · 11 comments
Open
1 task done

Multiplayer suddenly not working #227

xnnox70 opened this issue Aug 6, 2022 · 11 comments
Labels
bug Something isn't working

Comments

@xnnox70
Copy link

xnnox70 commented Aug 6, 2022

Operating System

Windows 11

Description of bug

Tried joining on a server after days of not playing. I try to join, but there's an error "Invalid signature for public profile key" shows up, and tells me to restart the game. I tried logging off and on, reinstalling the client to no avail. I thought this wasn't the launcher's issue, however, this didn't happen on another launcher I used.

Steps to reproduce

• Run instance
• Multiplayer>>join server>>connect
• "Invalid signature for public profile key"

Suspected cause

No response

This issue is unique

  • I have searched the issue tracker and did not find an issue describing my bug.
@xnnox70 xnnox70 added the bug Something isn't working label Aug 6, 2022
@xnnox70 xnnox70 changed the title LAN suddenly not working Multiplayer suddenly not working Aug 6, 2022
@Cyimil
Copy link

Cyimil commented Aug 7, 2022

It seems that since 1.19.1 was launched, UltimMC started having this problem...

@MenacingPerson
Copy link

MenacingPerson commented Aug 7, 2022

From authlib injector notes:

This update contains breaking changes that require both server and client to use v1.2.0 and above of authlib-injector!

If you encounter the Invalid signature for profile public key. Try restarting your game. error when entering the server, please make sure that the authlib-injector version of the server and client is v1.2.0 or above.

If your server version is 1.19 or above, please modify server.properties and modify enforce-secure-profile to true!

     [Fix] Fixed a warning that chat messages were not signed in MC 1.19.1

Linked pull request: #172
Build number: 48

I think ultimmc devs have to fix

@jwaxy
Copy link

jwaxy commented Aug 8, 2022

I have the same error with Linux.

@jwaxy
Copy link

jwaxy commented Aug 10, 2022

I fixed the problem with using Wurst Client's nochatreports and noencryption modules.

@sedub01
Copy link

sedub01 commented Aug 10, 2022

Yeah, I have that problem too but people around me say there's no errors
Hope devs will fix this asap

@Ar7hurz1nh0
Copy link

I was having the same issue, so I jumped in and tried fixing it myself, even if it was a temporarily solution. I'm linking my pull request that solves it (#241)

@Neptune650
Copy link
Collaborator

I see and can understand this issue, the cause is that is likely the server you're trying to connect to doesn't have that option enabled, please ask the server manager to do so.

@Neptune650
Copy link
Collaborator

This happens because UltimMC always uses the latest version, but the server may not.

@Ar7hurz1nh0
Copy link

Ar7hurz1nh0 commented Sep 17, 2022

As a server owner, I have disabled enforce-secure-profile on server.properties, and force-key-authentication on velocity.toml. But it seems that velocity in specific has some kind of bug that doesn't allow connections even with it disabled. The
PR linked solves that problem.

@jwaxy
Copy link

jwaxy commented Sep 18, 2022

As a server owner, I have disabled enforce-secure-profile on server.properties, and force-key-authentication on velocity.toml. But it seems that velocity in specific has some kind of bug that doesn't allow connections even with it disabled. The PR linked solves that problem.

I tried to it with PaperMC on aternos. But nothing changed :/

@roridev
Copy link

roridev commented Dec 16, 2022

A workaround is having NoChatReports installed on the client or server.

cc @Ar7hurz1nh0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants