Debug
Answers what Gotenberg runs: its modules, the versions of Chromium, LibreOffice, lok and litho, and the value of every flag.
GET/debug
Response
JSON: the modules, the engine versions and every flag. It answers 404 until --api-enable-debug-route is on.
The route is off until you set --api-enable-debug-route, and answers 404 before:
curl \
--request GET http://localhost:3000/debug
Response
{
"version": "9.0.0",
"timezone": "UTC",
"architecture": "amd64",
"modules": [
"api",
"chromium",
"libreoffice",
"libreoffice-api",
"pdf",
"webhook"
],
"modules_additional_data": {
"chromium": {
"version": "Chromium …"
},
"libreoffice-api": {
"lok_version": "lok v…",
"version": "LibreOffice …"
},
"pdf": {
"litho_version": "v…"
}
},
"flags": {
"api-body-limit": "",
"api-port": "3000",
"api-timeout": "30s",
"chromium-max-concurrency": "6"
}
}
lok is the library that drives LibreOffice, litho the one that edits PDFs. The answer gives their versions in full, and lists every flag; the example shows four. It reveals your configuration, so keep the route away from the public: with authentication on, it needs credentials like the other routes. Gotenberg doesn't log or trace it, unless --api-disable-debug-route-telemetry is false.