View Invoice as a "PDF" hanging

I thought this was just my installation but when i visited the demo.invoiceninja.com to view an invoice there i got the same result. The loading icon just keeps spinning and nothing happens. Is there something i’m missing here??

Are there any errors in the logs in storage/logs

I sent you a picture of “demo.invoiceninja.com” I can’t see your logs. But its doing the same on my site as it is on yours!!

Can you see this?:

If you’re able to send details from your error logs it would be helpful.

The demo server is a strange setup as we constantly refresh the database, it’s unclear if it’s the same problem.

Error Output:

================
Error: Failed to launch chrome!
[0723/015132.111360:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x564749872879 base::debug::CollectStackTrace()
#1 0x5647497cfc63 base::debug::StackTrace::StackTrace()
#2 0x5647497e4013 logging::LogMessage::~LogMessage()
#3 0x56474af7e95e service_manager::ZygoteHostImpl::Init()
#4 0x564749413adc content::ContentMainRunnerImpl::Initialize()
#5 0x56474945f72c service_manager::Main()
#6 0x5647494120b1 content::ContentMain()
#7 0x56474945e99d headless::(anonymous namespace)::RunContentMain()
#8 0x56474945e70b headless::HeadlessShellMain()
#9 0x5647471ef1b8 ChromeMain
#10 0x2ab110c76555 __libc_start_main
#11 0x5647471ef02a _start

Received signal 6
#0 0x564749872879 base::debug::CollectStackTrace()
#1 0x5647497cfc63 base::debug::StackTrace::StackTrace()
#2 0x564749872401 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x2ab10ac88630
#4 0x2ab110c8a387 __GI_raise
#5 0x2ab110c8ba78 __GI_abort
#6 0x564749871265 base::debug::BreakDebugger()
#7 0x5647497e4461 logging::LogMessage::~LogMessage()
#8 0x56474af7e95e service_manager::ZygoteHostImpl::Init()
#9 0x564749413adc content::ContentMainRunnerImpl::Initialize()
#10 0x56474945f72c service_manager::Main()
#11 0x5647494120b1 content::ContentMain()
#12 0x56474945e99d headless::(anonymous namespace)::RunContentMain()
#13 0x56474945e70b headless::HeadlessShellMain()
#14 0x5647471ef1b8 ChromeMain
#15 0x2ab110c76555 __libc_start_main
#16 0x5647471ef02a _start
r8: 0000000000000000 r9: 0000000000000000 r10: 0000000000000008 r11: 0000000000000202
r12: 00007ffc1eb028c8 r13: 00007ffc1eb018a8 r14: 00007ffc1eb018a8 r15: 00007ffc1eb018c0
di: 0000000000000451 si: 0000000000000451 bp: 00007ffc1eb01850 bx: 00002ab11101c868
dx: 0000000000000006 ax: 0000000000000000 cx: ffffffffffffffff sp: 00007ffc1eb01718
ip: 00002ab110c8a387 efl: 0000000000000202 cgf: 0000000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Did you see the responses here:

Yes, did you see the last post by Zeeshan?

@greaseduck

Did you try Zeeshans solution (assuming you are using CentOS) ? I don’t have a CentOS environment to see whether this does work.

Zeeshan did not have a solution, he asked a question that he’s still waiting a reply to!

Puppeteer has lots of issues with SELINUX. You could set it to permissive and allow puppeteer to generate its requests after doing a few things you can search and add those policies and re-enforce.

I have updated instructions here that should guide you through setup without those errors.

One of the worthwhile comments to note are chrom(e/ium)s dependencies:

sudo yum install libXcomposite libXcursor libXdamage libXext libXi libXtst libmng libXScrnSaver libXrandr libXv alsa-lib cairo pango atk at-spi2-atk gtk3

Do that, and set SELINUX permissive and you should be able to run it.