I just wanted to report, after my Cloudron updated IN to 1.6.46 the PDF generation was completely hosed, basically. It wouldn’t load at all on the invoice preview, when I would click “View PDF” if it had been generated before it would load there, if it hadn’t it either wouldn’t load or had the improper colors and formatting.
The solution for me was to roll back to a saved backup of 1.6.45 and everything is happy once again.
EDIT: Oops, in non-cloudron speak this was going from v5.5.49 to v5.5.50, and then back again.
That’s actually not present in the env file. I don’t know if cloudron is setting the variable somewhere else, or if it “just works” without that set and is part of the issue when it upgrades (doesn’t work unset on 5.5.50).
I did some more testing on all of these things. Yes, new Cloudron installs add the DISABLE_AUTO_UPDATE=true to the env file, and it works great. But also, there was an update released for the ones previously installed! I had already added it to my installation manually, so I’m guessing there is a check before it adds to the env file because it didn’t change (or duplicate within) mine, but you can see the update dialog for the change here:
Finally, I couldn’t get self hosted pdf generation on 5.5.50 to work even when adding PDF_GENERATOR=snappdf to my env file within the Cloudron environment (this didn’t appear to change anything anyway, according to the Health check in the about dialog), but PDF_GENERATOR=hosted_ninja works perfectly so I will leave that for now.
Could the PDF_GENERATOR be affected by the PHP memory limit? Everything works well, however my Cloudron is only providing 307MB according to the health check, of course noting that it doesn’t reach the recommended 512MB for in-app/non-Cloudron updates.
Snappdf worked great on the last version 5.5.49 with the same setup. I guess it could just be a Cloudron thing as well (though I do love Cloudron for this app for the ease of automating updates and backups).