Hi Marcos,

Thanks for reaching out on the forum and for sharing the details. I checked this with our R&D team - here is what the error means and what we suggest next.

The error error.ied.certificate.hostname.mismatch typically happens when AI Asset Manager retrieves the edge device’s IP addresses and its HTTPS certificate, then tries to find an address that the certificate is actually valid for. It could not match any of the device's reachable IPs/DNS names to the certificate's Subject Alternative Name (SAN) entries, so onboarding fails (because the agent (AIIS) needs the IP + cert to connect over HTTPS).

In short: this most likely points to a certificate misconfiguration on the edge device / inference server endpoint.

In this case, here are some thing to verify (quick checks)

Inspect the device certificate

• Open the device URL in a browser (the same address you use to reach the device) and view the certificate details, or

• Download the certificate from the device settings page (if available).

Check SAN entries

• Confirm the certificate contains the IP address and/or DNS name you are using to reach the device (and the one reachable from where the agent runs).

• The SAN should include the IP/DNS.

To answer your additional questions:

Is extra configuration needed during installation?

Usually no, as long as the certificate matches how the device is accessed. With default installs this normally works - issues tend to appear when the cert does not include the actually-used IP/DNS.

In order to diagnose the issue further and to provide you with the best support we would need some additional information.

Could you please share with us:

1. Network architecture

   • Any firewall, proxy, reverse proxy, or TLS inspection in between?

2. Edge device details

   • Edge device version

   • Network settings:

     • How many NICs (Network interfaces) do you have enabled/ are you using?

     • What is the NIC settings? Is the IP set static vs via DHCP?

     • Any Layer 2 setup? E.g., to connect to cameras via Vision Connector?

3. How you connect

   • Are you connecting via IEM (remote connection) or directly on the same network via IP/DNS name?

4. Logs

   • Please download logs from both AI Inference Server and AI Asset Manager.

   • In the IED app overview, click the three dots (⋮) and select Download logs.

5. Anything else

   • Any "non-standard" setup details that might matter.

If you want, paste the SAN section of the certificate (feel free to redact anything sensitive) plus the IP/DNS you use to access the device, and we can confirm the mismatch quickly.

Hope I could shed some light on the matter! Let me know if you have any more questions in the meantime.

Hi,

Thanks for the explanation. Regarding the connection details:

1. Network architecture
   • There are no firewalls, proxies, or TLS inspection
2. Edge device details
   • Edge device version: ievd-1.26.2-1-b
   • Network settings:
     • NICs: I have one network interface enabled (ens160).
       
     • NIC Settings: Mode: The IP is set as Static. The interface ens160 is configured with IP 10.1.21.84 and a /22 subnet mask (255.255.252.0).
     • Layer 2 setup: No, I am not using any Layer 2 setup.
3. How you connect
   • I am connecting directly on the same network via DNS/IP.
4. Logs
   • I have collected the logs as requested. I noticed some errors during the process, so I am attaching the screenshots for your review.

aiinferenceserver3p-aimm-agent-error-log

assetmanager_api-error

Additionally, I am attaching a screenshot of the certificate's SAN (Subject Alternative Name) section for your verification.

Please let me know if this information is sufficient or if you need anything else to proceed with the analysis.

Best regards,

Marcos

This issue is caused by a certificate SAN mismatch. AI Asset Manager tries to connect to AI Inference Server using an IP address or DNS name, but that address is not listed in the HTTPS certificate’s Subject Alternative Name (SAN). When no matching SAN entry is found, the onboarding fails with a hostname mismatch error.

The recommended approach is to use a single, stable connection address, preferably a DNS name, for the AI Inference Server. Then regenerate or replace the AIIS HTTPS certificate so that the SAN explicitly includes the DNS name (and optionally the IP address) that is used for the connection. After updating the certificate, retry the Update target connection step using the same address.

hi,

You don’t need to index the JSON manually in Mendix.

Jira returns issues[] as an array, and Mendix handles this by creating associated objects via the Import Mapping, not by flattening the JSON automatically.

Correct approach:

• Model the JSON properly: Root → Issue (0..*) → Fields
• Use Import Mapping with “Create objects”
• After Import from JSON, retrieve the Issue list via association from the Root
• Return List of Issue from the microflow
• Bind the Data Grid directly to the Issue entity
• Access nested data via associations (e.g. Issue/Fields/Summary)

Key rule:

In Mendix, you don’t “index” JSON arrays — you navigate the associations created by the import mapping.

Once you return the Issue list, the grid will work correctly.