Jump to content
  • 0

Multicraft Not Setting Dedicated Ips Properly

wmak907

Asked by wmak907,

 Share

Question

wmak907 Newbie

wmak907

Posted
Posted

Hello,

 

I am currently experiencing an issue regarding the Multicraft module. Upon purchasing a package without a dedicated IP, the email displays the IP as this: 

Here are more details regarding your server:

Server Name: Test - No Dedicated IP 01
Server Address: 0.0.0.0:25572

Log:

s:355:"{"success":true,"errors":[],"data":{"Server":{"memory":"256","start_memory":"1024","port":"25572","id":"8","name":"Test - No Dedicated IP 01","ip":"0.0.0.0","dir":"server8","world":"","players":"6","jarfile":"","autostart":"1","default_level":"10","daemon_id":"1","announce_save":"1","kick_delay":"3000","suspended":"0","autosave":"1","jardir":"server"}}}";

Now, when I attempt to purchase a package with a dedicated IP, the IP displays properly however the port is not set to the default Minecraft port (25565):

Note: IP snipped for security reasons.

Here are more details regarding your server:

Server Name: A New Server!
Server Address: xx.xxx.xxx.224:25574

Log for dedicated IP purchase:

s:353:"{"success":true,"errors":[],"data":{"Server":{"memory":"256","start_memory":"1024","port":"25574","id":"9","name":"A New Server!","ip":"0.0.0.0","dir":"server9","world":"","players":"6","jarfile":"","autostart":"1","default_level":"10","daemon_id":"1","announce_save":"1","kick_delay":"3000","suspended":"0","autosave":"1","jardir":"server"}}}";

I've been trying to figure this out for the past several hours and I am at a loss.

 

Any help would be greatly appreciated.

 

Thanks!

11 answers to this question

Recommended Posts

  • 0
wmak907 Newbie

wmak907

Posted
  • Author
Posted

Update:

 

So I was able to figure out why the IP address was not showing in the emails. To fix this, I simply logged in as admin to the Multicraft control panel, navigated to "Settings" and under the "Default Server IP" drop-down, I selected "Daemon IP".

 

Unfortunately, the dedicated IPs are still not being set up properly.

 

New log:

s:362:"{"success":true,"errors":[],"data":{"Server":{"memory":"256","start_memory":"1024","port":"25579","id":"12","name":"A New Server!","ip":"xx.xxx.xxx.153","dir":"server12","world":"","players":"6","jarfile":"","autostart":"1","default_level":"10","daemon_id":"1","announce_save":"1","kick_delay":"3000","suspended":"0","autosave":"1","jardir":"server"}}}";
  • 0
Tyson Newbie

Tyson

Posted
Posted

Multicraft determines the port to use for the accounts that are setup to avoid reusing an existing port. The comment on this task describes the problem of Multicraft incrementing ports while this task aims to simplify API calls which may or may not resolve the issue with Multicraft skipping port numbers it increments.

 

Always using a specific port like 25565 would require the module to allow you to specify a particular port to use, which is a task we would need to add. However, I'm not sure what will happen if you specify a port for a service that is already in use in Multicraft.

  • 0
wmak907 Newbie

wmak907

Posted
  • Author
Posted

It is still not setting up correctly. I have completely reinstalled Blesta 3 times now with no avail. I have also followed the Multicraft Blesta module instructions to a T, yet I am still having the same problem. I am at a loss, do you have any suggestions?

 

Here's a more in-depth explanation of what is happening.

I have several IPs setup on the dedicated server. I created a "Dedicated IP" configurable option as directed in the Multicraft Blesta module instructions. I also entered in all of the IPs correctly to the Multicraft Blesta module. When I go to purchase a package with the dedicated IP option, it successfully sets the server up on a new IP, however the port is not set to 25565. It climbs from the original port (25565). I am using the most recent Blesta release, 3.6.1. My Multicraft panel settings also have the settings for the default port set to 25565. I am beyond confused at this point

 

Update: Nothing regarding the dedicated IP option seems to be working. As of now, every server defaults to the main daemon IP. This is a major problem, as clients are not able to purchase a dedicated IP and have it setup instantly. I have a total of 17 IPs on the server list, all of which have been set up properly to my best knowledge.

 

Multicraft Blesta Module Dedicated IP Setup:

http://puu.sh/lwN0p/a4430d5c5d.png

 

Complete API Log:

Input (Success):
http://mydomain.net/mc/api.php|findUsers
a:2:{i:0;s:4:"name";i:1;s:22:"myemail@gmail.com";}

Output (Success):
http://mydomain.net/mc/api.php|findUsers
s:77:"{"success":true,"errors":[],"data":{"Users":{"12":"myemail@gmail.com"}}}";

-

Input (Success):
http://mydomain.net/mc/api.php|createServer
a:4:{i:0;s:0:"";i:1;s:0:"";i:2;s:0:"";i:3;s:1:"6";}

Output (Success):
http://mydomain.net/mc/api.php|createServer
s:47:"{"success":true,"errors":[],"data":{"id":"42"}}";

-

Input (Success):
http://mydomain.net/mc/api.php|setServerOwner
a:2:{i:0;s:2:"42";i:1;i:12;}

Output (Success):
http://mydomain.net/mc/api.php|setServerOwner
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|listConnections
a:0:{}

Output (Success):
http://mydomain.net/mc/api.php|listConnections
s:73:"{"success":true,"errors":[],"data":{"Daemons":{"1":"Multicraft Daemon"}}}";

-

Input (Success):
http://mydomain.net/mc/api.php|getConnectionMemory
a:1:{i:0;s:1:"1";}

Output (Success):
http://mydomain.net/mc/api.php|getConnectionMemory
s:68:"{"success":true,"errors":[],"data":{"total":"141312","used":"1280"}}";

-

Input (Success):
http://mydomain.net/mc/api.php|updateServer
a:3:{i:0;s:2:"42";i:1;a:8:{i:0;s:4:"name";i:1;s:9:"autostart";i:2;s:13:"default_level";i:3;s:7:"jarfile";i:4;s:6:"jardir";i:5;s:6:"memory";i:6;s:7:"players";i:7;s:9:"daemon_id";}i:2;a:8:{i:0;s:23:"A New Minecraft Server!";i:1;s:1:"0";i:2;s:2:"10";i:3;s:0:"";i:4;s:6:"daemon";i:5;s:3:"256";i:6;s:1:"6";i:7;s:1:"1";}}

Output (Success):
http://mydomain.net/mc/api.php|updateServer
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|updateServerConfig
a:3:{i:0;s:2:"42";i:1;a:6:{i:0;s:8:"user_ftp";i:1;s:8:"user_jar";i:2;s:7:"visible";i:3;s:13:"user_schedule";i:4;s:9:"user_name";i:5;s:15:"user_visibility";}i:2;a:6:{i:0;s:1:"1";i:1;s:1:"1";i:2;s:1:"0";i:3;s:1:"1";i:4;s:1:"1";i:5;s:1:"0";}}

Output (Success):
http://mydomain.net/mc/api.php|updateServerConfig
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|updateServer
a:3:{i:0;s:2:"42";i:1;a:2:{i:0;s:2:"ip";i:1;s:9:"daemon_id";}i:2;a:2:{i:0;s:14:"58.69.111.224";i:1;s:1:"1";}}

Output (Success):
http://mydomain.net/mc/api.php|updateServer
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|updateServer
a:3:{i:0;s:2:"42";i:1;a:2:{i:0;s:2:"ip";i:1;s:4:"port";}i:2;a:2:{i:0;s:0:"";i:1;s:0:"";}}

Output (Success):
http://mydomain.net/mc/api.php|updateServer
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|getServer
a:1:{i:0;s:2:"42";}

Output (Success):
http://mydomain.net/mc/api.php|getServer
s:359:"{"success":true,"errors":[],"data":{"Server":{"memory":"256","start_memory":"0","port":"25567","id":"42","name":"A New Minecraft Server!","ip":"58.69.118.153","dir":"server42","world":"","players":"6","jarfile":"","autostart":"0","default_level":"10","daemon_id":"1","announce_save":"1","kick_delay":"3000","suspended":"0","autosave":"1","jardir":"daemon"}}}";  
  • 0
wmak907 Newbie

wmak907

Posted
  • Author
Posted

The lack of functionality and documentation for the Multicraft module is displeasing. There are several features that I'd love to see implemented in the near future. Some of which being an option for the "user_players" coming default within the package, rather than having it set as a configurable option. Also, the majority of the pictures included in the documentation are obsolete, as there are new options within Blesta as well as the Multicraft module. As much as I love Blesta and the amazing community, the lack of features with this module is quite disappointing. I would love to see more documentation regarding setting up the dedicated IP option within the module; as it appears that there have been multiple users experiencing the same problem that I have regarding the dedicated IP option setup. None of the forum posts (that I have come across) have a definite solution to the dedicated IP problem.

  • 0
Tyson Newbie

Tyson

Posted
Posted

Thanks for including the module logs. It looks like the dedicated IP is set and then later overwritten. You might try making a quick change to the module and checking whether it will work correctly,

i.e. backup the file /components/modules/multicraft/lib/multicraft_service.php and find

if (empty($vars[$this->service_prefix . $service_field]))

change it to

if (empty($vars[$this->service_prefix . $service_field]) && empty($config_options['ip']))

Then try adding a service with a dedicated IP to see if that resolves the problem.

 

 

Also, the majority of the pictures included in the documentation are obsolete, as there are new options within Blesta as well as the Multicraft module.

Which images are you referring to? I've looked over the Multicraft images and the only differences I see are that the config option screenshots do not include "Client can Add" and "Client can Edit" checkboxes, which would not impact your Multicraft configuration.

 

 

I would love to see more documentation regarding setting up the dedicated IP option within the module; as it appears that there have been multiple users experiencing the same problem that I have regarding the dedicated IP option setup. None of the forum posts (that I have come across) have a definite solution to the dedicated IP problem.

Which forum posts are you referring to?

  • 0
wmak907 Newbie

wmak907

Posted
  • Author
Posted

Tyson,

 

It seems that it's now selecting the correct IP, however it is not creating the server on the default 25565 port.

 

New Complete Log:

Input (Success):
http://mydomain.net/mc/api.php|findUsers
a:2:{i:0;s:4:"name";i:1;s:18:"myemail@gmail.com";}

Output (Success):
http://mydomain.net/mc/api.php|findUsers
s:48:"{"success":true,"errors":[],"data":{"Users":[]}}";

-

Input (Success):
http://mydomain.net/mc/api.php|createUser
a:3:{i:0;s:18:"myemail@gmail.com";i:1;s:18:"myemail@gmail.com";i:2;s:12:"^!j9PGA#ci@t";}

Output (Success):
http://mydomain.net/mc/api.php|createUser
s:47:"{"success":true,"errors":[],"data":{"id":"14"}}";

-

Input (Success):
http://mydomain.net/mc/api.php|createServer
a:4:{i:0;s:0:"";i:1;s:0:"";i:2;s:0:"";i:3;s:1:"6";}

Output (Success):
http://mydomain.net/mc/api.php|createServer
s:47:"{"success":true,"errors":[],"data":{"id":"45"}}";

-

Input (Success):
http://mydomain.net/mc/api.php|setServerOwner
a:2:{i:0;s:2:"45";i:1;s:2:"14";}

Output (Success):
http://mydomain.net/mc/api.php|setServerOwner
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|listConnections
a:0:{}

Output (Success):
http://mydomain.net/mc/api.php|listConnections
s:73:"{"success":true,"errors":[],"data":{"Daemons":{"1":"Multicraft Daemon"}}}";

-

Input (Success):
http://mydomain.net/mc/api.php|getConnectionMemory
a:1:{i:0;s:1:"1";}

Output (Success):
http://mydomain.net/mc/api.php|getConnectionMemory
s:68:"{"success":true,"errors":[],"data":{"total":"141312","used":"1280"}}";

-

Input (Success):
http://mydomain.net/mc/api.php|updateServer
a:3:{i:0;s:2:"45";i:1;a:8:{i:0;s:4:"name";i:1;s:9:"autostart";i:2;s:13:"default_level";i:3;s:7:"jarfile";i:4;s:6:"jardir";i:5;s:6:"memory";i:6;s:7:"players";i:7;s:9:"daemon_id";}i:2;a:8:{i:0;s:29:"A New Minecraft Server!";i:1;s:1:"1";i:2;s:2:"10";i:3;s:0:"";i:4;s:6:"server";i:5;s:3:"256";i:6;s:1:"6";i:7;s:1:"1";}}

Output (Success):
http://mydomain.net/mc/api.php|updateServer
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|updateServerConfig
a:3:{i:0;s:2:"45";i:1;a:6:{i:0;s:8:"user_ftp";i:1;s:8:"user_jar";i:2;s:7:"visible";i:3;s:13:"user_schedule";i:4;s:9:"user_name";i:5;s:15:"user_visibility";}i:2;a:6:{i:0;s:1:"1";i:1;s:1:"1";i:2;s:1:"0";i:3;s:1:"1";i:4;s:1:"1";i:5;s:1:"0";}}

Output (Success):
http://mydomain.net/mc/api.php|updateServerConfig
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|setUserFtpAccess
a:3:{i:0;s:2:"14";i:1;s:2:"45";i:2;s:2:"rw";}

Output (Success):
http://mydomain.net/mc/api.php|setUserFtpAccess
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|updateServer
a:3:{i:0;s:2:"45";i:1;a:2:{i:0;s:2:"ip";i:1;s:9:"daemon_id";}i:2;a:2:{i:0;s:14:"158.69.111.224";i:1;s:1:"1";}}

Output (Success):
http://mydomain.net/mc/api.php|updateServer
s:38:"{"success":true,"errors":[],"data":[]}";

-

Input (Success):
http://mydomain.net/mc/api.php|getServer
a:1:{i:0;s:2:"45";}

Output (Success):
http://mydomain.net/mc/api.php|getServer
s:365:"{"success":true,"errors":[],"data":{"Server":{"memory":"256","start_memory":"0","port":"25566","id":"45","name":"A New Minecraft Server!","ip":"58.69.111.224","dir":"server45","world":"","players":"6","jarfile":"","autostart":"1","default_level":"10","daemon_id":"1","announce_save":"1","kick_delay":"3000","suspended":"0","autosave":"1","jardir":"server"}}}";
  • 0
Tyson Newbie

Tyson

Posted
Posted

The thread you linked to describes how you could force port 25565 to be used. The module is currently designed to let Multicraft determine the port because the API does not provide a method of determining what ports are available for use, so we cannot reliably choose one. We'll have to make another pass on the module to see if we can improve that behavior.

 

Does the dedicated IP address work now because you made the source change I mentioned above?

  • 0
wmak907 Newbie

wmak907

Posted
  • Author
Posted

Does the dedicated IP address work now because you made the source change I mentioned above?

 

It selects the new IP, however the port still increments off of the last one. Would a custom plugin be able to do this for me?

 

 

Also, not sure if this is possible or not. However, within the module if there was a way to set a base daemon IP for all non-dedicated IPs. Then another list for the dedicated IPs, which would always default to port 25565. Not sure if that makes any sense or not.

  • 0
Tyson Newbie

Tyson

Posted
Posted

I'm not sure I follow your idea of setting a base daemon IP. The Multicraft module will choose the "best" daemon to use based on the amount of resources available from all daemons available on your account, and then assign the service to that daemon if you are not using a dedicated IP. What are you envisioning for an alternative?

 

 

It selects the new IP, however the port still increments off of the last one. Would a custom plugin be able to do this for me?

 

A plugin wouldn't solve it. You would need to update the module itself to force a specific port. Did you try updating the module as I mentioned in this other thread?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to question listing
×
×
  • Create New...