I have been using Ninja v.4.5.13 whitelabeled. I have no desire to upgrade to the Beta version. I’m not great with managing the web server, so I don’t want to need to fix issues with beta software… but we upgraded our webserver to PHP 7.4 and are disappointed to see that Ninja stopped working. Is there a way to get it to work? I would MUCH prefer to just use the current version and not go to the beta.
But in case, I thought I would try to beta.
I am using an AWS EC2 Server running their Amazon Linux AMI2 distro.
I tried installing 5.0.17, the installation instructions are too complicated for me. I’ve spent several hours tonight trying to get it to work, and can’t. I get to the setup screen, but when I click “Test PDF” all I get is “Oops, looks like something isn’t correct!” When I check the logs, I see there is an error saying:
production.INFO: The command “PATH=$PATH:/usr/local/bin NODE_PATH=npm root -g
node ‘/data/www/live/ninja5/vendor/spatie/browsershot/src/…/bin/browser.js’ '{“url”:“https://www.invoiceninja.com”,“action”:“pdf”,“options”:{“path”:”/data/www/live/ninja5/public/test.pdf",“args”:["–no-sandbox"],“viewport”:{“width”:800,“height”:600}}}’" failed.
I have tried to install npm, but I do get errors saying there are required programs not available (filbers and node-sass). Fibers nor Node-SASS are available through yum, so I’m not sure how to do that. NodeJS is installed.
When I go to the old version of Ninja there is no option for migration under the Account Management settings, as the instructions say there should be. I’m unclear from the instructions if I should set up a new database for Ninja5 or if I should connect it to the same database. Does migration copy it from the old database into a new one or should I use the same?
Thanks for any help you can provide.