Considering the move from FusionPBX

Voipy

New Member
Feb 5, 2026
5
0
1
56
Hi

We run a cluster of 3 fusion instances with a central DB. We have been very happy with some aspects of the system - it is rock solid, it's incredibly flexible, etc. But the lack of a useable client interface is an issue, as is the performance of certain tasks like running CDRs or call stats. Those simply don't work - it just times out. And the voodoo required for an update scares us off doing so.

I have just installed FSPBX with the intention of moving over eventually once tested. Installation was smooth. Can't (yet) get past the 419 page expired issue at this point but will post that separately -it's not important for testing purposes. I love the look of it. BUT - it seems very slow. Granted I have only given it 4G of RAM for testing but it runs on the exact same server as our other stuff does which all runs fine.

As an example, I have created just one domain. Changing between the admin domain and that one takes 9 seconds on the dot. Is that the expected speed or is something wrong? There is no io delay at all, no load of any kind, just two extensions that are registered.

Any words of wisdom on what this could be - or is that indeed the norm?
 
Hi @Voipy, This is 200% not how it's supposed to be. Even on my dev servers with 4 GB of RAM, it only takes a second.
The upgrades for FS PBX will not require any voodoo going forward. Our clients are able to update production servers in the middle of the day without any fear.

Here is an article on how to bypass the 419 error. The system is very secure, so everything has to match exactly; otherwise, the session cookie will trigger a protection.


Send me a private message, and we can have a quick Zoom call to investigate what's happening on your system if you like. I can also show you around and demonstrate how we improved the system across the board to make it more user-friendly and more production-ready.
 
Glad to report that the speed issue seemed to somehow be a browser problem. I was using Vivaldi - the issue does not happen when using firefox and response times are perfect.

PBXGeek also resolved the 419 page expired issue which looked to be a duplicate entry in the .env file.

All in all - up and running and looking forward to test driving this!