Troubleshooting¶
Resolve Presidio startup, request, redaction, and TLS problems.
The service is not active¶
Fix:
sudo cloud-init status --wait
sudo -iu ubuntu
sudo systemctl is-active sushi-presidio-api.service
sudo journalctl -u sushi-presidio-api.service --no-pager -n 50
Do not recreate the instance identity to force a retry.
HTTP 400¶
Cause: entities is not 1 to 32 distinct recognizer names for the
requested language.
Fix: omit entities to analyze all supported types, or send names the
language supports. Languages documented here are en and es.
The redaction looks incomplete¶
Cause: the score threshold is 0.6, and detection can miss entities or mark extra spans. A successful example is not a guarantee that every entity was removed.
Fix: review entities in the JSON, including start and end offsets,
against the source text. See
Getting started.
The workstation call fails TLS¶
Cause: the client does not trust this instance's server.crt, or port
8443 is not forwarded.
Fix: forward the port and keep certificate verification on. On the
instance, sushi-presidio-api reads the account file for you.
Last updated November 1, 2026 · Suggest an improvement