PDF export broken on dillinger.io - "Could not find Chrome (ver. 142.0.7444.175)"

[ManuzimFerreira]

Bug Description

PDF export on the production site (dillinger.io) is broken.

Steps to Reproduce

1. Go to https://dillinger.io
2. Write any markdown content
3. Click Export As → PDF
4. Navigate to /factory/fetch_pdf

Expected Behavior

PDF should download successfully.

Actual Behavior

Raw error displayed:

Could not find Chrome (ver. 142.0.7444.175). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
 2. your cache path is incorrectly configured (which is: /home/sbx_user1051/.cache/puppeteer).

Environment

• Production site: dillinger.io
• The path /home/sbx_user1051/ suggests a sandboxed cloud environment

Suggested Fix

The recent Dockerfile fix (commit 24f352c) adds proper Chromium installation and sets PUPPETEER_EXECUTABLE_PATH. This fix may need to be deployed to production, or the production environment may need Chrome installed separately with proper path configuration.

[joemccann]

LIkely has to do with how Vercel doesn't allow Puppeteer

…

On Thu, Jan 22, 2026 at 8:00 AM Emanuel Furtado ***@***.***> wrote: *ManuzimFerreira* created an issue (joemccann/dillinger#885) <#885> Bug Description PDF export on the production site (dillinger.io) is completely broken. Steps to Reproduce 1. Go to https://dillinger.io 2. Write any markdown content 3. Click Export As → PDF 4. Navigate to /factory/fetch_pdf Expected Behavior PDF should download successfully. Actual Behavior Raw error displayed: Could not find Chrome (ver. 142.0.7444.175). This can occur if either 1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or 2. your cache path is incorrectly configured (which is: /home/sbx_user1051/.cache/puppeteer). Environment - Production site: dillinger.io - The path /home/sbx_user1051/ suggests a sandboxed cloud environment Suggested Fix The recent Dockerfile fix (commit 24f352c <24f352c>) adds proper Chromium installation and sets PUPPETEER_EXECUTABLE_PATH. This fix may need to be deployed to production, or the production environment may need Chrome installed separately with proper path configuration. — Reply to this email directly, view it on GitHub <#885>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALY2VS2PTWUKFVOU2XLLD4IDX2RAVCNFSM6AAAAACSR2KMBCVHI2DSMVQWIX3LMV43ASLTON2WKOZTHA2DGNJZGM3DCNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>