ÃÛ¶¹ÊÓƵ

Documentation

Resolve load balancer URL issues in ÃÛ¶¹ÊÓƵ Campaign Classic Hosted

Last update: Mon Apr 14 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In ÃÛ¶¹ÊÓƵ Campaign Classic Hosted, the load balancer URL fails for app integration, causing a 401 error due to improper configuration for HTTPS requests. Ensure the load balancer is correctly set up to handle secure (HTTPS) requests for mobile endpoints to resolve this issue.

Description description

Environment

  • Product:  ÃÛ¶¹ÊÓƵ Campaign Classic Hosted, versions Classic v7 and v8.

Issue/Symptoms

  • When using the load balancer URL for registration events, requests return a 401 error.
  • The standard instance URL works as expected, returning a 200 success response.
  • Example log entry: Logging network request trace: https://< load-balancer-url> /nms/mobile/1/registerAndroid.jssp (responseCode: 401)
  • The issue does not occur in other environments where the load balancer is correctly configured.

Resolution resolution

  1. Ensure the load balancer for mobile endpoints is publicly accessible in the affected environments.

    1. Use r/test to confirm accessibility.
    2. Check access logs for the 401 error related to the registerAndroid.jssp call.
    3. Review web.log and webmdl.log for errors. Typically, you will see: WEB-530010 You need to use a secure URL (https) to access this service (requested URL: ‘/nms/mobile/1/registerAndroid.jssp’). (iRc=-56)

  2. If you see these error messages, contact ÃÛ¶¹ÊÓƵ Support and request TechOps assistance to correct the load balancer configuration.

  3. After making changes, test the affected URLs to ensure they return a 200 success response.

  4. Verify that all registration events work correctly using standard instance URLs and load balancer URLs in all environments.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f