Imperva Cyber Community

communities_1.jpg
 View Only

  • 1.  Gateway could not be registered with the SecureSphere management server.

    Posted 03-01-2022 01:45
    Hi All, 

    Greeting for the day. !

    Facing error while implementing new gateway. Getting error while booting process and it's get failed. 
    Gateway version is 14.4.1.10._0. 

    Showing like this. 

    Warning: The gateway could not be registered with the SecureSphere management server.
    Please check that the following are true:
    1. You supplied the correct password and IP address for the management server
    2. The management server is running
    3. You supplied the correct name of the gateway destined to be replaced by this gateway(Optional)
    4. If the Server is in Trust enforce mode make sure GW is in FIPS mode and that the GW does not contain non ssl listener
    If either of these is not true, correct and try again.

    impctl boot ... [ FAILED ]


    Error: The transaction has failed. For more information, execute 'impctl show log' for details!, Press <Enter> to continue:

    [root@XYZ ~]# impctl restart service
    Stopping SecureSphere gateway ... [ OK ]
    Starting SecureSphere gateway ...[FAILED]
    01/03/2022 10:23:38.847139 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 1 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:23:44.433890 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 2 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:23:50.018848 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 3 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:23:55.578772 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 4 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:24:01.140658 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 5 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:24:06.760400 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 6 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:24:12.373522 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 7 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:24:19.238017 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 8 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:24:24.864826 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 9 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:24:30.449665 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: Response from Management Server for the product query attempt 10 failed. Retrying. Max. retry attempts: 10
    01/03/2022 10:24:36.068914 [log_error] /mnt/workspace/ci-dam_14.4.1.10-pipeline-dam/Gateway/src/argus/gwlib/TrustUtils.cpp:1225 platformGetAction - failed to perform Http Get action to MX on URL- /SecureSphere/gateway_request/mx_product_info. Http code: 400.
    _verify_compatible_mx_version_and_product_type: No response from Management Server for the product query. Please contact support. (exit status: 100)
    Cannot connect to X.X.X.X:8083 [HTTP: 450 APP: response code is 450. Invalid Password] (exit status: 100)
    Cannot register gateway (vendor: Imperva) (exit status: 7)
    Failed to start service "gateway". (exit status: 7)
    Cannot start gateway (exit status: 7

    If anyone had facing the same challenge while deploying new gateway. Please suggest on this. 

    Regards,
    #DatabaseActivityMonitoring

    ------------------------------
    Debajyoti Paul
    IT security manager
    Dubai
    ------------------------------


  • 2.  RE: Gateway could not be registered with the SecureSphere management server.

    Posted 03-03-2022 07:55
    Edited by Sarah LAMONT 03-03-2022 08:36
    Hi there,

    I am afraid you will need to raise a ticket  on the support portal for this one. There could be a number of possible causes, so the support team would need to look at your upgrade log to learn more.

    Thanks,




  • 3.  RE: Gateway could not be registered with the SecureSphere management server.

    Posted 07-21-2022 03:09
    Edited by Stefan Sia 07-21-2022 03:09
    During the First-Time Login (ftl) on new GW, we should key in the same "secure" user's password with Management Server (MX).
    This is used to register the GW with MX.

    First-Time Login for the Gateway
    https://docs.imperva.com/bundle/v14.8-dam-vmware-installation-guide/page/65037.htm

    ------------------------------
    Stefan Sia
    Product Support Engineer
    Imperva Singapore
    ------------------------------



  • 4.  RE: Gateway could not be registered with the SecureSphere management server.

     
    Posted 06-02-2025 12:59

    As you wish, we need to re-check secure account, right?



    ------------------------------
    Bui Duc
    Security Engineer
    SOTA VIETNAM TECHNOLOGY JOINT STOCK COMPANY
    Hanoi
    ------------------------------

    Original Message


  • 5.  RE: Gateway could not be registered with the SecureSphere management server.

    Posted 06-02-2025 20:25
    Edited by Stefan Sia 06-02-2025 20:25

    Hi,

    If you're not sure what is your MX server 'secure' password, you may refer to this article:

    • https://docs.imperva.com/bundle/z-kb-articles-knowledgebase-support/page/288984872.html

    Once you've confirmed the secure password in MX, you may login to GW CLI and re-run FTL or re-register to MX by referring this article: 

    • https://docs.imperva.com/bundle/v14.19-dam-administration-guide/page/8747.htm 



    ------------------------------
    Stefan Sia
    Technical Account Manager
    Imperva Singapore
    ------------------------------

    Original Message