Some questions about Invoice Ninja x Apache x Flutter

Hi folks!

I recently installed Invoice Ninja with Apache and PHP 8.1.

The default installation use Flutter as frontend, and it is extremely (very extremely) slow.
It takes 1 min to login. Theme letters appear blurry, and some issues like when I add an invoice and an Item, I unable to change Item price.

I dont have much knowledge in nginx, but I use apache by many years.
So, the first question is Invoice Ninja runs better on nginx than apache?
I asked because I found example configuration file for nginx, but nothing for apache.
Invoice Ninja can be improved migrating it to nginx?

Another question. As I had problems in Flutter, I changed Flutter to React version.
And it improved 500%! Very quickly and responsive.
But in React I had some problems. Sometimes, when I add an Invoice, after adding, the next page is blank. I need to refresh the page. Despite this, the invoice was added.
I set APP_DEBUG=“true” in .env, but no log is generated in storage/logs/. No error log in apache.
If you have any suggestion, I would appreciate.

And for last, these two links are broken:

A red triangle appeared in the application, but I can’t see what I should schedule in cronn due to broken links above.

Oh, the Desktop (macOS) and Mobile (iOS) Application for Invoice Ninja worked 100%! No delay, no issues, quickly, fantastic!

Thanks for help! Sorry for so many questions!


The React app is the recommend app to use on web, Flutter is used for desktop/mobile.

If you’re seeing errors in the React app please check the browser console for error details.

Where did you find the doc links? Here’s the correct link:

Hi @hillel
Thanks for your reply!

Do you recommend using nginx instead apache for invoice ninja?

I will look for console errors, thanks.

And about doc link, I found it here: Free Source Available Invoicing, Expenses & Time-Tracking | Invoice Ninja

There is a section: " If you are having troubles with your crons, have a look at the troubleshooting section here"

I don’t think you’ll see in a difference in the app if you use Nginx or Apache.

Thanks for letting us know where the invalid link is, @david is it possible to redirect the broken links or will we need to update the docs?


No problem, its a pleasure.

The errors that appear in the console are basically “tinymce should have been loaded into global scope”. I exported the errors.

console-export-2023-7-1_17-32-45.txt (10.9 KB)

Thanks! @david do you have any suggestions?


The tinymce errors can be ignored, they should not have an impact on the functionality.

It sounds like you have


This would make all of the interfaces block until all backend actions are completed. Both interfaces will respond much faster when using queues to process background tasks


You’ll want to first configure the queues, and then the experience should be much faster and also prevent any timeouts you are seeing with white pages.


Thanks for sugestion. Indeed, the interface is responding faster than before.

But the page remains blank after I add an invoice.
The same occurs occasionally when I try to edit an invoice. I can’t edit, the page is showed blank.
I will do more tests. Perhaps queues work differently on FreeBSD.

@David and @hillel

Well, if this problem is related to queue connection, probably no much can be done in FreeBSD, but I will try other attempts using redis server/jobs.
And this is a small problem that doesn’t affect the functionality too much, as it is enough to refresh the page. And most of the time I’ll be using the desktop or iOS app, where everything works perfectly fine.

Invoice Ninja is fully supported in FreeBSD, with some tweaks/adjustments.

Thanks for your support, and I want to collaborate to community.
I saw that is no section FreeBSD installation on Free Source Available Invoicing, Expenses & Time-Tracking | Invoice Ninja

So, If you want, I can do fully documentation to install and run invoice ninja on FreeBSD. It’s the least I can do.
If it is interesting to you, please let me know. It would be a pleasure to help.

That would be great, thanks!

Perfect, in 1 or 2 weeks I will make a pull request.

I will mark this topic as solved.


1 Like