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

GoGetSSL: "Unknown API method" error

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.4.0
    • Fix Version/s: 3.5.0-b2
    • Component/s: None
    • Labels:
      None

      Description

      When attempting to provision a service using GoGetSSL in sandbox mode, its possible to receive an error regardin an "Unknown API method" because "The requested method was not found". However, performing the same action with the production API works as expected.

      There may be some incompatibility issue or unsupported behavior with the sandbox that only the production API allows. We may want to consider disabling the sandbox API, or finding an alternate method to accomplish the same behavior (if available).

      See http://www.blesta.com/forums/index.php?/topic/3878-gogetssl-module-internal-error-or-no-response-from-server/


      The issue is that the "activateSSLOrder" API command is no longer supported. This task should remove its use. However, the module would not know when an order was successfully processed, as GoGetSSL expects us to query them periodically for that answer.

      Since we do not perform any periodic checks, we can only assume that the order is successful.

        Activity

        tyson Tyson Phillips (Inactive) created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Fix Version/s 3.5.0-b2 [ 10701 ]
        Fix Version/s 3.5.0-b1 [ 10401 ]
        admin Paul Phillips made changes -
        Fix Version/s 3.5.0-b2 [ 10701 ]
        tyson Tyson Phillips (Inactive) made changes -
        Summary GoGetSSL: Sandbox API differs from production API GoGetSSL: "Unknown API method" error
        tyson Tyson Phillips (Inactive) made changes -
        Fix Version/s 3.5.0-b2 [ 10701 ]
        tyson Tyson Phillips (Inactive) made changes -
        Description When attempting to provision a service using GoGetSSL in sandbox mode, its possible to receive an error regardin an "Unknown API method" because "The requested method was not found". However, performing the same action with the production API works as expected.

        There may be some incompatibility issue or unsupported behavior with the sandbox that only the production API allows. We may want to consider disabling the sandbox API, or finding an alternate method to accomplish the same behavior (if available).

        See http://www.blesta.com/forums/index.php?/topic/3878-gogetssl-module-internal-error-or-no-response-from-server/
        When attempting to provision a service using GoGetSSL in sandbox mode, its possible to receive an error regardin an "Unknown API method" because "The requested method was not found". However, performing the same action with the production API works as expected.

        There may be some incompatibility issue or unsupported behavior with the sandbox that only the production API allows. We may want to consider disabling the sandbox API, or finding an alternate method to accomplish the same behavior (if available).

        See http://www.blesta.com/forums/index.php?/topic/3878-gogetssl-module-internal-error-or-no-response-from-server/

        -----

        The issue is that the "activateSSLOrder" API command is no longer supported. This task should remove its use. However, the module would not know when an order was successfully processed, as GoGetSSL expects us to query them periodically for that answer.

        Since we do not perform any periodic checks, we can only assume that the order is successful.
        tyson Tyson Phillips (Inactive) made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        tyson Tyson Phillips (Inactive) made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          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:
              13/May/15