Troubleshooting

This section covers some of the issues that an administrator can face when installing and operating the NoPass™ passwordless authentication system.

In case your issue is not discussed here, send your request to support@identite.us.

troubleshooting docker containers

Issue: Docker container status is not "healthy".

Solution:

To check the status of docker containers, run $ sudo docker ps -a (Linux). 

If the containers display a status such as “unhealthy”, “restarting” or “exited”,  there was a problem with the installation.

Logs are available and may give insight into what went wrong with the attempted installation. These logs can be accessed by the command

sudo docker logs <docker container name or ID>.

When troubleshooting, finding an error in the logs will be most helpful if contacting support is needed. 

To restart the docker containers without re-installing NoPass™, run the command

sudo docker-compose down

to shut down the containers, then, run

sudo docker-compose up -d

to restart containers.

 

troubleshooting portal registration

Issue: The portal registration failed. There was an error during storing portalRegistration in DB.

Solution:

The possible reason can be a database connection issue. First, check the following points:

1) Have you registered any portals before?

2) What is the name of the portal that causes the error?

3) Check the NoPass™ server logs in /<script_folder>/logs/nopass_server/, or use the command "$sudo docker logs nopass_server" to check the container logs.

4) Check your database, it should contain the database and tables similar to those on the attached screenshot.

 

troubleshooting nopass server update

Issue: the NoPass user registration fails

Solution:

To solve the NoPass user registration failure, the current NoPass server needs to be updated. To do this, perform the following steps:

1. Navigate to the folder with installation script.

2. To shut down the docker containers, run 

 sudo docker-compose down

3. Modify variables.env by adding MAPD_PushNotificationSettings__FirebaseServerKey 

4. To apply the new values, the docker containers should be rebuild, run

./install.sh

4. At this point, the docker-compose.yml file changes back to default settings. To make changes to the docker-compose.yml file, shut down the docker containers with

sudo docker-compose down 

5. Modify the docker-compose.yml  file by changing the hubdocker.identite.us/nopass-customer:latest  image with  hubdocker.identite.us/nopass-customer:1.1.2 image.

6. Start the docker containers again by running

 sudo docker-compose up -d --build --force-recreate --no-deps nopass 

7. After the docker containers are restarted, the static host names for  both the NoPass server and  nginx server disappear, so you need to modify the hosts.

troubleshooting server reboot

Issue: the web server does not respond after the stack reset or server reboot.

Solution:

It looks like the bridge interface after the network stack reset stops bridging outside and the communication with SQL is broken.

To solve the issue, perform the following:

sysctl net.ipv4.conf.all.forwarding=1

sudo iptables -P FORWARD ACCEPT

 

 

next topic: Glossary

previous topic: Configuration files