Tag: Axis HTTPS Setup

Categories
exacqVision Server Products

Axis Cameras using HTTPS With a Hostname

Description 

Axis Cameras running Firmware 9.0 and above fail to connect and stream video when configured to use a hostname instead of IP address and the protocol in the exacqVision Client has been set to HTTPS Required.

Product 

  • Axis Firmware 9.0 and above
  • exacqVision Server 22.06

Steps to Reproduce 

  1. Make sure the camera has a self-signed certificate and that the network and the server are set up accordingly. This would require a DNS pointer to be created.<br><br>
  2. Log into the camera’s web interface and navigate to certificate section.<br><br>
  3. Choose the appropriate certificate action.
    <br><br>
  4. Navigate to the HTTP/HTTPS menu.<br><br>
  5. Verify the Allow access through option is set to ‘HTTP and HTTPS’.
    1. In the exacqVision Client:
      1. Go to Add IP Cameras.
      2. In the Hostname/IP Address field, enter the hostname of the camera instead of the camera’s IP address.
      3. In the Protocol drop down box, select ‘HTTPS Required’.

    <br>

    Expected Results 

    The camera should connect and stream video.

    <br>

    Actual Results 

    • The camera fails to connect.
    • The Status shows “Device not Streaming” and the Troubleshooting Steps are “Device not streaming. The device is connected but video hasn’t been received in the last 10 seconds.”

    Solution

    Within the Add IP Cameras page of the client:

    1. Disable the camera.<br><br>
    2. Append #transport=tcp to the hostname already listed.

      Example: “axis-b8a44f307314” would become “axis-b8a44f307314#transport=tcp”<br><br>
    3. Enable the camera.<br><br>
    4. The camera should connect and stream video.

    <br>

    Categories
    Knowledge Support Support Categories Products exacqVision Integrations

    Axis HTTPS setup

    To setup an Axis camera for HTTPS support in 8.4.1 server.

    1. Log into the camera web page and go to the setup page.
    2. Select “System options” and HTTPS.
    3. The HTTPS settings page might look different between fw’s.
    4. To create self signed certificates, select the create option and fill in the required fields such as country/locality/state/organization/etc in the popup.
    5. To load a certificate, select the install signed certificates option and navigate to the certificate.
    6. Install the certificate.
    7. Set the policy for admin/operator/viewer to https or both(http/https)
    8. The plugin will try https and if failed will then try http.
    9. The Client will show a lock beside the device to indicate HTTPS connections.