---
title: "Troubleshooting"
slug: "s3suite94-deploy-install-usingkubernetes-troubleshooting"
updated: 2026-10-27T18:42:16Z
published: 2026-10-27T18:42:16Z
canonical: "docs.onespan.com/s3suite94-deploy-install-usingkubernetes-troubleshooting"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onespan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

## Unable to Register a Passkey

When running the Nok Nok Tutorial Web App and attempting to register a passkey, the app displays the following error message: “Something went wrong. Please try again.”

The configuration of Port 443 was not successful. Follow the instructions in [Step 6. Configure your environment to use port 443](/dpoa/docs/s3suite94-deploy-install-usingkubernetes-install-the-nok-nok-s3-suite#step-6-configure-your-environment-to-use-port-443)

## Out of Memory

If the WSL2 VM instance requires more memory, you can create or edit the .wslconfig file under the powershell home directory:

```plaintext
cd
notepad .wslconfig
```

Here is an example of how to configure the CPUs and memory in the .wslconfig file:

```plaintext
[wsl2]
memory=8GB
processors=max
```

Note that you need to shutdown the WSL2 VM instances and restart WSL2 for this change to take effect. After restarting, use the top command to confirm that your change has taken effect.

## Invalid Reference Format

To run a command that continues on a second line of the terminal, remove all spaces after the backslash on the first line.

## API Server Access

*When you run this command on the* ***CDT Host System*** *terminal:*

```plaintext
kubectl get ns
```

*You get this output:*

```plaintext
couldn’t get current server API group list: Get "https://127.0.0.1:32769/api?timeout=32s": dial tcp 127.0.0.1:32769: connect: connection refused
```

*Resolution:*

```plaintext
Ensure that Kubernetes is up and running. On MacOS, confirm that the Rancher Desktop is running with Kubernetes enabled. On Linux systems, check minikube status by running minikube status. If minikube is not running, start it with the command minikube start.
```

## Private Container Registry Access

*When you run this command* on the **CDT Host System** terminal:

```plaintext
curl -v https://nns3-registry.noknokeval.com:50443/v2/_catalog
```

*You get this output:*

```plaintext
Trying 192.168.1.135:50443…
Connected to nns3-registry.noknokeval.com (192.168.1.135) port 50443 (#0)
ALPN: offers h2,http/1.1
(304) (OUT), TLS handshake, Client hello (1):
LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to nns3-
registry.noknokeval.com:50443
Closing connection 0
```

*Resolution:*

Check if the private image registry is running.

```plaintext
cd ${NN_CDT_HOME}/registry
docker compose ps
```

If the registry docker container is not shown in running state, run the following command to

start it:

```plaintext
cd ${NN_CDT_HOME}
helm/bin/start_private_registry.sh
```

If the registry is running, check if the IP address in the hosts file is correct and change it if needed.

## Browser Cannot Resolve Host

*When you run this command* on the **Browser Client System** terminal:

```plaintext
ping nns3-admin.noknokeval.com
```

*You get this output:*

```plaintext
ping: cannot resolve nns3-admin.noknokeval.com: Unknown host
```

*Resolution:*

Check hosts DNS entry and correct the IP address used. Use ping to verify that the name resolution works.

## Browser Connection Error

*When you run this command* on the **Browser Client Systemterminal**:

```plaintext
curl -v https://nns3-admin.noknokeval.com:8443/nnladmin
```

*You get this output:*

```plaintext
Trying 157.143.123.2:8443…
Connected to nns3-admin.noknokeval.com (157.143.143.2) port 8443 (#0)
ALPN: offers h2,http/1.1
(304) (OUT), TLS handshake, Client hello (1):
LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to nns3-admin.noknokeval.com:8443
Closing connection 0
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to nns3-admin.noknokeval.com:8443
```

*Resolution:*

Check if port forwarding from the host system to the Kubernetes Ingress Controller Service is running.