Client does not support authentication protocol requested by server. #1061
Comments
|
Please post your MySQL/MariaDB server version. I think MySQL 8 broke the compatibility with the MariaDB (forked version of MySQL) driver. |
|
Related #1015 |
|
@games647 Yeah I am running MySQL 8.0.33 version. Now I tried to use sqllite, but this error occured. |
This version is out of date. |
|
@games647 Sorry, my bad. Now I am using the latest, and on /premium command it says "sending request (bungeecord guide etc)". I am not running it as proxy.... I just installed fastloginbukkit ... |
|
Please post your EDIT: BTW Velocity is a Minecraft proxy. Therefore the setup guide has to be followed. |
|
So can't I run it only on a backend server? |
|
ok @games647 , I installed It also in velocity. Is it a problem if the velocity one and the bukkit one have 2 different databases? (both sqllite, because mysql is not supported). Now I ran /premium, it asks to retype the command to confirm but also it sends again "sending request... (bungeecord guide)." Is this normal? |
|
Btw thank you so much for the help |
Yes, but it needs to be installed on the proxy server so with Velocity or BungeeCord. The reason for that is that those instances are directly connected to the clients and are responsible for dealing with onlinemode authentication. This also the case if you aren't using FastLogin and enable the onlinemode normally.
The spigot database will no longer be used once it is in proxy setup. The spigot will only be responsible for auto plugin communication and provide an API for spigot plugins.
This means that were no response for the proxy version of the plugin. Either the proxy plugin disabled itself or its message got rejected. You are required follow the setup guide on the project page. These extra steps are required for verifying the origin between the plugin-to-plugin communication. So that no malicious user can fake these messages. |
I followed the guide. If I activate the premium mode it works... it also sends the other message but my settings are fine. Can I upload here the config? |
|
I think that message sending every /cracked or /premium is a correct behavior, he is waiting for proxy... I will cancel the message from message.yml and it's everything fine to my settings, true? |
|
If you get a following messages, yes. |
games647
changed the title
|
@games647 What's this error? It happens sometimes when I try to join. Now always. |
|
Please post the complete context. Please add more lines before it or post the complete log. |
|
[13:46:40 INFO] [fastlogin]: Incoming login request for Balda_ from / |
|
@games647 I removed My IP adress, you'll see only the "/" |
|
Then you need to confirm for me that the host:port combination is exactly the same during the first message and later messages. An unique session id built based on those numbers combined. |
If you mean the port after my ip:port yes it is the same |
|
well everytime I join into the server the port changes |
But both stays consisted during a login attempt? |
|
@games647 Well I remove 2 IP from the error message and they were the same |
|
Could you please post your plugin configuration. |
# FastLogin config
# Project site: https://www.spigotmc.org/resources/fastlogin.14153
# Source code: https://github.com/games647/FastLogin
#
# You can access the newest config here:
# https://github.com/games647/FastLogin/blob/main/core/src/main/resources/config.yml
# This a **very** simple anti bot protection. Recommendation is to use a dedicated program to approach this
# problem. Low level firewalls like uwf (or iptables direct) are more efficient than a Minecraft plugin. TCP reverse
# proxies could also be used and offload some work even to different host.
#
# The settings wil limit how many connections this plugin will handle. After hitting this limit. FastLogin will
# completely ignore incoming connections. Effectively there will be no database requests and network requests.
# Therefore, auto logins won't be possible.
anti-bot:
enabled: true
# Image the following like bucket. The following is total amount that is allowed in this bucket, while expire
# means how long it takes for every entry to expire.
# Total number of connections
connections: 600
# Amount of minutes after the first connection got inserted will expire and made available
expire: 10
# Action - Which action should be performed when the bucket is full (too many connections)
# Allowed values are: 'ignore' (FastLogin drops handling the player) or 'block' (block this incoming connection)
action: 'ignore'
# Request a premium login without forcing the player to type a command
#
# If you activate autoRegister, this plugin will check/do these points on login:
# 1. An existing cracked account shouldn't exist
# -> paid accounts cannot steal the existing account of cracked players
# - (Already registered players could still use the /premium command to activate premium checks)
# 2. Automatically registers an account with a strong random generated password
# -> cracked player cannot register an account for the premium player and so cannot the steal the account
#
# Furthermore the premium player check have to be made based on the player name
# This means if a cracked player connects to the server, we request a paid account login from this player
# the player just disconnect and sees the message: 'bad login' or 'invalid session'
# There is no way to change this message
# For more information: https://github.com/games647/FastLogin#why-do-players-have-to-invoke-a-command
autoRegister: false
# Should FastLogin respect per IP limit of registrations (e.g. in AuthMe)
# Because most auth plugins do their stuff async - FastLogin will still think the player was registered
# To work best - you also need to enable auto-register-unknown
#
# If set to true - FastLogin will always attempt to register the player, even if the limit is exceeded
# It is up to the auth plugin to handle the excessive registration
# https://github.com/games647/FastLogin/issues/458
respectIpLimit: false
# This is extra configuration option to the feature above. If we request a premium authentication from a player who
# isn't actual premium but used a premium username, the player will disconnect with the reason "invalid session" or
# "bad login".
#
# If you activate this, we are remembering this player and do not force another premium authentication if the player
# tries to join again, so the player could join as cracked player.
secondAttemptCracked: false
# New cracked players will be kicked from server. Good if you want switch from offline-mode to online-mode without
# losing players!
#
# Existing cracked and premium players could still join your server. Moreover, you could add player names to an
# allow-list.
# So that these cracked players could join too, although they are new players.
switchMode: false
# If this plugin detected that a player has a premium, it can also set the associated
# uuid from that account. So if the player changes the username, they will still have
# the same player data (inventory, permissions, ...)
#
# Warning: This also means that the UUID will be different if the player is connecting
# through an offline mode connection. This **could** cause plugin compatibility issues.
#
# This is an example and doesn't apply for every plugin.
# Example: If you want to ban players who aren't online at the moment, the ban plugin will look
# after an offline uuid associated to the player, because the server is in offline mode. Then the premium
# players could still join the server, because they have different UUID.
#
# Moreover, you may want to convert the offline UUID to a premium UUID. This will ensure that the player
# will have the same inventory, permissions, ... if they switched to premium authentication from offline/cracked
# authentication.
#
# This feature requires Cauldron, Spigot or a fork of Spigot (Paper)
premiumUuid: false
# This will make an additional check (only for player names which are not in the database) against the mojang servers
# in order to get the premium UUID. If that premium UUID is in the database, we can assume on successful login that the
# player changed its username and then update the name in the database.
# Examples:
# #### Case 1
# autoRegister = false
# nameChangeCheck = false
#
# GameProfile logins as cracked until the player invoked the command /premium. Then we could override the existing
# database record.
#
# #### Case 2
# autoRegister = false
# nameChangeCheck = true
#
# Connect the Mojang API and check what UUID the player has (UUID exists => Paid Minecraft account). If that UUID is in
# the database it's an **existing player** and FastLogin can **assume** the player is premium and changed the username.
# If it's not in the database, it's a new player and **could be a cracked player**. So we just use an offline mode
# authentication for this player.
#
# **Limitation**: Cracked players who use the new username of a paid account cannot join the server if the database
# contains the old name. (Example: The owner of the paid account no longer plays on the server, but changed the username
# in the meanwhile).
#
# #### Case 3
# autoRegister = true
# nameChangeCheck = false
#
# We will always request a premium authentication if the username is unknown to us, but is in use by a paid Minecraft
# account. This means it's kind of a more aggressive check like nameChangeCheck = true and autoRegister = false, because
# it requests a premium authentication which are completely new to us, that even the premium UUID is not in our database.
#
# **Limitation**: see below
#
# #### Case 4
# autoRegister = true
# nameChangeCheck = true
#
# Based on autoRegister it checks if the player name is premium and login using a premium authentication. After that
# fastlogin receives the premium UUID and can update the database record.
#
# **Limitation from autoRegister**: New offline players who use the username of an existing Minecraft cannot join the
# server.
nameChangeCheck: false
# If your players have a premium account and a skin associated to their account, this plugin
# can download the data and set it to the online player.
#
# Keep in mind that this will only work if the player:
# * is the owner of the premium account
# * the server connection is established through a premium connection (paid account authentication)
# * has a skin
#
# This means this plugin doesn't need to create a new connection to the Mojang servers, because
# the skin data is included in the Auth-Verification-Response sent by Mojang. If you want to use for other
# players like cracked player, you have to use other plugins.
#
# If you use PaperSpigot - FastLogin will always try to set the skin, even if forwardSkin is set to false
# It is needed to allow premium name change to work correctly
# https://github.com/games647/FastLogin/issues/457
#
# If you want to use skins for your cracked player, you need an additional plugin like
# ChangeSkin, SkinRestorer, ...
forwardSkin: true
# Displays a warning message that this message SHOULD only be invoked by
# users who actually are the owner of this account. So not by cracked players
#
# If they still want to invoke the command, they have to invoke /premium again
premium-warning: true
# ======[[ Spigot+ProtocolLib users only ]]======
# When set to true, enables the use of alternative session resolver which does not send the server IP
# to mojang session servers. This setting might be useful when you are trying to run the server via a
# transparent reverse proxy or some other form of DNAT. As far as security goes, this setting has
# negligible to no security impact.
#
# This setting works on a similar principle as 'prevent-proxy' setting in server.properties.
# When set to false, the server behaves like prevent-proxy was set to true and vice-versa.
# Normally, when you use the prevent-proxy=true, you would want this disabled.
#
# Please note that this setting has no effect when used outside of Spigot+ProtocolLib context.
#
# !!! [WARNING] !!!
# This option is considered highly experimental. While it is highly unlikely this will break your server,
# more tests need to be conducted in order to verify its effectiveness. Brief tests seemed promising, but
# every environment is different, and so it might not work for you as it did for me.
useProxyAgnosticResolver: false
# If you have autoRegister or nameChangeCheck enabled, you could be rate-limited by Mojang.
# The requests of the both options will be only made by FastLogin if the username is unknown to the server
# You are allowed to make 600 requests per 10-minutes (60 per minute)
# If you own a big server this value could be too low
# Once the limit is reached, new players are always logged in as cracked until the rate-limit is expired.
# (to the next ten minutes)
#
# The limit is IP-wide. If you have multiple IPv4-addresses you specify them here. FastLogin will then use it in
# rotating order --> 5 different IP-addresses 5 * 600 per 10 minutes
# If this list is empty only the default one will be used
#
# Lists are created like this:
#ip-addresses:
# - 192-168-0-2
ip-addresses: []
# How many requests should be established to the Mojang API for Name -> UUID requests. Some other plugins as well
# as the head Minecraft block make such requests as well. Using this option you can limit the amount requests this
# plugin should make.
#
# If you lower this value, other plugins could still make requests while FastLogin cannot.
# Mojang limits the amount of request to 600 per 10 minutes per IPv4-address.
mojang-request-limit: 600
# This option automatically registers players which are in the FastLogin database, but not in the auth plugin database.
# This can happen if you switch your auth plugin or cleared the database of the auth plugin.
# https://github.com/games647/FastLogin/issues/85
auto-register-unknown: false
# By setting this option to false, you can disable the auto login from fastlogin. So a premium (like a paid account)
# authentication is requested, but the player won't be auto logged into the account from the auth plugin.
#
# This can be used as 2Factor authentication for better security of your accounts. A hacker then needs both passwords.
# The password of your Minecraft and the password to login in with your auth plugin
autoLogin: true
# Floodgate configuration
# Connecting through Floodgate requires player's to sign in via their Xbox Live account
# !!!!!!!! WARNING: FLOODGATE SUPPORT IS AN EXPERIMENTAL FEATURE !!!!!!!!
# Enabling any of these settings might lead to people gaining unauthorized access to other's accounts!
# Automatically log in players connecting through Floodgate.
# Possible values:
# false: Disables auto login for every player connecting through Floodgate
# true: Enables auto login for every player connecting through Floodgate
# linked: Only Bedrock accounts that are linked to a Java account will be logged in automatically
# no-conflict: Bedrock players will only be automatically logged in if the Mojang API reports
# that there is no existing Premium Java MC account with their name.
# This option can be useful if you are not using 'username-prefix' in floodgate/config.yml
# Requires 'autoLogin' to be 'true'
# !!!!!!!! WARNING: FLOODGATE SUPPORT IS AN EXPERIMENTAL FEATURE !!!!!!!!
# Enabling this might lead to people gaining unauthorized access to other's accounts!
autoLoginFloodgate: false
# This enables Floodgate or Offline Geyser players to join the server, even if they are using the name of an
# existing Java **PREMIUM** account (so someone has bought Minecraft with that username)
#
# Java and Bedrock players will get different UUIDs, so their inventories, location, etc. will be different.
# However, some plugins (such as AuthMe) rely on names instead of UUIDs to identify a player which might cause issues.
# In the case of AuthMe (and other auth plugins), both the Java and the Bedrock player will have the same password.
#
# To prevent conflicts from two different players having the same name, it is highly recommended using a
# 'username-prefix' in floodgate/config.yml
#
# Possible values:
# false: Kick Bedrock players, if they are using an existing Premium Java account's name
# Note: Linked Floodgate players have the same name as their Java profile, so the Bedrock player will always conflict
# their own Java account's name. Therefore, setting this to false will prevent any linked player from joining.
# true: Bypass name conflict checking.
# linked: Floodgate accounts linked to a Java account will be allowed to join with conflicting names
# For Offline Geyser players, 'linked' works as 'false'
# !!!!!!!! WARNING: FLOODGATE/GEYSER SUPPORT IS AN EXPERIMENTAL FEATURE !!!!!!!!
# Enabling this might lead to people gaining unauthorized access to other's accounts!
allowFloodgateNameConflict: false
# Automatically register players connecting through Floodgate.
# autoLoginFloodgate must be available for the player to use this
# Possible values:
# false: Disables auto registering for every player connecting through Floodgate
# true: Enables auto registering for every player connecting through Floodgate
# linked: Only Bedrock accounts that are linked to a Java account will be registered automatically
# no-conflict: Bedrock players will only be automatically registered if the Mojang API reports
# that there is no existing Premium Java MC account with their name.
# This option can be useful if you are not using 'username-prefix' in floodgate/config.yml
# Requires 'autoRegister' to be 'true'
# !!!!!!!! WARNING: FLOODGATE SUPPORT IS AN EXPERIMENTAL FEATURE !!!!!!!!
# Enabling this might lead to people gaining unauthorized access to other's accounts!
autoRegisterFloodgate: false
# This option resembles the vanilla configuration option 'enforce-secure-profile' in the 'server.properties' file.
# It verifies if the incoming cryptographic key in the login request from the player is signed by Mojang. This key
# is necessary for servers where you or other in-game players want to verify that a chat message sent and signed by
# this player is not modified by any third-party. Modifications by your server would also invalidate the message.
#
# This feature is only relevant if you use the plugin in ProtocolLib mode and use 1.19+.
# This also the case if you don't have any proxies in use.
verifyClientKeys: false
# Database configuration
# Recommended is the use of MariaDB (a better version of MySQL)
# Single file SQLite database
driver: 'sqlite'
# File location
database: '{pluginDir}/FastLogin.db'
# MySQL/MariaDB
# If you want to enable it, uncomment only the lines below; this not this line.
# If on velocity use 'mariadb' as the driver
#driver: 'mariadb'
#host: 'localhost'
#port: 3306
#database: 'fastlogin'
#username: 'root'
#password: ''
# Advanced Connection Pool settings in seconds
#timeout: 30
#lifetime: 30
## It's recommended to enable SSL if the MySQL server isn't running on the same host
## This will encrypt the connection for secure transportation of the sql server password
#useSSL: false
## Verification requirements for the server cert,
## Values: Required (unchecked SSL connection), VerifyCA (verify CA), VerifyFull (verify CA and matching hostname)
#sslMode=Required
## TLS is preferred for this technique, then your host stored certificate store will be used to verify the server cert
## Similar to HTTPS. If that's not possible RSA can be used with the following options.
## This allows to request the public RSA key from the server to encrypt the data to it. True would allow machine-in-the-
## middle attacks.
#allowPublicKeyRetrieval=false
## Path to the RSA public key if key retrieval is forbidden
#ServerRSAPublicKeyFile=
# HTTP proxies for connecting to the Mojang servers in order to check if the username of a player is premium.
# This is a workaround to prevent rate-limiting by Mojang. These proxies will only be used once your server hit
# the rate-limit or the custom value above.
# Please make sure you use reliable proxies.
proxies:
# 'IP:Port' or 'Domain:Port'
# - 'xyz.com:1337'
# - 'test.com:5131' |
|
@games647 Sorry I couldn't upload the config,yml, anyway that's it |
What happened?
I am on velocity. I followed the guide and used 'mariadb' as the driver. (I am trying to connect to a mysql database.
on startup I have these errors.
[21:16:14] [Velocity Async Event Executor - #0/INFO] [fastlogin.hikari.HikariDataSource]: fastlogin - Starting...
[21:16:15] [Velocity Async Event Executor - #0/ERROR] [fastlogin.hikari.pool.HikariPool]: fastlogin - Exception during pool initialization.
java.sql.SQLException: Client does not support authentication protocol requested by server. plugin type was = 'mysql_native_password'
at fastlogin.mariadb.jdbc.plugin.authentication.AuthenticationPluginLoader.get(AuthenticationPluginLoader.java:48) ~[?:?]
at fastlogin.mariadb.jdbc.client.impl.ConnectionHelper.authenticationHandler(ConnectionHelper.java:272) ~[?:?]
at fastlogin.mariadb.jdbc.client.impl.StandardClient.(StandardClient.java:185) ~[?:?]
at fastlogin.mariadb.jdbc.Driver.connect(Driver.java:70) ~[?:?]
at fastlogin.mariadb.jdbc.Driver.connect(Driver.java:101) ~[?:?]
at fastlogin.mariadb.jdbc.Driver.connect(Driver.java:27) ~[?:?]
at fastlogin.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138) ~[?:?]
at fastlogin.hikari.pool.PoolBase.newConnection(PoolBase.java:364) ~[?:?]
at fastlogin.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:206) ~[?:?]
at fastlogin.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:476) ~[?:?]
at fastlogin.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561) ~[?:?]
at fastlogin.hikari.pool.HikariPool.(HikariPool.java:115) ~[?:?]
at fastlogin.hikari.HikariDataSource.(HikariDataSource.java:81) ~[?:?]
at com.github.games647.fastlogin.core.storage.SQLStorage.(SQLStorage.java:77) ~[?:?]
at com.github.games647.fastlogin.core.storage.MySQLStorage.(MySQLStorage.java:39) ~[?:?]
at com.github.games647.fastlogin.core.shared.FastLoginCore.setupDatabase(FastLoginCore.java:250) ~[?:?]
at com.github.games647.fastlogin.velocity.FastLoginVelocity.onProxyInitialization(FastLoginVelocity.java:94) ~[?:?]
at com.github.games647.fastlogin.velocity.Lmbda$1.execute(Unknown Source) ~[?:?]
at com.velocitypowered.proxy.event.UntargetedEventHandler$VoidHandler.lambda$buildHandler$0(UntargetedEventHandler.java:56) ~[velocity.jar:3.2.0-SNAPSHOT (git-37fedf50-b260)]
at com.velocitypowered.proxy.event.VelocityEventManager.fire(VelocityEventManager.java:597) ~[velocity.jar:3.2.0-SNAPSHOT (git-37fedf50-b260)]
at com.velocitypowered.proxy.event.VelocityEventManager.lambda$fire$5(VelocityEventManager.java:478) ~[velocity.jar:3.2.0-SNAPSHOT (git-37fedf50-b260)]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1589) [?:?]
[21:16:15] [Velocity Async Event Executor - #0/ERROR] [com.velocitypowered.proxy.event.VelocityEventManager]: Couldn't pass ProxyInitializeEvent to fastlogin
fastlogin.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: Client does not support authentication protocol requested by server. plugin type was = 'mysql_native_password'
at fastlogin.hikari.pool.HikariPool.throwPoolInitializationException(HikariPool.java:596) ~[?:?]
at fastlogin.hikari.pool.HikariPool.checkFailFast(HikariPool.java:582) ~[?:?]
at fastlogin.hikari.pool.HikariPool.(HikariPool.java:115) ~[?:?]
at fastlogin.hikari.HikariDataSource.(HikariDataSource.java:81) ~[?:?]
at com.github.games647.fastlogin.core.storage.SQLStorage.(SQLStorage.java:77) ~[?:?]
at com.github.games647.fastlogin.core.storage.MySQLStorage.(MySQLStorage.java:39) ~[?:?]
at com.github.games647.fastlogin.core.shared.FastLoginCore.setupDatabase(FastLoginCore.java:250) ~[?:?]
at com.github.games647.fastlogin.velocity.FastLoginVelocity.onProxyInitialization(FastLoginVelocity.java:94) ~[?:?]
at com.github.games647.fastlogin.velocity.Lmbda$1.execute(Unknown Source) ~[?:?]
at com.velocitypowered.proxy.event.UntargetedEventHandler$VoidHandler.lambda$buildHandler$0(UntargetedEventHandler.java:56) ~[velocity.jar:3.2.0-SNAPSHOT (git-37fedf50-b260)]
at com.velocitypowered.proxy.event.VelocityEventManager.fire(VelocityEventManager.java:597) ~[velocity.jar:3.2.0-SNAPSHOT (git-37fedf50-b260)]
at com.velocitypowered.proxy.event.VelocityEventManager.lambda$fire$5(VelocityEventManager.java:478) ~[velocity.jar:3.2.0-SNAPSHOT (git-37fedf50-b260)]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1589) [?:?]
Caused by: java.sql.SQLException: Client does not support authentication protocol requested by server. plugin type was = 'mysql_native_password'
at fastlogin.mariadb.jdbc.plugin.authentication.AuthenticationPluginLoader.get(AuthenticationPluginLoader.java:48) ~[?:?]
at fastlogin.mariadb.jdbc.client.impl.ConnectionHelper.authenticationHandler(ConnectionHelper.java:272) ~[?:?]
at fastlogin.mariadb.jdbc.client.impl.StandardClient.(StandardClient.java:185) ~[?:?]
at fastlogin.mariadb.jdbc.Driver.connect(Driver.java:70) ~[?:?]
at fastlogin.mariadb.jdbc.Driver.connect(Driver.java:101) ~[?:?]
at fastlogin.mariadb.jdbc.Driver.connect(Driver.java:27) ~[?:?]
at fastlogin.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138) ~[?:?]
at fastlogin.hikari.pool.PoolBase.newConnection(PoolBase.java:364) ~[?:?]
at fastlogin.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:206) ~[?:?]
at fastlogin.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:476) ~[?:?]
at fastlogin.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561) ~[?:?]
... 13 more
What did you expect?
No response
Steps to reproduce
Startup
Plugin list
Authme, authmevelocity
Configuration file
No response
Server log
No response
Plugin version
1.12--SNAPSHOT-1715c08
Platform
Velocity
Relevance
If there are, please vote them with a thumps reaction and not create new ones
The text was updated successfully, but these errors were encountered: