Not creating pdfs after updates

[AartJansen]

@humptydumpty No they look the same with either generated for me. (thankfully)

[AartJansen]

Now my workaround doesn't work either, the invoices are unreadable/blank for mail recipients.

[jdaviescoates]

@humptydumpty said in Not creating pdfs after updates:

Nodebb doesn't have a male facepalm icon so it tossed a female facepalm and the male symbol

this happens me when using emojis on mobile but I eventually worked out you can then edit your post and delete the extra symbol

[jdaviescoates]

@humptydumpty said in Not creating pdfs after updates:

@girish I checked my PDF's (I send a copy to myself) and it started with 5.11.11. I'm not sure what they're doing upstream, but PDF issues keep recurring every few updates

See, I just quoted your post with the extra symbol then deleted it and it change to the above

[humptydumpty]

This post is deleted!

[girish]

@AartJansen are you using the latest package 1.16.0 ? The package has now switched to google chrome stable like upstream. Can you check if a fresh installation works for you?

[humptydumpty]

I'm on 1.16.0 (upgraded existing app) and PDFs weren't generating for me which in turn causes invoice emails not to send. I changed false to true in the .env file and it's all working now. PHANTOMJS_PDF_GENERATION=true

Do existing apps upgrade properly to the new Chrome thing or should I go with a fresh install? If so, does the normal backup restore/import work in this case or should I use the built-in app's export/import function?

[girish]

@humptydumpty it should be like below and atleast for new packages it works

PDF_GENERATOR=snappdf
SNAPPDF_CHROMIUM_PATH=/usr/bin/google-chrome-stable

[humptydumpty]

I'll give those a try soon. Thanks!

[humptydumpty]

@girish I compared my existing .env file to fresh install to see what else has changed and noticed a few things:

In my existing env file, there was a double entry of this section:

DB_HOST=mysql
DB_DATABASE=blablabla
DB_USERNAME=blablabla
DB_PASSWORD=blablabla
DB_PORT=3306

Then, we have:

Existing env DB_CONNECTION=db-ninja-01
Fresh env DB_CONNECTION=mysql

Existing env TRUSTED_PROXIES=
Fresh env TRUSTED_PROXIES=*

Lastly, we have a few additions that didn't exist before, such as:

PHANTOMJS_KEY='a-demo-key-with-low-quota-per-ip-address'
PHANTOMJS_SECRET=secret

DELETE_PDF_DAYS=60
DELETE_BACKUP_DAYS=60

GOOGLE_PLAY_PACKAGE_NAME=
APPSTORE_PASSWORD=

MICROSOFT_CLIENT_ID=
MICROSOFT_CLIENT_SECRET=
MICROSOFT_REDIRECT_URI=

APPLE_CLIENT_ID=
APPLE_CLIENT_SECRET=
APPLE_REDIRECT_URI=

NORDIGEN_SECRET_ID=
NORDIGEN_SECRET_KEY=

# https://invoiceninja.github.io/en/self-host-installation/#supervisor-for-invoice-ninja-ubuntu-22-04-lts

I hope copy/pasting these new additions won't mess anything up in the database.

[girish]

@humptydumpty yes, the fresh variables are correct. The PHANTOMJS_* should not be required afaik

[AartJansen]

@girish Yes I have 1.1.6.0... but I don't have those lines in the env file. I'll try just add them manually, before I do a reinstall.

EDIT: Manually adding those lines to the env file has fixed it for me.

[girish]

@AartJansen thanks for testing! There's too many releases of IN by now, so it's hard to track down where it went wrong...

[fanvyr]

i'm running 6 instances of invoice ninja with cloudron, each setup at a different time (well, over time more..)
i had problems with ALL, created before a specific time (don't know when right now).
But yeah, changing the phantomjs var from false to true solved it for me. Weirdly enough, the DB vars are double in the configs... why?
Thinking about setting up fresh instances and export/import all the clients... man....
But thanks for the advices here. (don't get the emoji ones, but at least we're having fun while noone appreciate our work )
have a good one!

[humptydumpty]

@fanvyr no need to go through import/export of the app. Simply delete the phantomjs line and paste the two lines Girish posted above. That’s the updated env. I also had the double db in there. It’s safe to delete the duplicates.