Nexus' software components have new names:

Nexus PRIME -> Smart ID Identity Manager
Nexus Certificate Manager -> Smart ID Certificate Manager
Nexus Hybrid Access Gateway -> Smart ID Digital Access component
Nexus Personal -> Smart ID clients

Go to Nexus homepage for overviews of Nexus' solutions, customer cases, news and more.

Skip to end of metadata
Go to start of metadata

Here are some troubleshooting that you can do if the upgrade of Smart ID Digital Access component to 6.0.5 and above fails.

Expand/Collapse All

Problem: After upgrade to 6.0.5 or above, publishing one time does not connect the services.

Solution: Retry publishing or restart services and then publish again.

Problem: Publishing multiple times even does not connect the services.

Solution: Verify that for each service, the LocalConfiguration file (/opt/nexus/config/<service>/config/LocalConfiguration.xml) has the "Administration Service" object mHost attribute's value as "admin" instead of Host IP/

If not, follow these steps:

  1. Change mhost to "admin".

    Change mhost to "admin"
    <object key="c000ejp1m5" name="Administration Service" trans="ivjq0838gkxs" ver="50600">
    <attribute name="mAllInterfaces" type="boolean" value="false"/>
    <attribute name="mPort" type="integer" value="8300"/>
    <attribute name="mHost" type="string" value="admin"/>
    <attribute name="mType" type="integer" value="5"/>
    <attribute name="mId" type="integer" value="1"/>
  2. Restart the Digital Access services using the following commands:

    Restart services
    sudo docker stack rm da
    sudo bash /opt/nexus/scripts/

Problem: The access point does not connect and shows '403 Access Denied' when accessed.

Solution: Either restart all services or go to policy service setting in Digital Access Admin and click on Save and then Publish.

Problem: When restarting the services, if you get this message: 'da overlay network is missing' [Error response from daemon: network da_da-overlay not found]

Solution: Restart all the services again

Problem: Database max connection issue

Solution: Restart the postgres container.

This article is valid for Digital Access 6.0.5 and above.