Problem connecting to the server, only works locally

Question

Problem connecting to the server, only works locally

TheFiery opened this issue 8 months ago · 1 comments

TheFiery commented 8 months ago

What behaviour is observed?

With AuthMe, I can only log in locally. If I do this while I'm connected to the server via my public ip, I can't log in.

I have investigated this problem, but no solution solved the problem.
I don't host MYSQL

When I join locally it works very well 192.168.1.20
but I get this error in the console

[13:47:33 ERROR] [STDERR]: [Server thread] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection fr.xephi.authme.libs.com.mysql.cj.jdbc.ConnectionImpl@238ed46f (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[13:47:33 ERROR] [STDERR]: [Server thread] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection fr.xephi.authme.libs.com.mysql.cj.jdbc.ConnectionImpl@5af683a1 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[13:47:33 ERROR] [STDERR]: [Server thread] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection fr.xephi.authme.libs.com.mysql.cj.jdbc.ConnectionImpl@1df9bfa (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[13:47:33 ERROR] [STDERR]: [Server thread] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection fr.xephi.authme.libs.com.mysql.cj.jdbc.ConnectionImpl@4cd25f0a (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[13:47:33 ERROR] [STDERR]: [Server thread] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection fr.xephi.authme.libs.com.mysql.cj.jdbc.ConnectionImpl@192ac753 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[13:47:33 ERROR] [STDERR]: [Server thread] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection fr.xephi.authme.libs.com.mysql.cj.jdbc.ConnectionImpl@77afa45c (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[13:47:33 ERROR] [STDERR]: [Server thread] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection fr.xephi.authme.libs.com.mysql.cj.jdbc.ConnectionImpl@a52e118 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[13:47:33 ERROR] [STDERR]: [Server thread] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection fr.xephi.authme.libs.com.mysql.cj.jdbc.ConnectionImpl@5426d557 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.

then when I connect via my public ip, I can't log in even though I've entered the right password.

and in the console

[13:46:25 WARN] [AuthMe]: Plugin AuthMe v5.6.0-SNAPSHOT-b2623 generated an exception while executing task 20
java.lang.IllegalArgumentException: name cannot be null
        at com.google.common.base.Preconditions.checkArgument(Preconditions.java:145) ~[guava-31.1-jre.jar%23108!/:?]
        at org.bukkit.craftbukkit.v1_20_R1.CraftServer.getPlayerExact(CraftServerMixin.java:601) ~[arclight-1.20.1-1.0.5-1a8925b.jar%23163!/:arclight-1.20.1-1.0.5-1a8925b]
        at fr.xephi.authme.service.BukkitService.getPlayerExact(BukkitService.java:191) ~[?:?]
        at fr.xephi.authme.process.login.AsynchronousLogin.displayOtherAccounts(AsynchronousLogin.java:335) ~[?:?]
        at fr.xephi.authme.process.login.AsynchronousLogin.performLogin(AsynchronousLogin.java:291) ~[?:?]
        at fr.xephi.authme.process.login.AsynchronousLogin.login(AsynchronousLogin.java:105) ~[?:?]
        at fr.xephi.authme.process.Management.lambda$performLogin$0(Management.java:53) ~[?:?]
        at org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftTask.run(CraftTask.java:82) ~[arclight-1.20.1-1.0.5-1a8925b.jar%23163!/:arclight-1.20.1-1.0.5-1a8925b]
        at org.bukkit.craftbukkit.v1_20_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:54) ~[arclight-1.20.1-1.0.5-1a8925b.jar%23163!/:arclight-1.20.1-1.0.5-1a8925b]
        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:840) ~[?:?]

I tested with an earlier version but same problem
AuthMe 5.6.0-beta2 build n.2453

Expected behaviour

I expect to be able to reach my server via my public ip

To Reproduce

configure config.yml
launch the server
connect using its public ip

Plugin list

AuthMe
PlaceholderAPI
ProtocolLib

Server Implementation

Standalone server (no proxy)

Database Implementation

MySQL

AuthMe Version

AuthMeReloaded v5.6.0-SNAPSHOT (build: 2623)

Error log (if applicable)

https://paste.gg/fcc18d21261e4c28aaa15d72d246414f

Configuration

https://paste.gg/5c2331d4b7cb4ff1901ee68a299cf5b1

sgdc3 · Answer 1 · 2024-04-26T21:40:43.000Z

@TheFiery please try again with the latest dev build: https://ci.codemc.io/job/AuthMe/job/AuthMeReloaded/

Share to