I've got papercut setup with a LE cert, no issues there. The problem I am trying to overcome is the Canon Multi Function Devices (Copiers and Printers) always prompt on the device for the certificate to be re-trusted everytime the cert is renewed.
I have updated the Papercut MEAP+ software on all the devices to v1.34, but there is no concrete answer I can get. I have been advised it will automatically trust papercuts own self-signed certificate (but that won't suit us)
Sounds like you need to add the Let's Encrypt root(s) to the Canon MFDs. Or, your Papercut service is not sending out the "fullchain" of certificates. Or both.
The TLS Client (the MFDs in this case) see the cert chain the TLS Server sent. The client uses the cert and chain to link to an existing trusted root installed in their trust store. I am not sure but I think the Canon may call it "Register CA Certificate". You should install the ISRG Root X1 or just the ISRG Root X2 for ECDSA certs. See: Chains of Trust - Let's Encrypt
Do NOT install any Let's Encrypt Intermediates there. Just the roots.
However, if your Papercut is not sending the full chain and instead sending just the leaf that makes it difficult for TLS Clients to link it to a trusted root. If this is happening you should change papercut to send the fullchain and you may also need to add a Let's Encrypt root to the MFDs (maybe not if they already have them I don't know).
Sorry I should have clarified, on every renewal, the Canon MFDs want to re-trust the certificate hash, not the actual certificate per say. Supposedly the MFDs will auto accept the self-signed cert papercut will use, but so far I've had no luck with getting it auto-accepted.
I'll look into the Canon trust store if I can and see what I can find.
If that's true I don't know how you can avoid re-trusting it at every renewal. That will change each time. Using a long-lived self-signed cert retains the same hash which is probably why they suggest that.
You might be better off asking about this on the papercut support channels. I assume it's their client running on your MFD that needs this. Let's Encrypt, or any web pki cert isn't well-suited for this purpose.