Multicraft Not Automatically Setting Up Dedicated Ips For Clients.

[MariusB]

Hey there,

 

I've installed the Multicraft addon and hooked it up to our dedicated server. When we order, everything works fine, except for setting up dedicated IPs. We have a configurable option that edits the Value of the "dedicated_ip" permission (http://marius.li/i/hDSxH.png). When I order, I click the Dedicated IP button (creatively named "Yes, I don't want an ugly port!) so it is flagged to a yes (http://marius.li/i/X8u0y.png).

 

When the server is then set up after paying, we don't get the correct port in Multicraft (http://marius.li/i/fZQBG.png). We make sure that the IP is available every time.

 

Any idea how to fix this?

[Blesta Addons]

this was already a bug and corected http://www.blesta.com/forums/index.php?/topic/3175-multicraft-does-not-pick-ip/?hl=multicraft

also check this thread

http://www.blesta.com/forums/index.php?/topic/3302-multicraft-module-dedicated-ip/?hl=multicraft

[Paul]

@MariusB, what version of Blesta are you running? The 3.3.0 official build should include the latest Multicraft module which addressed this issue. Thanks @naja7host

[ericlimab]

We are running Version 3.3.0, and Multicraft Module 1.2.0. 

 

this was already a bug and corected http://www.blesta.com/forums/index.php?/topic/3175-multicraft-does-not-pick-ip/?hl=multicraft

also check this thread

http://www.blesta.com/forums/index.php?/topic/3302-multicraft-module-dedicated-ip/?hl=multicraft

We are already running the latest build, and it's a problem where the Dedicated IP won't be assigned itself. 

http://<REMOVED>|createServer
a:4:{i:0;s:0:"";i:1;s:0:"";i:2;s:0:"";i:3;s:2:"20";}

http://<REMOVED>|createServer
s:46:"{"success":true,"errors":[],"data":{"id":"7"}}";

[Tyson]

Hey there,

 

I've installed the Multicraft addon and hooked it up to our dedicated server. When we order, everything works fine, except for setting up dedicated IPs. We have a configurable option that edits the Value of the "dedicated_ip" permission (http://marius.li/i/hDSxH.png). When I order, I click the Dedicated IP button (creatively named "Yes, I don't want an ugly port!) so it is flagged to a yes (http://marius.li/i/X8u0y.png).

 

When the server is then set up after paying, we don't get the correct port in Multicraft (http://marius.li/i/fZQBG.png). We make sure that the IP is available every time.

 

Any idea how to fix this?

 

Blesta doesn't set a specific port when creating the server unless you provide that information (or it is already available from the package) when the service is created. Instead, Multicraft determines the next available port based off of your Multicraft settings and any other servers that are currently setup, in order to avoid duplicates. Perhaps your starting port number is not 25565 in Multicraft, or you have multiple Multicraft servers on that IP such that new servers get assigned a different port? I would need to see module log information to know more.

 

 

 

We are running Version 3.3.0, and Multicraft Module 1.2.0. 

 

We are already running the latest build, and it's a problem where the Dedicated IP won't be assigned itself. 

http://<REMOVED>|createServer
a:4:{i:0;s:0:"";i:1;s:0:"";i:2;s:0:"";i:3;s:2:"20";}

http://<REMOVED>|createServer
s:46:"{"success":true,"errors":[],"data":{"id":"7"}}";

 

Could you clarify? The log you've included looks correct--simply creating a server. There should also be several subsequent logs, and if you have an available dedicated IP setup under [settings] -> [Modules] -> [Multicraft] that was set for that service, you should also have a log entry regarding updating the server to use that dedicated IP. For example:

http://domain.com/multicraft/api.php|updateServer
a:3:{i:0;s:2:"78";i:1;a:2:{i:0;s:2:"ip";i:1;s:9:"daemon_id";}i:2;a:2:{i:0;s:13:"123.123.123.123";i:1;s:1:"1";}}

That log shows the IP being set to 123.123.123.123 and the daemon ID set to 1.

 

Search the page for ip and you should find that log entry indicating the dedicated IP was set.

The last log in the list contains the information set for the server as given by Multicraft, which should contain the same IP. For example:

http://domain.com/multicraft/api.php|getServer
s:353:"{"success":true,"errors":[],"data":{"Server":{"memory":"256","start_memory":"0","port":"25580","id":"78","name":"Minecraft Server","ip":"123.123.123.123","dir":"server1","world":"","players":"10","jarfile":"","autostart":"1","default_level":"10","daemon_id":"1","announce_save":"1","kick_delay":"3000","suspended":"0","autosave":"1","jardir":"daemon"}}}";

[ericlimab]

INPUT

|updateServer
a:3:{i:0;s:1:"8";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:16:"Minecraft Server";i:1;s:1:"1";i:2;s:2:"10";i:3;s:0:"";i:4;s:11:"server_base";i:5;s:4:"3072";i:6;s:2:"60";i:7;s:1:"1";}}

INPUT

|updateServer
a:3:{i:0;s:1:"8";i:1;a:2:{i:0;s:2:"ip";i:1;s:9:"daemon_id";}i:2;a:2:{i:0;s:12:"my_PUBLIC_IP";i:1;s:1:"1";}}

OUTPUT

|getServer
s:355:"{"success":true,"errors":[],"data":{"Server":{"memory":"3072","start_memory":"0","port":"25571","id":"8","name":"Minecraft Server","ip":"my_PUBLIC_IP","dir":"server8","world":"","players":"60","jarfile":"","autostart":"1","default_level":"10","daemon_id":"1","announce_save":"1","kick_delay":"3000","suspended":"0","autosave":"1","jardir":"server_base"}}}";

We have 1 suspended server on the 25565 port. Is there any way we can limit the orders for this option or make this an addon?

Also, after suspension immediately terminate/delete the server?

Here is a screenshot of the option

http://gyazo.com/7e0a4b2398c905044ccbae892fd98601

[Tyson]

Based on your logs, it looks like it's working correctly. Is the "my_PUBLIC_IP" not correct?

 

 

We have 1 suspended server on the 25565 port. Is there any way we can limit the orders for this option or make this an addon?

You could create an addon that uses the config option, but I'm not sure that's what you're looking for here. Config options don't have limits, so as long as they are assigned to the package they will be available. You could set a limit on the package instead, and only set that config option for that package--kind of like a dedicated MC server only package.

 

 

Also, after suspension immediately terminate/delete the server?

 

A suspended service in Blesta can be reactivated upon payment, or manually if you choose to do so. So it does not immediately delete the Multicraft server on suspension. You can, however, delete the server by cancelling the service instead. The directory for any saved files related to that server in Multicraft will not be deleted, though. Most people tend not to want automated cancellations to be done unless they are scheduled to be cancelled, or are cancelled manually, because there is no recovery from the action after it has been performed.

[ericlimab]

Based on your logs, it looks like it's working correctly. Is the "my_PUBLIC_IP" not correct?

Server is setup, but the IP is not a dedicated IP.

You could create an addon that uses the config option, but I'm not sure that's what you're looking for here. Config options don't have limits, so as long as they are assigned to the package they will be available. You could set a limit on the package instead, and only set that config option for that package--kind of like a dedicated MC server only package.

I will look into that.

 

A suspended service in Blesta can be reactivated upon payment, or manually if you choose to do so. So it does not immediately delete the Multicraft server on suspension. You can, however, delete the server by cancelling the service instead. The directory for any saved files related to that server in Multicraft will not be deleted, though. Most people tend not to want automated cancellations to be done unless they are scheduled to be cancelled, or are cancelled manually, because there is no recovery from the action after it has been performed.

Ok. Is there any way I can set a cron job like "after 15days of suspension, run the server delete method"?

[Tyson]

Server is setup, but the IP is not a dedicated IP.

When someone orders a dedicated IP using that config option, one of the IPs that you have set under [settings] -> [Modules] -> [Multicraft] (Manage) -> (edit) will be chosen if it is not currently in use. If none are available, it will instead choose the best daemon to use based on memory usage, and Multicraft will assign an appropriate IP.

 

 

Ok. Is there any way I can set a cron job like "after 15days of suspension, run the server delete method"?

You could write a plugin that adds a cron task to perform that action on the module via cron.

[ericlimab]

When someone orders a dedicated IP using that config option, one of the IPs that you have set under [settings] -> [Modules] -> [Multicraft] (Manage) -> (edit) will be chosen if it is not currently in use. If none are available, it will instead choose the best daemon to use based on memory usage, and Multicraft will assign an appropriate IP.

The IPs are correctly added and the IP is marked not in use.

[Tyson]

So you're saying that:

1. You have dedicated IPs available for a module row that are not currently in use, and they are set to the correct daemon ID in Multicraft as you have defined them in Blesta - as described in the docs
2. You add a service, whose package uses that module row, and you select the config option for a dedicated IP as described in the docs
3. The logs show that an IP and Daemon ID combination have been sent to Multicraft as the dedicated IP address - obfuscated as "my_PUBLIC_IP" in your logs, above

All of that sounds like valid behavior. So the question, then, is what IP address did you expect to be set for the server? What incorrect IP did it set, and where did it get this incorrect IP address from?

The module would only select an IP address that was available in the dedicated IP list, as described in #1.

[ericlimab]

So you're saying that:

• You have dedicated IPs available for a module row that are not currently in use, and they are set to the correct daemon ID in Multicraft as you have defined them in Blesta - as described in the docs
• You add a service, whose package uses that module row, and you select the config option for a dedicated IP as described in the docs
• The logs show that an IP and Daemon ID combination have been sent to Multicraft as the dedicated IP address - obfuscated as "my_PUBLIC_IP" in your logs, above

All of that sounds like valid behavior. So the question, then, is what IP address did you expect to be set for the server? What incorrect IP did it set, and where did it get this incorrect IP address from?

The module would only select an IP address that was available in the dedicated IP list, as described in #1.

I mean dedicated IP's, with a 25565 port. 1, 2, 3 are all yes.

[Tyson]

I mean dedicated IP's, with a 25565 port. 1, 2, 3 are all yes.

 

Multicraft chooses the port based on the port setting you have set in your Multicraft account under [settings] -> (Base server port to use on new IPs).

 

If your IP:25565 is currently in use, you're going to receive a different port number when you assign a server to that IP. But by adding more than one server to an IP, you can no longer call it dedicated.

 

It looks like the module is handling the use of IPs properly, but either your settings in Multicraft are not set such that 25565 is the base server port, or Multicraft internally determined, for whatever reason, that a different port should be used.