Question Mojang.Authlib.exceptions Issue

Cloudy

New member
Jun 27, 2022
2
0
1
Hellow Everybody.
After i changed my spigot servers to Paper. I've got a strange issue. some players can't connect to server and there is an error log per each player connection to server:
Code:
[13:39:26] [User Authenticator #16/WARN]: Couldn't look up profile properties for [email protected][id=e3e474b2-dddb-3cde-8662-921481ef3391,name=Cloudy,properties={},legacy=false]
com.mojang.authlib.exceptions.AuthenticationUnavailableException: Cannot contact authentication server
    at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:126) ~[authlib-3.3.39.jar:?]
    at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:100) ~[authlib-3.3.39.jar:?]
    at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillGameProfile(YggdrasilMinecraftSessionService.java:194) ~[authlib-3.3.39.jar:?]
    at com.destroystokyo.paper.profile.PaperMinecraftSessionService.fillGameProfile(PaperMinecraftSessionService.java:38) ~[paper-1.18.2.jar:git-Paper-386]
    at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillProfileProperties(YggdrasilMinecraftSessionService.java:187) ~[authlib-3.3.39.jar:?]
    at com.destroystokyo.paper.profile.PaperMinecraftSessionService.fillProfileProperties(PaperMinecraftSessionService.java:31) ~[paper-1.18.2.jar:git-Paper-386]
    at com.destroystokyo.paper.profile.CraftPlayerProfile.complete(CraftPlayerProfile.java:229) ~[paper-1.18.2.jar:git-Paper-386]
    at com.destroystokyo.paper.profile.CraftPlayerProfile.complete(CraftPlayerProfile.java:223) ~[paper-1.18.2.jar:git-Paper-386]
    at net.minecraft.server.network.ServerLoginPacketListenerImpl$LoginHandler.fireEvents(ServerLoginPacketListenerImpl.java:401) ~[?:?]
    at net.minecraft.server.network.ServerLoginPacketListenerImpl$1.run(ServerLoginPacketListenerImpl.java:282) ~[?:?]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
    at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.net.SocketTimeoutException: Connect timed out
    at sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:543) ~[?:?]
    at sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:594) ~[?:?]
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327) ~[?:?]
    at java.net.Socket.connect(Socket.java:633) ~[?:?]
    at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:299) ~[?:?]
    at sun.net.NetworkClient.doConnect(NetworkClient.java:178) ~[?:?]
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:498) ~[?:?]
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:603) ~[?:?]
    at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:264) ~[?:?]
    at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:378) ~[?:?]
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:189) ~[?:?]
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1287) ~[?:?]
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1128) ~[?:?]
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:175) ~[?:?]
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1665) ~[?:?]
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1589) ~[?:?]
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224) ~[?:?]
    at com.mojang.authlib.HttpAuthenticationService.performGetRequest(HttpAuthenticationService.java:140) ~[authlib-3.3.39.jar:?]
    at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:105) ~[authlib-3.3.39.jar:?]
    ... 12 more
[13:39:26] [User Authenticator #16/INFO]: UUID of player Cloudy is e3e474b2-dddb-3cde-8662-921481ef3391
[13:39:27] [Server thread/INFO]: Cloudy[/5.238.205.92:58025] logged in with entity id 200351 at ([world]191.49173800147122, 148.81385413537728, -336.51256005110395)
:D I lost players cause this on my new version server
 
Solution
Unfortunately, this does not have much to do with Paper at all and could not have been caused by migrating to it. When a player joins your server, the server must authenticate the player with Mojang to ensure they are playing with a valid Minecraft account. When Paper has tried to do this for this player in your log, the connection timed out. Paper could not talk to the Mojang authentication servers due to a networking issue. Paper uses the same code here as both vanilla and Spigot; there is nothing Paper has done that could be causing this.
Jan 28, 2022
43
1
7
8
Germany
crazycloudcraft.de
Hello,
i would like it, if you tell us more informations like what server version you use, instead of showing the server log with ipv4 adresses.

But i think that you forgot to delete/change things by changeing the software, also please take a look here:
 

sulu

Paper Triage
Staff member
Dec 14, 2021
23
3
4
3
Minnesota
Unfortunately, this does not have much to do with Paper at all and could not have been caused by migrating to it. When a player joins your server, the server must authenticate the player with Mojang to ensure they are playing with a valid Minecraft account. When Paper has tried to do this for this player in your log, the connection timed out. Paper could not talk to the Mojang authentication servers due to a networking issue. Paper uses the same code here as both vanilla and Spigot; there is nothing Paper has done that could be causing this.
 
Solution

Cloudy

New member
Jun 27, 2022
2
0
1
alright then do you know the server and ports we are using to connect Mojang servers? i should communicate the my server side to this...