Troubleshooting Common Issues

Start here when something is not working. Find your symptom in the table and
follow the article that covers it. The few issues with no article of their own
are written out further down this page.

If none of this resolves the problem, raise a request — see Getting Help.

Find your symptom

Symptom	Where to go
Teleport shows "No Resources Found" after access was approved	Teleport Shows No Resources After Access Is Approved
Teleport on Windows fails with "expected PEM encoded private key"	Teleport Login Fails With a PEM Private Key Error
A resource in SVIEW denies access even though your role should allow it	Access Requests
The available access durations are too short	Access Requests
A pod is restarting repeatedly (`CrashLoopBackOff`)	Pod Keeps Restarting (CrashLoopBackOff)
A pod was killed with `OOMKilled`	Pod Killed with OOMKilled
A pod restarted with no change on your side	Pod Restarted During Node Maintenance
Your URL returns 503, does not resolve, or shows a certificate warning	Troubleshooting
A secret is not reaching your application	Application Dependencies
You cannot find logs or metrics for a workload	Observability
Your database connection fails or is refused	Attach to Your Application
Login to SVIEW fails	See below
A deployment fails with "Token revoked" or "Forbidden"	See below
An image cannot be pulled (`ErrImagePull`, `ImagePullBackOff`)	See below
An IAM role is not created because the OIDC issuer is missing	See below

Cannot log in to SVIEW with GitLab SSO

If your organisation uses GitLab as its SSO provider, access to SVIEW is granted
through GitLab group membership. If the expected group no longer exists — it may
have been deleted because it looked unused — or you are not a member of it,
login fails.

Re-create the group in GitLab if it was removed.
Add the affected users to the group.
Retry logging in to SVIEW.

Deployment fails with "token revoked" or "forbidden"

ERROR Deployment failed : {"Error":"Token revoked: subj:static-pipelines","Message":"Forbidden"}

The token your CI/CD pipeline uses to publish to SVIEW was revoked, rotated, or
has expired.

Re-issue the token if it has expired, and update the secret your pipeline
uses.
Confirm the token name you are using is still permitted. If it was renamed,
update your pipeline configuration to match.

Image pull failures

ErrImagePull, ImagePullBackOff, or repository does not exist all mean the
image named in your Component's configuration cannot be found or cannot be
accessed.

Check the image name and tag are spelled correctly.
Use a specific tag such as :v1.0.0 rather than :latest.
Try pulling the image from your own machine. If that fails too, the image is
not in the registry or your credentials do not allow pulling it.
Correct the image path or tag in the Component's configuration and save.

IAM role not created — missing OIDC issuer

On AWS, this happens when terraform.outputs.platform.oidc_issuer_url is not
set in the Environment's Global variables.

Copy the full OIDC issuer URL from your EKS cluster's configuration in the
AWS console.
In SVIEW, open Global variables, select the affected stage and
Environment, and set terraform.outputs.platform.oidc_issuer_url to that
value.
Save, then retry the operation that needed the IAM role.

Checking deployment logs

For most issues, the logs are the fastest first step.

In the SVIEW sidebar, click Deployments.
Find the deployment and click View Logs.

Logs are available for cluster resources managed through SVIEW. See
Observability for the full picture of logs and metrics.

Still having issues?

Raise a request with the Environment, the Component name, and the exact error
message. See Getting Help.