com.mojang.authlib.exceptions.AuthenticationException: The client has sent too many requests within a certain amount of time
at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:79) ~[server.jar:git-Spigot-d21162c-61e0c69]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillGameProfile(YggdrasilMinecraftSessionService.java:180) [server.jar:git-Spigot-d21162c-61e0c69]
at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.fillProfileProperties(YggdrasilMinecraftSessionService.java:173) [server.jar:git-Spigot-d21162c-61e0c69]
at net.minecraft.server.v1_12_R1.TileEntitySkull$1.load(TileEntitySkull.java:76) [server.jar:git-Spigot-d21162c-61e0c69]
at net.minecraft.server.v1_12_R1.TileEntitySkull$1.load(TileEntitySkull.java:1) [server.jar:git-Spigot-d21162c-61e0c69]
at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3716) [server.jar:git-Spigot-d21162c-61e0c69]
at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2424) [server.jar:git-Spigot-d21162c-61e0c69]
at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2298) [server.jar:git-Spigot-d21162c-61e0c69]
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2211) [server.jar:git-Spigot-d21162c-61e0c69]
at com.google.common.cache.LocalCache.get(LocalCache.java:4154) [server.jar:git-Spigot-d21162c-61e0c69]
at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4158) [server.jar:git-Spigot-d21162c-61e0c69]
at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:5147) [server.jar:git-Spigot-d21162c-61e0c69]
at com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:5153) [server.jar:git-Spigot-d21162c-61e0c69]
at net.minecraft.server.v1_12_R1.TileEntitySkull$3.run(TileEntitySkull.java:201) [server.jar:git-Spigot-d21162c-61e0c69]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_141]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_141]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141]
[15:26:03 WARN]: Sun Sep 22 15:26:03 CEST 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
[15:26:03 WARN]: Sun Sep 22 15:26:03 CEST 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
[15:26:04 WARN]: Sun Sep 22 15:26:04 CEST 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
[15:26:04 WARN]: Sun Sep 22 15:26:04 CEST 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.