johnbrasil Postado Dezembro 21, 2018 Denunciar Compartilhar Postado Dezembro 21, 2018 Boa tarde Senhores. Instalei o Multicraft no meu Dedicado e o WHMCS para realizar a conexão automática tbm. Mas na parte quando eu vou em Criar database, deu este erro, e estou tentando corrigir, mas está difícil. Sou bem leigo nesta parte, mas está complicado. Alguem poderia me auxiliar, por gentileza? Obrigado. Link para o comentário Compartilhar em outros sites More sharing options...
craftMC Postado Dezembro 21, 2018 Denunciar Compartilhar Postado Dezembro 21, 2018 qual e versao teu mysql? Link para o comentário Compartilhar em outros sites More sharing options...
johnbrasil Postado Dezembro 21, 2018 Autor Denunciar Compartilhar Postado Dezembro 21, 2018 A versão é a 5.0.12 do Php é 7.0 Link para o comentário Compartilhar em outros sites More sharing options...
craftMC Postado Dezembro 21, 2018 Denunciar Compartilhar Postado Dezembro 21, 2018 tem instalado o php_mysql e mysql_connect? Link para o comentário Compartilhar em outros sites More sharing options...
johnbrasil Postado Dezembro 21, 2018 Autor Denunciar Compartilhar Postado Dezembro 21, 2018 1 minuto atrás, BlackEnergyPT disse: tem instalado o php_mysql e mysql_connect? Então Black... Eu tenho tudo instalado sim, eu crio o servidor normalmente pelo WHMCS, e ele é ativado automaticamente, tudo certinho, cria o usuário de ftp, cria tudo, está tudo certo nesta parte. O único errado é para criar a DB na área do multicraft mesmo. Mas sim, possuo ambos! Link para o comentário Compartilhar em outros sites More sharing options...
craftMC Postado Dezembro 21, 2018 Denunciar Compartilhar Postado Dezembro 21, 2018 usas discord? eu posso tentar ajudar a ti Link para o comentário Compartilhar em outros sites More sharing options...
johnbrasil Postado Dezembro 22, 2018 Autor Denunciar Compartilhar Postado Dezembro 22, 2018 Senhores, boa tarde. o problema do FTP foi solucionado com êxito. Uma problema do qual está acontecendo comigo agora, é que todo servidor quando criado, ele vem setado como "0.0.0.0:porta" . Todos os servidores que eu crio no WHMCS, ele sempre vem com esta configuração, sempre com o IP 0.0.0.0.... Como que eu mudo esta configuração para vir com o IP normal, para que os players NATURALMENTE possam saber qual o IP para se conectarem? Segue minha configuração: Citar [multicraft] ## The daemon will run under this user (not used for Windows) user = minecraft ## Directories created by Multicraft will have the owner set to ## the user and the group set to the webUser (not used for Windows) ## default: same as "user" webUser = ## The daemon will listen on the following IP/port. ## 0.0.0.0 to listen on all available interfaces (all IPs). Note that ## you will have to use the "externalIp" setting below if you set this ## to 0.0.0.0 as the control panel needs to know where to connect. ip = 0.0.0.0 port = 25465 ## If the external address is different from the listen address ## you can set the external address here. This setting will be saved ## to the DB and used by the control panel to connect to the daemon. ## default: same as "ip" externalIp = 0.0.0.0 ## The connection password for daemon communication ## !! Change this when you set Multicraft to listen on a public IP !! ## The same password will have to be used on the panel side in the file: ## protected/config/config.php password = MINHASENHAQUI ## Remote IP restrictions for daemon connections. This is a comma separated ## list of IPs that are allowed to connect to this daemon. Empty for all ## remote IPs allowed. ## default: empty allowedIps = ## The maximum number of daemon connections to allow to this daemon. ## default: 500 #maxConnections = 500 ## The maximum number of daemon connections a single client can open. ## default: 50 #maxClientConnections = 50 ## The daemon ID, only the Dynamic license supports this setting. ## Running multiple servers with the same IDs can cause unpredictable behavior ## Valid values: 1, 2, ..., 65535 id = 1 ## The database containing daemon ## default: sqlite:data.db (-> "baseDir"/"dataDir"/data.db) database = mysql:host=127.0.0.1;dbname=multicraft_daemon ## Example for MySQL connections: database = mysql:host=127.0.0.1;dbname=multicraft_daemon dbUser = MEUUSUARIOAQUI dbPassword = MINHASENHAQUI #dbCharset = utf8 ## A name for this daemon, this is optional ## default: Multicraft Daemon name = Servidor Multicraft 1 ## The amount of memory available to this daemon in MB. This setting mainly ## serves informational purpose for display in the control panel and ## for the API to decide if this daemon can still run more servers. ## 0 means undefined ## default: 0 #totalMemory = ## The base directory of the multicraft install. Relative to the users ## home directory or absolute. Must exist. ## default: multicraft (-> /home/"user"/multicraft) baseDir = /home/minecraft/multicraft ## The directory the daemon binaries reside in ## default: bin (-> "baseDir"/bin) daemonDir = bin ## The data directory. Contains the database, socket, log and ## must be accessible by the control panel user if using a SQLite DB ## default: data (-> "baseDir"/data) dataDir = data ## The directory jar files can be placed in ## default: jar (-> "baseDir"/jar) jarDir = jar ## The directory containing all the servers. Users can be given access ## to specific subdirectories containing their server data ## default: servers (-> "baseDir"/servers) serversDir = servers ## The directory containing server templates ## default: templates (-> "baseDir"/templates) templatesDir = templates ## The following files contain daemon specific data. ## The paths specified are relative to "baseDir" pidFile = multicraft.pid logFile = multicraft.log licenseFile = multicraft.key scriptsFile = scripts.conf ## This file defines the config file to use depending on the executable name configsFile = server_configs.conf ## This config file contains the default server configuration. It is not ## in the "jar" directory so it does not get listed as a selection in the ## JAR File dropdown. defaultConfigFile = default_server.conf ## Note that for all of the above settings where a file or directory is ## indicated you can also use absolute paths (/dir), home-relative ## paths (~/dir) or relative paths (./dir or ../dir). "dir" stands for ## the setting you're editing. ## When not using absolute/relative paths the setting is taken to be ## relative to the home directory of the user configured by the "user" ## setting. ## Examples: ## - Changing "baseDir" to ./multicraft will cause multicraft to search ## all the files in a subdirectory "multicraft" of the directory it's ## called from ## - Changing "logFile" to ~/multicraft.log will cause Multicraft to log ## everything to the file multicraft.log in the home directory of the ## user configured by the "user" setting ## The maximum size of one logfile after which the log will be rotated ## default: 20971520 (20 MB) logSize = 20971520 ## The number of log files to keep (multicraft.log.1 ... multicraft.log.X) ## default: 9 logCount = 9 ## Synchronize log writes. Disabling this will improve performance at the ## risk of having some log entries overlap. ## default: true #logSync = false ## Use thesyslog facility instead of logging to a file. ## default: false #logSyslog = true ## The syslog facility to log to. Possible values: auth, cron, daemon, ## kern, lpr, mail, news, security, syslog, user, uucp, local10-17 ## default: daemon #logFacility = daemon ## Log all commands the daemon receives from the panel ## default: false #logCommands = false ## Log server console output to the log file under these conditions: ## - always Always log server console output ## - startup Only log server console output during server startup ## - running Only log server console output after server startup ## - never Never log server console output ## default: startup #logServerConsole = startup ## Delay between server auto-starts in milliseconds. ## default: 750 autostartDelay = 750 ## Automatically update server binaries, conf files or both on daemon ## startup. Valid values: ## - empty Don't update anything on startup ## - base Update the server binaries and conf files for the base server ## types that come with Multicraft. Currently: ## minecraft_server.jar.conf, minecraft_optimized.jar.conf, ## craftbukkit.jar.conf, spigot.jar.conf ## - initial Same as "base" but only update if the jar files don't exist ## - binary Update all server binaries on daemon startup ## - conf Update all server conf files on daemon startup ## - both Update all server binaries and conf files on daemon startup ## default: empty startupServerUpdate = initial ## A list of section names in .conf files that can safely be defined ## or overridden by users. Note that this is just a default value that ## can itself be overridden in the .conf files in the daemon directory. ## Use * to allow all sections or a regular expression matching allowed ## sections only. ## default: ^(encoding|commands|parse_.+)$ #safeConfSections = ^(encoding|commands|parse_.+)$ ## Allow symlinks where directories are expected. This check is done for ## security. ## default: false #allowSymlinks = false ## Skip the integrity check for directories. This check is done for ## security, it verifies that a directory entry is consistent with its ## filesystem entry. You can disable this if this check causes issues ## on your particular filesystem. ## default: true #skipIntegrityCheck = false ## The timeout for template setup operations in seconds ## default: 600 #templateSetupTimeout = 600 ## Disables the template functionality. Please use the setting in the panel to ## disable it there. ## default: false #templatesDisabled = false ## Advanced: Use TCP keepalive for daemon connections ## default: true #tcpKeepAlive = true ## Advanced: Use TCP keepalive for FTP connections ## default: true #ftpTcpKeepAlive = true ## TCP keepalive parameters, use 0 for system default ## default: 0 tcpKeepAliveIdle = 60 tcpKeepAliveInterval = 5 tcpKeepAliveCount = 6 ## Advanced: Set global timeout for TCP connections in seconds, 0 for no ## timeout ## default: 120 tcpTimeout = 120 ## Advanced: Prefer IPv4 for version check requests. ## Can speed up hostname lookup. ## default: true #preferIPv4 = true ## Whether to delete the server directory on the old daemon after a server ## move. This is disabled by default for safety. ## default: false #deleteAfterMove = false ## Only allow a single script to be run at a time for each server. If disabled ## there is no limit on the number of scripts that can be running at the same ## time. ## default: false singleScriptPerServer = true ## The timeout for server executable and config file downloads in seconds. ## default: 15 #downloadTimeout = 15 ## The User-Agent string to use for server executable and config file downloads #downloadUserAgent = Your Custom User-Agent ## The User-Agent string to use for plugin downloads #downloadUserAgentPlugins = Your Custom User-Agent ## Whether or not to add version/architecture/OS parameters when downloading ## config files ## default: true #downloadAddVersionInfo = true ## When enabled the remote host will be verified when using HTTPS, otherwise ## the host and certificate checks are skipped. ## default: false #secureDownloads = false ## The CA certificate bundle to use for verifying secure downloads. If set to ## "auto" the daemon will try a set of default paths. ## default: auto #caBundle = /etc/ssl/certs/ca-certificates.crt [useragent] ## The path to the Multicraft useragent. This program is used in ## multiuser mode to access user files. ## default: bin (-> "baseDir"/bin, same as daemonDir) #userAgentDir = bin ## The executable of the Multicraft useragent. Note that a config ## file with the same name as this setting (plus .conf) will be ## generated next to this file. ## default: launcher (-> "baseDir"/"userAgentDir"/useragent) #userAgentFile = useragent ## The minimum allowed user and group IDs for server users ## default: 100 #userAgentMinUid = 100 #userAgentMinGid = 100 ## The script to run when a server is being prepared. The path is ## relative to the userAgentDir. ## NOTE: This script will be run as the superuser. ## default: empty #userAgentSuperuserPrepare = ## The script to run when a server is being prepared. The path is ## relative to the baseDir. ## default: empty #userAgentPrepare = ## Various useragent configuration options #userAgentCp = /bin/cp #userAgentCpOpts = --preserve=mode,timestamps -- #userAgentDirCpOpts = -r --preserve=mode,timestamps -- #userAgentUnzip = /usr/bin/unzip #userAgentUnzipOpts = -qql #userAgentUnzipRe = ^(?:\s+[^\s]+){3}\s+(.*)$ [launcher] ## The path to the Multicraft launcher. This launcher program enables ## Multicraft to run servers that need a console to run correctly. ## default: launcher (-> "baseDir"/launcher) #launcherDir = launcher ## The executable of the Multicraft launcher ## default: launcher (-> "baseDir"/"launcherDir"/launcher) #launcherFile = launcher ## Integrated FTP server settings [ftp] ## Wheter or not to enable the integrated FTP server, true/false ## default: true enabled = true ## IP to listen on for FTP connections, uncomment to use the same as ## for the daemon. ## 0.0.0.0 means listening on all available interfaces (all IPs) ## default: same as the "ip" setting for the daemon, see above ftpIp = 0.0.0.0 ## See the descriptions of "externalIp" and "ip" for the daemon above ## default: same as "externalIp" if "ftpIp" is "0.0.0.0" otherwise "ftpIp" ftpExternalIp = MEUHOSTAQUI ## Masquerade IP address to use for passive FTP connections when ## Multicraft is running behind a router. ## default: empty #ftpNatIp = ## A port range to use for passive data transfers. If this is not ## specified the FTP server will use random ports. ## Format: 4000-8000 ## default: empty #ftpPasvPorts = ## Port to listen on for incoming FTP connections. Change this to ## something else if you are already running an FTP server on this ## system. ## default: 21 ftpPort = 21 ## Regular expression matching files that can't be manipulated by ## users in any way. If you want users to be able to upload their own ## plugins instead of using the ones you provide for them you can ## just comment this option out. ## default: empty forbiddenFiles = ## Set the level of detail for FTP server log messages in the multicraft.log. ## Errors will always be logged regardless of this setting. ## Available levels: ## - full Log all messages ## - basic Don't log client/server communication ## - none No FTP logging ## default: full ftpLogLevel = full ## If this setting is enabled the FTP server will not be started when the main ## daemon process is started. You can start the FTP server separately by using ## "start_ftp" instead of "start" as the parameter to the daemon command. ## default: false ftpSeparate = false ## The PID file for the FTP only process. The path is relative to "baseDir" ## default: multicraft_ftp.pid ftpPidFile = multicraft_ftp.pid ## The log file to use for the FTP only process. This setting has no effect if ## the FTP server is started as part of the main daemon process (i.e. if ## "ftpSeparate" is false. ## default: multicraft.log (same as the daemon) ftpLogFile = multicraft.log ## Throttle the FTP bandwidth (experimental) ## Incoming data throttle (Kb/s) ## default: 0 (unlimited) #ftpThrottleIn = 0 ## Outgoing data throttle (Kb/s) ## default: 0 (unlimited) #ftpThrottleOut = 0 Link para o comentário Compartilhar em outros sites More sharing options...
gaalaxY Postado Abril 22, 2020 Denunciar Compartilhar Postado Abril 22, 2020 Seu tópico foi marcado como Inativo. Para reverter esta ação, entre em contato com a equipe de Moderação. OBS: Essa mensagem é automática. Link para o comentário Compartilhar em outros sites More sharing options...
Posts Recomendados