# Prisma Cloud Compute self-hosted API uses self-signed certs, so curl fails validation by default

## TL;DR

When hitting a self-hosted Prisma Cloud Compute Console API (port 8083) with curl, either pass --insecure (the connection stays encrypted, you just skip identity validation) or configure Prisma Cloud Compute to use your own custom certs. Context: Official docs (pan.dev, Access the Prisma Cloud Compute Edition APIs): documents the TLS gotcha that trips agents scripting the self-hosted Compute API. The default Prisma Cloud Compute install uses self-signed certificates, and curl validates the server cert by default, so API calls fail certificate validation even though the address and credentials are right.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

Tool: Prisma. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

Context: Official docs (pan.dev, Access the Prisma Cloud Compute Edition APIs): documents the TLS gotcha that trips agents scripting the self-hosted Compute API. The default Prisma Cloud Compute install uses self-signed certificates, and curl validates the server cert by default, so API calls fail certificate validation even though the address and credentials are right.