Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2062

Multicraft: Force port 25565 for dedicated IP addresses

        Details

        • Type: Improvement
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 3.6.0
        • Fix Version/s: 4.0.0-b1
        • Component/s: Modules
        • Labels:
          None

          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

            Descending order - Click to sort in ascending order
            Automated transition triggered when Tyson Phillips (Inactive) merged pull request #6 in Stash -
            Status In Review [ 5 ] Closed [ 6 ]
            admin Paul Phillips made changes -
            Fix Version/s 4.0.0 [ 10603 ]
            Fix Version/s Short Term [ 10800 ]
            Automated transition triggered when Jonathan Reissmueller created pull request #6 in Stash -
            Status In Progress [ 3 ] In Review [ 5 ]
            Resolution Fixed [ 1 ]
            Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
            Status Open [ 1 ] In Progress [ 3 ]
            jonathan Jonathan Reissmueller made changes -
            Assignee Tyson Phillips [ tyson ] Jonathan Reissmueller [ jonathan ]
            tyson 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
            tyson 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
            admin Paul Phillips made changes -
            Field Original Value New Value
            Rank Ranked higher
            admin Paul Phillips created issue -

              People

              • Assignee:
                jonathan Jonathan Reissmueller
                Reporter:
                admin Paul Phillips
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  15/Sep/16