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

Multicraft: Notify Multicraft that it should reselect the IP:Port

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.4.2
    • Fix Version/s: 3.4.3, 3.5.0-b1
    • Component/s: Modules
    • Labels:
      None

      Description

      Currently, the module relies on Multicraft to determine the server IP and Port. However, if the daemon changes and no socket address is specified (e.g. no dedicated IP), then Multicraft continues to use the socket address that it generated when the server was created. This could be, for instance, on daemon ID 1. Thus, the socket address is no longer valid for the given daemon.

      Daniel from Multicraft advised that specifying no value (empty strings) for both the IP and Port fields will force Multicraft to reselect a new socket address based on the current daemon.

        Issue Links

          Activity

          tyson Tyson Phillips (Inactive) created issue -
          tyson Tyson Phillips (Inactive) made changes -
          Field Original Value New Value
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          tyson Tyson Phillips (Inactive) made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          tyson Tyson Phillips (Inactive) made changes -
          Link This issue relates to CORE-3223 [ CORE-3223 ]

            People

            • Assignee:
              tyson Tyson Phillips (Inactive)
              Reporter:
              tyson Tyson Phillips (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                25/Mar/15