Лаунчер sashok724's Launcher v3 [OpenSource] [Support]

Ну не верно настроил провайдер аутентификации. Скидывай содержимое
LaunchServer.cfg

 

Названия у меня нормальные стоят в:
мой_ip
пользователь_MySQL
пароль_MySQL
база_данных
Там стоит всё как у меня

Спойлер: LaunchServer.cfg

address: "localhost";
bindAddress: "0.0.0.0";
port: 7240;

authHandler: "mysql";
authHandlerConfig: {
fetchAll: false; # Загрузить всю базу в кэш при запуске

address: "мой_ip"; # Адрес MySQL-сервера
port: 3306; # Порт MySQL-сервера (по умолчанию 3306)
username: "пользователь_MySQL"; # Имя пользователя MySQL-сервера
password: "пароль_MySQL"; # Пароль пользователя
database: "база_данных"; # База данных

table: "dle_users"; # Таблица
uuidColumn: "uuid"; # Поле с UUID пользователей
usernameColumn: "name"; # Поле с именами пользователей
accessTokenColumn: "accessToken"; # Поле с accessToken
serverIDColumn: "serverID"; # Поле с serverID
};

authProvider: "mysql"; # Название способа авторизации
authProviderConfig: {
address: "мой_ip"; # Адрес MySQL-сервера
port: 3306; # Порт MySQL-сервера (по умолчанию 3306)
username: "пользователь_MySQL"; # Имя пользователя MySQL-сервера
password: "пароль_MySQL"; # Пароль пользователя
database: "база_данных"; # База данных

query: "SELECT name FROM dle_users WHERE (email=? OR name=?) AND password=MD5(MD5(?)) LIMIT 1";
queryParams: [ "%login%", "%login%", "%password%" ];
};

# Texture provider
textureProvider: "request";
textureProviderConfig: {
skinsURL: "http://skins.minecraft.net/MinecraftSkins/%username%.png";
cloaksURL: "http://skins.minecraft.net/MinecraftCloaks/%username%.png";
};

# Launch4J EXE binary building
launch4J: false;

Спойлер: LaunchServer.log

2016.04.18 22:23:09 [ERROR] com.zaxxer.hikari.pool.PoolInitializationException: Exception during pool initialization

 

java -Xmx256M -Dlauncher.debug=true -jar LaunchServer.jar

Лог сюда кинь.

 

Вот как-то так:

Спойлер: log

sashok724's LaunchServer v15.2-NOT-SIGNED (build #5, 27.03.2016)
2016.04.18 23:32:51 [INFO] Setting up server script engine bindings
2016.04.18 23:32:51 [INFO] JLine2 terminal enabled
2016.04.18 23:32:51 [INFO] Reading RSA keypair
2016.04.18 23:32:51 [INFO] Modulus CRC32: 0xbe557a14
2016.04.18 23:32:51 [INFO] Reading LaunchServer config file
2016.04.18 23:32:51 [INFO] Syncing launcher binaries
2016.04.18 23:32:51 [INFO] Syncing launcher binary file
2016.04.18 23:32:52 [INFO] Syncing launcher EXE binary file
2016.04.18 23:32:52 [WARN] Missing launcher EXE binary file
2016.04.18 23:32:52 [INFO] Syncing updates dir
2016.04.18 23:32:52 [INFO] Syncing '1.6.4' update dir
2016.04.18 23:32:52 [INFO] Syncing 'HiTech' update dir
2016.04.18 23:32:52 [INFO] Syncing 'jre-8u66-win32' update dir
2016.04.18 23:32:54 [INFO] Syncing 'jre-8u66-win64' update dir
2016.04.18 23:32:55 [INFO] Syncing profiles dir
2016.04.18 23:32:55 [INFO] Syncing 'HiTech.cfg' profile
2016.04.18 23:32:55 [INFO] Starting server socket thread
2016.04.18 23:32:55 [DEBUG] LaunchServer started in 4205ms
2016.04.18 23:32:55 [INFO] Server socket thread successfully started
2016.04.18 23:33:11 [DEBUG] Connection #1 from 127.0.0.1
2016.04.18 23:33:11 [DEBUG] #1 Type: AUTH
2016.04.18 23:33:11 [DEBUG] #1 Login: 'WebFox', Password: '******'
2016.04.18 23:33:11 [INFO] HikariCP pooling enabled for 'authProviderPool'
2016.04.18 23:33:12 [ERROR] com.zaxxer.hikari.pool.PoolInitializationException: Exception during pool initialization
at com.zaxxer.hikari.pool.HikariPool.initializeConnections(HikariPool.java:580)
at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:150)
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:96)
at launchserver.auth.MySQLSourceConfig.getConnection(MySQLSourceConfig.java:109)
at launchserver.auth.provider.MySQLAuthProvider.auth(MySQLAuthProvider.java:34)
at launchserver.response.auth.AuthResponse.reply(AuthResponse.java:44)
at launchserver.response.ResponseThread.respond(ResponseThread.java:154)
at launchserver.response.ResponseThread.run(ResponseThread.java:61)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: null, message from server: "Host 'WIN-7H6IFU20G7C' is not allowed to connect to this MariaDB server"
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:937)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1037)
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2239)
at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2270)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2069)
at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:794)
at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:44)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:389)
at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:399)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:325)
at com.mysql.jdbc.jdbc2.optional.MysqlDataSource.getConnection(MysqlDataSource.java:422)
at com.mysql.jdbc.jdbc2.optional.MysqlDataSource.getConnection(MysqlDataSource.java:134)
at com.mysql.jdbc.jdbc2.optional.MysqlDataSource.getConnection(MysqlDataSource.java:105)
at com.zaxxer.hikari.pool.HikariPool.addConnection(HikariPool.java:495)
at com.zaxxer.hikari.pool.HikariPool.initializeConnections(HikariPool.java:564)
... 10 more

2016.04.18 23:33:12 [DEBUG] #1 Request error: Internal auth provider error

 

Не может подключиться к БД.

Caused by: java.sql.SQLException: null, message from server: "Host 'WIN-7H6IFU20G7C' is not allowed to connect to this MariaDB server"

Проверяй authProvider.

 

Если он утверждает что у него данные бд верны, то скорее всего что-то не так с конфигурацией базы данных.

 

Согласен. Он выбрал способ авторизации "mysql", а пытается приконтачить MariaDB. Это разные бд.

 

Да вот в том то и дело, там всё правильно указал.
Всё что зелёным отмечено, всё введено от моего VDS.

Спойлер: authProveder

authProvider: "mysql"; # Название способа авторизации
authProviderConfig: {
address: "Мой_IP"; # Адрес MySQL-сервера
port: 3306; # Порт MySQL-сервера (по умолчанию 3306)
username: "Пользователь_MySQL"; # Имя пользователя MySQL-сервера
password: "Пароль_пользователя_MySQL"; # Пароль пользователя
database: "dle_База_Данных"; # База данных

query: "SELECT name FROM dle_users WHERE (email=? OR name=?) AND password=MD5(MD5(?)) LIMIT 1";
queryParams: [ "%login%", "%login%", "%password%" ];
};

[DOUBLEPOST=1461009051,1461008989][/DOUBLEPOST]

А чем MariaDB отличается?
Это через программу XAMPP всё делаю. ( ласт версии )

 

MariaDB - это бд на основе mysql, но с рядом нововведений и улучшений. Утверждать не буду, но возможно в этом проблема.

 

MariaDB - это бд на основе mysql, но с рядом нововведений и улучшений. Утверждать не буду, но возможно в этом проблема.[/QUOTE]
Просто я читал тут сообщения не помню точно на какой странице.
Но у сашка вышло подключить к этой MariaDB.
Неужели с ней никто не сталкивался кроме 2-3 людей? Переходить на другую программу не вижу смысла, так как у меня на этой все сервера стоят. ( не майн )

 

Внешка на VDS открыта, на mysql? нука покажи файл /etc/mysql/my.cfg (возможно напутал с раширением, но поймешь какой брать, если что там паролей никаких нет).

 

Внешка закрыта на VDS. ( все файлы скачал для лаунчера сашка с другой ВДС, потом просто копирнул себе на ВДС )
И файла нету my.cfg
Есть только my.ini

 

Давай его, покажу где открыть внешку.

 

Спойлер: my.ini

# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't use much resources.
#
# You can copy this file to
# C:/xampp/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is C:/xampp/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
# password = your_password
port = 3306
socket = "C:/xampp/mysql/mysql.sock"


# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3306
socket = "C:/xampp/mysql/mysql.sock"
basedir = "C:/xampp/mysql"
tmpdir = "C:/xampp/tmp"
datadir = "C:/xampp/mysql/data"
pid_file = "mysql.pid"
# enable-named-pipe
key_buffer = 16M
max_allowed_packet = 1M
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
log_error = "mysql_error.log"

# Change here for bind listening
# bind-address="127.0.0.1"
# bind-address = ::1 # for ipv6

# Where do all the plugins live
plugin_dir = "C:/xampp/mysql/lib/plugin/"

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
# commented in by lampp security
#skip-networking
#skip-federated

# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin


# Point the following paths to different dedicated disks
#tmpdir = "C:/xampp/tmp"
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir = "C:/xampp/mysql/data"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "C:/xampp/mysql/data"
#innodb_log_arch_dir = "C:/xampp/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

## UTF 8 Settings
#init-connect=\'SET NAMES utf8\'
#collation_server=utf8_unicode_ci
#character_set_server=utf8
#skip-character-set-client-handshake
#character_sets-dir="C:/xampp/mysql/share/charsets"

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

 

Это не конфиг VDS, если у тебя VDS конечно не на винде.
По конфигу все ок, значит пользователь без внешки.

 

Как раз таки у меня Windows server 2008 стоит.
Думаю надо тыкать сашка и покупать тех поддержку, сил и нервов больше моих нет...

 

Он тут не причем уверен, дело в БД

 

Тогда надо проверить и Firewall тоже
-------------------------
Если подключения из внешки идут, проверь доступность порта mysql
вот например этим сервисом http://speed-tester.info/check_port.php (не реклама)[DOUBLEPOST=1461067618,1461067349][/DOUBLEPOST]Помогите с краш логом пожалуйста

Спойлер: crash-log

Код:

---- Minecraft Crash Report ----
// Quite honestly, I wouldn't worry myself about that.

Time: 4/19/16 4:37 PM
Description: Initializing game

java.lang.ExceptionInInitializerError
    at net.minecraft.client.network.OldServerPinger.func_147224_a(OldServerPinger.java:60)
    at cpw.mods.fml.client.FMLClientHandler.connectToServerAtStartup(FMLClientHandler.java:825)
    at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:558)
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:878)
    at net.minecraft.client.main.Main.main(SourceFile:148)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
    at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at launcher.client.ClientLauncher.launch(ClientLauncher.java:285)
    at launcher.client.ClientLauncher.main(ClientLauncher.java:186)
Caused by: java.lang.IllegalStateException: failed to create a child event loop
    at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:61)
    at io.netty.channel.MultithreadEventLoopGroup.<init>(MultithreadEventLoopGroup.java:49)
    at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:61)
    at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:52)
    at net.minecraft.network.NetworkManager.<clinit>(NetworkManager.java:51)
    ... 17 more
Caused by: io.netty.channel.ChannelException: failed to open a new selector
    at io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:128)
    at io.netty.channel.nio.NioEventLoop.<init>(NioEventLoop.java:120)
    at io.netty.channel.nio.NioEventLoopGroup.newChild(NioEventLoopGroup.java:87)
    at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:57)
    ... 21 more
Caused by: java.io.IOException: Unable to establish loopback connection
    at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:101)
    at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:68)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.nio.ch.PipeImpl.<init>(PipeImpl.java:170)
    at sun.nio.ch.SelectorProviderImpl.openPipe(SelectorProviderImpl.java:50)
    at java.nio.channels.Pipe.open(Pipe.java:155)
    at sun.nio.ch.WindowsSelectorImpl.<init>(WindowsSelectorImpl.java:127)
    at sun.nio.ch.WindowsSelectorProvider.openSelector(WindowsSelectorProvider.java:44)
    at io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:126)
    ... 24 more
Caused by: java.net.SocketException: Permission denied: connect
    at sun.nio.ch.Net.connect0(Native Method)
    at sun.nio.ch.Net.connect(Net.java:454)
    at sun.nio.ch.Net.connect(Net.java:446)
    at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
    at java.nio.channels.SocketChannel.open(SocketChannel.java:189)
    at sun.nio.ch.PipeImpl$Initializer$LoopbackConnector.run(PipeImpl.java:130)
    at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:83)
    ... 32 more


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
    at net.minecraft.client.network.OldServerPinger.func_147224_a(OldServerPinger.java:60)
    at cpw.mods.fml.client.FMLClientHandler.connectToServerAtStartup(FMLClientHandler.java:825)
    at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:558)

-- Initialization --
Details:
Stacktrace:
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:878)
    at net.minecraft.client.main.Main.main(SourceFile:148)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
    at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at launcher.client.ClientLauncher.launch(ClientLauncher.java:285)
    at launcher.client.ClientLauncher.main(ClientLauncher.java:186)

-- System Details --
Details:
    Minecraft Version: 1.7.10
    Operating System: Windows 7 (amd64) version 6.1
    Java Version: 1.8.0_66, Oracle Corporation
    Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation

Win 7 x64, антивирь и файрволл выключены

 

есть у когонибуть собраный клиент 1.8 для лаунчера

 

Помогите, все настроил правильно, лаунчсервер запускается без проблем.
Когда заходишь в лаунчер идет примерно 30 секунд обновление серверов а потом:
[DOUBLEPOST=1461130689,1461130655][/DOUBLEPOST]

http://launcher.sashok724.net/download/clients/[DOUBLEPOST=1461131247][/DOUBLEPOST]Новая ошибка :В, открыл порт 7240: