I can confirm that the same error occurs on a different Windows 11 computer, running locally on localhost:5000.
I can reproduce the issue too. Strangely, this was a known bug in Playwright library which has been fixed. Looking into what can be done about this.
Please try the latest version (25.10.30.3074). I have changed how Chromium is downloaded. The first click on PDF button will take longer because Chromium/Chrome dependency will be downloaded but then it will be fast.
Updated to latest version but still getting error, below is the error code. In the first line if i understand correct it’s trying to open x86_64 but my ubuntu is ARM64
**h1>Internal Error</h1><hr />Manager 25.10.30.3074<hr /><pre>PuppeteerSharp.ProcessException: Failed to launch browser! qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory**
**at PuppeteerSharp.States.ProcessStartingState.StartCoreAsync(LauncherBase p) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/States/ProcessStartingState.cs:line 83**
**at PuppeteerSharp.States.ProcessStartingState.StartCoreAsync(LauncherBase p) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/States/ProcessStartingState.cs:line 89**
**at PuppeteerSharp.Launcher.LaunchAsync(LaunchOptions options) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Launcher.cs:line 77**
**at PuppeteerSharp.Launcher.LaunchAsync(LaunchOptions options) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Launcher.cs:line 110**
**at ManagerServer.HttpHandlers.Pdf.Post() in /home/runner/work/Manager/Manager/ManagerServer/HttpHandlers/Pdf.cs:line 32**
**at ManagerServer.HttpServer.<>c.<<Build>b__0_16>d.MoveNext() in /home/runner/work/Manager/Manager/ManagerServer/HttpServer.cs:line 270**
**--- End of stack trace from previous location ---**
**at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|7_0(Endpoint endpoint, Task requestTask, ILogger logger)**
**at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)**
**at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)**
**at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.<Invoke>g__Awaited|10_0(ExceptionHandlerMiddlewareImpl middleware, HttpContext context, Task task)</pre><p><a href="javascript:window.history.back();”>Go back</a>**
I tested and it works, but not when I run manager server as a service. This is not a big deal for me, I have no issue running the .exe file.
@qinwanhasan OK, it seems the issue is with Google, they don’t provide binaries for Linux arm64.
It’s such a bummer because PDF now works across all editions except for server edition on Linux Arm64.
I am running the server edition in a Synology NAS Container and have the same problem 
Hi a few versions back the PDF and Email buttons were not working on mine they now work logged into the server itself but neither windows or Mac clients work… is this a separate issue or a continuation of the same thing?
Updated to latest version: 25.11.3.3093
No change in behaviour. Same JS error on PDF push and nothing happens on Email push.
Yes a bummer indeed! @Lubos could you kindly tell us what you will do about this so that we can use PDF/Email as intended, thank you.
Are there any solutions yet to make the PDF creator en Email button working again?
Because this is a big pain in the *ss at the moment.
The only way when the PDF creator works is using desktop version (Windows).
The Linux server version (running in a docker) and the Windows server version are both with the same problem that the PDF and Email buttons don’t work.
1 Like
Hi
I see that my Windows version (25.11.6.3097) has issues with this again, neither PDF nor email buttons do anything.
Similar error after upgrading to v 25.11..7.30978. Before I was using v 25.10.23.3022 everything works fine. I am using ServerEdtion on Almalinux9
<h1>Internal Error</h1><hr />Manager 25.11.7.3098<hr /><pre>PuppeteerSharp.ProcessException: Failed to launch browser!
at PuppeteerSharp.States.ProcessStartingState.StartCoreAsync(LauncherBase p) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/States/ProcessStartingState.cs:line 83
at PuppeteerSharp.States.ProcessStartingState.StartCoreAsync(LauncherBase p) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/States/ProcessStartingState.cs:line 89
at PuppeteerSharp.Launcher.LaunchAsync(LaunchOptions options) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Launcher.cs:line 77
at PuppeteerSharp.Launcher.LaunchAsync(LaunchOptions options) in /home/runner/work/puppeteer-sharp/puppeteer-sharp/lib/PuppeteerSharp/Launcher.cs:line 110
at ManagerServer.HttpHandlers.Pdf.Post() in /home/runner/work/Manager/Manager/ManagerServer/HttpHandlers/Pdf.cs:line 32
at ManagerServer.HttpServer.<>c.<<Build>b__0_16>d.MoveNext() in /home/runner/work/Manager/Manager/ManagerServer/HttpServer.cs:line 270
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|7_0(Endpoint endpoint, Task requestTask, ILogger logger)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.<Invoke>g__Awaited|10_0(ExceptionHandlerMiddlewareImpl middleware, HttpContext context, Task task)</pre><p><a href="javascript:window.history.back();">Go back</a>
It seems to be the problem, when you tell the ManagerServer.exe to listen to the IP address and port given in CMD like: (ManagerServer.exe –urls 192.168.1.3:8080). At that point the problem with PDF creator and the email script wont work.
If you run the executable at itself without any commands, then if you surf to your loopback address 127.0.0.1:5000 then the pdf creator works and also the email window works.
So in my opinion the problem relies at the fact that when the program is told to forced ip address then, the mechanism in the PDF creator and the email window won’t work.
So clearly, when you let the program (ManagerServer.exe) loaded by itself, everything works fine.
But when forced to an IP address and/or port then these issues occur.
Anyway If I launch the ManagerServer.exe and its only available at the loopback address, Why is this a server version?
(Offcourse this is not the perception, but let me clear it up)
(Another thing is, if this a license issue, please report, because I would defently pay you for your hard work)