Server Edition - PDF/Email Issues

81

Got it fixed here also.

For Unraid docker use following instructions:

1 Get inside your docker console:
docker exec -it MANAGER-DOCKER-NAME bash

2 Update & install chromium:
apt-get update
apt-get install -y chromium || apt-get install -y chromium-browser

3 Search for the right chromium which is installed:
which chromium || which chromium-browser

4:
cat << ‘EOF’ > /usr/local/bin/manager-chrome-wrapper
#!/bin/bash
exec /usr/bin/chromium --no-sandbox --disable-gpu --headless “$@”
EOF

chmod +x /usr/local/bin/manager-chrome-wrapper

5 Look for PUPPETEER:
env | grep PUPPETEER

6:
Go in Unraid UI → Docker → your docker container → Edit

Below the page: Add another Path, Port, Variable, Label → Variable

Name: PUPPETEER_EXECUTABLE_PATH

Key: PUPPETEER_EXECUTABLE_PATH

Value: /usr/local/bin/manager-chrome-wrapper

Apply (container restart)

Again check in the container if you can find PUPPETEER:

env | grep PUPPETEER_EXECUTABLE_PATH

Response should be:
PUPPETEER_EXECUTABLE_PATH=/usr/local/bin/manager-chrome-wrapper

7 Check if Chrome is working inside the docker:
Enter in the console inside the container:

manager-chrome-wrapper --dump-dom https://example.com

If you get this HTML response back → :tada: Chromium works through the wrapper.

8:
If using HTTP instead of HTTPS make sure you mark your IP address as secure for HTTP.
Otherwise your browser will block the API.

Fill this in your browser you are using:
Brave: brave://flags/#unsafely-treat-insecure-origin-as-secure
Chrome: chrome://flags/#unsafely-treat-insecure-origin-as-secure
Edge: edge://flags/#unsafely-treat-insecure-origin-as-secure

Look for the flag “Insecure origins treated as secure”.
Set this option to enabled.
In the text field add your IP or URL, something like this:
HTTP://192.168.1.105:8080 and/or HTTP://yourdomain.com/manager/
Then relaunch your browser as stated below in your screen.

9:
If you get error message missing chrome headless shell, then apply following commands in your console in your docker.

If not in your docker console yet:
docker exec -it MANAGER-DOCKER-NAME bash

10:
apt-get update
apt-get install -y wget unzip

11:
unzip chrome-headless-shell-linux64.zip
mkdir -p /root/.cache/puppeteer/chrome-headless-shell/linux-138.0.7204.101/
mv chrome-headless-shell-linux64 /root/.cache/puppeteer/chrome-headless-shell/linux-138.0.7204.101/

12 Last check:
If your moving has done correctly you can check it with this command:
ls -l /root/.cache/puppeteer/chrome-headless-shell/linux-138.0.7204.101/chrome-headless-shell-linux64

If it repeats back with the files in that folder you are good to go.

Now check if the PDF creator and the Email button works. It should be working.

Took me some time to figure out but I managed to get it fixed.

If you want to use HTTPS instead of making an exception in your browser you should be using Nginx reverse proxy server.

Good luck!

Sincerely,

Dreammert

83

I’m still hoping for an official update from @lubos

Manager Server Edition: 26.1.11.3168

—
Apologies I noticed the chrome flag had been reset on all machines:

Additional info:
When logging into manager via localhost:port - works
When logging into manager via intranet address - intra.local:port - works if insecure origins flag + url is set

all urls added using the -url parameter with ; separator

So in short (for our Windows Server AD Environment):

  1. Chrome #Insecure origins treated as secure enabled
  2. Add comma separated list of local urls including ports
  3. Ensure those binds are set using –url when starting managerserver.exe
  4. Clear cache just in case

Seems to be a workaround currently.

85

Somewhat disturbed. We updated Ubuntu Server version from 25.10. x.x where everything worked to 26.3.12.3199 Latest version. Now no PDF, no Printing & no Email operational. All three items fail with the error below. Tested with Firefox, Chrome and Chromium Browsers, all no joy from Ubuntu desktop. Tested with Windows Desktop using Edge Browser also with the same result.
Please advise what is going on now “dead in the water”.

image
image2546×358 58 KB

86

@compuit try the latest version (26.3.13). I have added required parameter.

87

OK Downloaded and installed 26.3.13.3202 OK. Using Firefox, Chromium and Chrome on Ubuntu workstations connecting to manager Ubuntu Server version Email, Printing and PDF all Function OK. Now on Windows using Edge there was a small issue with site permissions in the browser for PDF - Turned off “Always download PDF Files” then all worked as well when email, printing and PDF are invoked. Thank you, excellent :pray:

88

How can I get the latest version (26.3.13) in docker? I can only get version 26.1.21.3171.

90

I asked claude and it suggested me this solution and it worked for me

Fix (Linux — running as root via systemd)

This is the solution that worked for multiple users on Debian/Ubuntu x64, as documented in the thread.

Step 1 — Install Chromium’s system dependencies

You don’t need to install Chrome itself — PuppeteerSharp downloads its own Chrome binary. What you need are the system libraries Chrome depends on: manager

bash

apt-get install -y \
  libglib2.0-0 libnss3 libnspr4 libatk1.0-0 libatk-bridge2.0-0 \
  libcups2 libdrm2 libdbus-1-3 libxcb1 libxkbcommon0 libx11-6 \
  libxcomposite1 libxdamage1 libxext6 libxfixes3 libxrandr2 \
  libgbm1 libpango-1.0-0 libcairo2 libasound2 libatspi2.0-0 \
  libwayland-client0 fonts-liberation

Step 2 — Find the PuppeteerSharp auto-downloaded Chrome binary

After Manager has been run at least once, the binary will be somewhere like:

~/.local/share/PuppeteerSharp/Chrome/Linux-<version>/chrome-linux64/chrome

You can find it with:

bash

find / -name "chrome" -path "*/PuppeteerSharp/*" 2>/dev/null

Step 3 — Create a wrapper script

bash

vim /usr/local/bin/manager-chrome-wrapper

Paste this (update the path to match what you found in Step 2):

bash

#!/bin/bash
exec /root/.local/share/PuppeteerSharp/Chrome/Linux-138.0.7204.101/chrome-linux64/chrome \
  --no-sandbox --disable-setuid-sandbox --disable-gpu --headless "$@"

Make it executable:

bash

chmod +x /usr/local/bin/manager-chrome-wrapper

Test it:

bash

/usr/local/bin/manager-chrome-wrapper --dump-dom https://example.com

Step 4 — Update your systemd service

bash

vim /etc/systemd/system/manager-server.service

Add the Environment line before ExecStart:

ini

[Service]
Environment="PUPPETEER_EXECUTABLE_PATH=/usr/local/bin/manager-chrome-wrapper"
ExecStart=/usr/share/manager-server/ManagerServer -port 5000
Restart=always

Step 5 — Reload and restart

bash

systemctl daemon-reload
systemctl restart manager-server

Additional requirement: HTTPS

The PDF generator uses the JavaScript function crypto.subtle.digest, which browsers only allow in a “Secure Context.” Browsers automatically treat localhost as secure, but when clients access the server via an IP address over HTTP, the browser blocks the PDF script from running. manager

So if PDF works on the server itself but not from other machines, you need either:

  • A reverse proxy (nginx/Caddy) with an SSL certificate, or

  • On each client browser: go to chrome://flags/#unsafely-treat-insecure-origin-as-secure, add your server’s URL (e.g. http://192.168.x.x:5000), and relaunch.

91

I can see that most of the solutions are users trying to make a workaround fix.

Why is there no official fix provided by @lubos regarding this issue to shorten the errors that may occur for users, especially for non-tech individuals like me?

Or the issue is not related to manager !

92

Using server edition version 26.4.18.3405, on a UBUNTU 24.04.3 LTS>

The PDF and Email function has not been working for ever. You press the buttons and nothing happens. These 2 features were great. But no longer working.

Any work around. I have reported this 4 months ago, but it is not fixed yet.

image

93

Refer this topic for some workarounds

94

In the latest version (26.5.11.3580), Manager will try to use locally installed Chromium-based browser so this should resolve issue on ARM64 Linux servers.

Here are the paths Manager will probe:

  • /usr/bin/google-chrome
  • /usr/bin/google-chrome-stable
  • /usr/bin/chromium
  • /usr/bin/chromium-browser
  • /usr/bin/microsoft-edge
  • /usr/bin/microsoft-edge-stable
  • /snap/bin/chromium
  • /opt/google/chrome/chrome
  • /opt/microsoft/msedge/msedge

So please try PDF function on ARM64 Linux again and see if the issue is resolved.

95

@lubos iam also unable to produce PDF if i access my server via ip address or localhost directly. if i access through designated domain address then i can produce pdf using Windows

96

@lubos I have discovered something very interesting in relation to this matter. Because of all the issues with the PDF button and Emails in the latest Manager Server version/s (along with the inability to delete history records; thereby making “cloning” of a business virtually impossible), I have continued trialing Manager V25.10.4.2873.

With V25.10.4.2873, EVERYTHING was working well until early June 2026. I changed NOTHING on the Server, so operating System; security updates; browser etc remained consistent throughout my tests.

What I found is that the issue/s (at least in my case) are related to the DATE. If I set the date on the server to ANY date prior to early June 2026, the PDF Button and Emails etc work perfectly. If I then change the date to (say) today, those functions cease working.

I have tested and retested the above and the problem can easily be replicated.

I know that others may be trying to solve the issue/s with the latest version, but the issues with PDF/Email being affected by the Server date (when NOTHING else has changed) is certainly worth noting. That said, is there any solution that can be proposed (other than fixing the date to an incorrect past date)?

97

An incredible finding, well done. This must have been driven by sheer frustration. Thank you for showing the devs another possible avenue for consideration. :+1:

98

Has this issue been resolved? version 26.6.17.3647 still has PDF/EMAIL not working.