Details
Improvement
Major
Description
When offering a dedicated IP address with the Multicraft module no port is specified. You'd think Multicraft would assign 25565 by default, since there are no other servers using the IP but this is not the case.
So, whenever we provision a Minecraft server using a dedicated IP from the pool, we need to set the port specifically to 25565, which is the default Minecraft port, and the entire reason people pay extra for a dedicated IP.
Reported here - http://www.blesta.com/forums/index.php?/topic/5527-multicraft-not-setting-dedicated-ips-properly/ and http://www.blesta.com/forums/index.php?/topic/5791-blesta-multicraft-dedicated-ip/
This task should:
- On the module row, the 'Dedicated IPs' table should support the full socket, IP:PORT. PORT may be best as a new field
- Setting only the IP will default to 25565
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
How about allowing users to set the default port to use (default to 25565), such as on the module row, rather than hard-coding 25565?
Tyson Phillips (Inactive)
added a comment - How about allowing users to set the default port to use (default to 25565), such as on the module row, rather than hard-coding 25565? I am alright with that, but it should default to 25565. It just seems like it may be over engineered to make it configurable given that the vast majority will expect a dedicated IP to be provisioned on that port.
Paul Phillips
added a comment - I am alright with that, but it should default to 25565. It just seems like it may be over engineered to make it configurable given that the vast majority will expect a dedicated IP to be provisioned on that port. It wouldn't need to be configurable if the Multicraft API supported determining the default port, but AFAIK that's not possible.
Tyson Phillips (Inactive)
added a comment - It wouldn't need to be configurable if the Multicraft API supported determining the default port, but AFAIK that's not possible. Ok then, let's add the setting, defaulting it to 25565 and release an updated module on the forums, including it in the next release.
Paul Phillips
added a comment - Ok then, let's add the setting, defaulting it to 25565 and release an updated module on the forums, including it in the next release. Tyson Phillips (Inactive)
made changes -
| Description |
When offering a dedicated IP address with the Multicraft module no port is specified. You'd think Multicraft would assign 25565 by default, since there are no other servers using the IP but this is not the case.
So, whenever we provision a Minecraft server using a dedicated IP from the pool, we need to set the port specifically to 25565, which is the default Minecraft port, and the entire reason people pay extra for a dedicated IP. Reported here - http://www.blesta.com/forums/index.php?/topic/5527-multicraft-not-setting-dedicated-ips-properly/ and http://www.blesta.com/forums/index.php?/topic/5791-blesta-multicraft-dedicated-ip/ |
When offering a dedicated IP address with the Multicraft module no port is specified. You'd think Multicraft would assign 25565 by default, since there are no other servers using the IP but this is not the case.
So, whenever we provision a Minecraft server using a dedicated IP from the pool, we need to set the port specifically to 25565, which is the default Minecraft port, and the entire reason people pay extra for a dedicated IP. Reported here - http://www.blesta.com/forums/index.php?/topic/5527-multicraft-not-setting-dedicated-ips-properly/ and http://www.blesta.com/forums/index.php?/topic/5791-blesta-multicraft-dedicated-ip/ This task should: - On the module row, the 'Dedicated IPs' table should support the full socket, IP:PORT - Setting only the IP will default to 25565 |
Tyson Phillips (Inactive)
made changes -
| Description |
When offering a dedicated IP address with the Multicraft module no port is specified. You'd think Multicraft would assign 25565 by default, since there are no other servers using the IP but this is not the case.
So, whenever we provision a Minecraft server using a dedicated IP from the pool, we need to set the port specifically to 25565, which is the default Minecraft port, and the entire reason people pay extra for a dedicated IP. Reported here - http://www.blesta.com/forums/index.php?/topic/5527-multicraft-not-setting-dedicated-ips-properly/ and http://www.blesta.com/forums/index.php?/topic/5791-blesta-multicraft-dedicated-ip/ This task should: - On the module row, the 'Dedicated IPs' table should support the full socket, IP:PORT - Setting only the IP will default to 25565 |
When offering a dedicated IP address with the Multicraft module no port is specified. You'd think Multicraft would assign 25565 by default, since there are no other servers using the IP but this is not the case.
So, whenever we provision a Minecraft server using a dedicated IP from the pool, we need to set the port specifically to 25565, which is the default Minecraft port, and the entire reason people pay extra for a dedicated IP. Reported here - http://www.blesta.com/forums/index.php?/topic/5527-multicraft-not-setting-dedicated-ips-properly/ and http://www.blesta.com/forums/index.php?/topic/5791-blesta-multicraft-dedicated-ip/ This task should: - On the module row, the 'Dedicated IPs' table should support the full socket, IP:PORT. PORT may be best as a new field - Setting only the IP will default to 25565 |
| Assignee | Tyson Phillips [ tyson ] | Jonathan Reissmueller [ jonathan ] |
Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Automated transition triggered when Jonathan Reissmueller created pull request #6 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
Paul Phillips
made changes -
| Fix Version/s | 4.0.0 [ 10603 ] | |
| Fix Version/s | Short Term [ 10800 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #6 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |
If this is fairly simple, we should implement a fix for 4.0 and release a hotfix on the forums. Quite a few people are experiencing this.