I installed CO about 2-3 months ago and I didn’t need to print or convert office documents to PDF.
Today I wanted to print an office document and printing doesn’t work at all.
I’m using Nextcloud 32.0.1 and CO
Printing still doesn’t work. I have no idea where the problem could be
I have CO installed in LXC and integrated into nextcloud.
Everything works except printing (exporting to pdf also doesn’t work).
If I try to print or export to pdf, nothing happens.
I have a similar setup on a completely different server and printing works there without any problems (I installed both servers the same way).
edit:
I forgot to write that if I print a pdf or a regular txt file in nextcloud, everything works (only office documents don’t work).
I also have a reverse proxy server and the configuration there is as follows
Thanks for sharing the config and logs — that’s really helpful!
First, the good news: those lc_validate*.svg “File not found” warnings are harmless (just missing icon lookups), so you can ignore them.
The interesting line is the last one. When you print or export to PDF, Collabora generates the file and gives your browser a one-time download link (/cool/.../download/<id>). Your log shows that request reaching coolwsd but being answered with “Not found” — which usually means the request got duplicated or mangled on the way, so the one-shot link was no longer valid when it arrived. That points at the transport layer, i.e. the reverse proxy.
And the thing that jumps out in your nginx config is the HTTP/3 / QUIC block:
You’re on Chrome (per the log), and Chrome switches the connection to HTTP/3 as soon as it sees that Alt-Svc header. WebSockets and these one-shot download requests don’t always survive that cleanly behind nginx’s h3 proxying — and “everything works except print/PDF export” is exactly the symptom that produces. I’d bet your working server doesn’t have that QUIC block
To confirm:
Comment out listen 443 quic; and the Alt-Svc / x-quic add_header lines, then nginx -t && systemctl reload nginx
Chrome caches Alt-Svc aggressively, so test in a fresh incognito window — or launch Chrome with --disable-quic, or simply try Firefox
Try Print and File → Export as PDF again
Also useful: open DevTools → Network, click Print, and look at the /download/ request — check its status and the Protocol column (h3 vs http/1.1). If it shows h3 and fails, that’s our confirmation.
If it still misbehaves with QUIC disabled, please share a fresh coolwsd log from the same moment and we’ll dig further!
Thanks for the reply
You are right, I do not use HTTP3 on the servers where printing works. However, when I disable HTTP3 on the original server, nextcloud cannot connect to the collaboration server and then it will not even open the office document.