PoC troubleshooting

Every Monopam page answers 404 on the new address.

The address is not registered for the tenant.

Add it with MONOPAM_TENANT_HOSTS=https://host,... (or MONOPAM_PUBLIC_URL) and restart the application.

The gateway is listed as offline.

The gateway cannot reach Monopam, or its API key or URL is wrong.

Check the gateway's Monopam address and API key, and that the gateway can reach the Monopam port.

A session does not open: A task was canceled.

The gateway URL registered in Monopam is not reachable from the application.

Fix the gateway's URL under Gateways so Monopam can reach it.

A container gateway opens no sessions or records nothing.

The recording paths are not set.

Set MONOPAM_GW_CAPTURE_TEMP_PATH and MONOPAM_GW_CAPTURE_VIDEO_PATH on a mounted volume.

Connections fail after setting a vault key on one host.

The key is not the same on the application and every gateway.

Use the same MONOPAM_VAULT_KEY and version everywhere and restart.

SSH connects to port 22 although another port is in the Server field.

The SSH port is set separately.

Use Advanced → Custom SSH Port on the resource.

A request is approved but the user cannot connect.

Approval does not grant access the policies do not allow.

Give the user a Resource Access Policy and a Space Access Policy.

A native database client cannot connect.

The Database Proxy is off, or the engine's port is blocked.

Turn on the proxy on the gateway's Database tab and open the port.