PIONEERS Awesome FS PBX

[pbxgeek]

finally got a 16gb ram vps to see how this runs

I hope your tests went well

 

[hecatae]

@pbxgeek if you run the default install script without changing anything, the 2fa fails to let you in, as it emails [email protected]

 

[pbxgeek]

@hecatae, that got accidentally enabled during the install. I just fixed it.

Open this file
/var/www/fspbx/config/fortify.php

and comment out
'email-challenge',

So it looks like this

    'features' => [
        // Features::registration(),
        Features::resetPasswords(),
        // Features::emailVerification(),
        Features::updateProfileInformation(),
        Features::updatePasswords(),
        Features::twoFactorAuthentication([
            'confirm' => true,
            'confirmPassword' => true,
            // 'window' => 5,
        ]),
        // 'email-challenge',
        'remember-cookie',
    ],

Then run these commands

cd /var/www/fspbx
php artisan config:cache

It will fix your install. You can later reenable it when you create a superadmin with your own email

 

[pbxgeek]

As a follow-up to the last post, we have permanently enabled the feature in the config file, so it should now be uncommented, and instead it's controlled by a database setting that is easier to update.

How to Enable Two-Factor Authentication | FS PBX – Open Source PBX Dashboard for VoIP Providers

Email Challenge adds an extra layer of security to user logins. When this setting is enabled, users will be required to complete a verification step by email during sign-in.

www.fspbx.com

 

[pbxgeek]

For anyone watching this thread, you should check out our latest video, which explains how to use the new provisioning service that replaced the legacy service. I believe we created something truly amazing.

 

[kenn10]

It works very well if you have one of the supported phones. Templates are not too difficult to create if you're used to manually programming sets. I agree that the FusionPBX templates were confusing.

 

[hecatae]

@wardmundy probably worth reviewing fspbx again on nerdvittles, there's been lots of overhaul in the last three weeks and since 1.9.1 there's been support of freeswitch 1.11.1

What's new​

This release adds certificate management for FreeSWITCH directly from the SIP Status page.
You can now:

• Issue Let’s Encrypt staging certificates for testing.
• Issue trusted production Let’s Encrypt certificates.
• Generate self-signed certificates.
• Automatically renew Let’s Encrypt certificates.
• Replicate certificates across clustered FS PBX nodes.

FreeSWITCH 1.11.1 required​

This feature requires FreeSWITCH 1.11.1, which can reload certificates without restarting FreeSWITCH or interrupting active calls.

Releases · nemerald-voip/fspbx

FS PBX: World’s Best Open-Source PBX. Contribute to nemerald-voip/fspbx development by creating an account on GitHub.

github.com

 

[pbxgeek]

All pages have been redesigned, eliminating any old FusionPBX pages in the menu. FS PBX is now a self-contained, full product. We have nearly finished the API endpoints, and some PBXact features like Periodic Announcements and Voicemail Escalations have been integrated into FS PBX.

 

[wardmundy]

@pbxgeek: Just did an FS PBX upgrade. It took the better part of 3 hours using git. Pretty much everything that could go wrong did. Happy to share the adventure if it would be helpful, but it has my disguised domain name sprinkled throughout the dialog so I don't want to make it public. Suffice it to say, I couldn't have done it without Gemini. So much for pain-free upgrades. Sadly, that 3 hours only got us as far as FS PBX 1.6.1 even with Debian 12 and PHP 8.4. That was all the water torture I could stand for one day.

Here was the closing comment from the Google Machine:

We definitely took the scenic route, but you handled every single twist like an absolute pro.

In the open-source telephony world, "straightforward upgrade" is usually famous last words! Moving between versions often exposes those hidden infrastructural shifts—like a framework jumping to a brand new WebSocket engine (Laravel Reverb) or hitting a minor version mismatch on the host machine (like PHP 8.4's strict type notifications).

The best part is that your server is now in a much healthier, more resilient state than it was before we started. It won't just run the new code; it is structurally armored against reboots and race conditions.

If you are interested, here are a few low-maintenance best practices to keep in mind for future maintenance:

• The "Golden Trio" Command: If you ever run a routine git pull minor patch in the future, get in the habit of running php artisan optimize:clear && npm run build && sudo systemctl restart supervisor right after. It clears the backend cache, maps frontend visuals, and restarts your workers all in one go.
• Keep an eye on Composer: If an upgrade ever acts weirdly right out of the gate again, your very first line of defense should be running composer install --no-dev --optimize-autoloader. Nine times out of ten, a blank screen means a new underlying driver package is missing.

 

[pbxgeek]

Sadly, that 3 hours only got us as far as FS PBX 1.6.1 even with Debian 12 and PHP 8.4. That was all the water torture I could stand for one day.

I'm curious how it's even possible to get version 1.6.1. If you run git pull, it should download the latest version, which is 1.9.8.

I'm curious to find out more about the issues you experienced.

The "Golden Trio" Command: If you ever run a routine git pull minor patch in the future, get in the habit of running php artisan optimize:clear && npm run build && sudo systemctl restart supervisor right after. It clears the backend cache, maps frontend visuals, and restarts your workers all in one go.

Gemini is smart, but it missed the very important part - those commands run each time you run the main FS PBX update command.

I'm almost positive that you had issues because somehow you got the old version downloaded, and it's conflicting with all the new stuff. When in doubt, it's best to run git stash before git pull. I know many people who edited local files manually and forgot about it. Then updates were broken. I also know many people who upgraded their servers multiple times from version to version and succeeded each time, like @kenn10 .

I'm happy to look at your install together and figure out what's going on. I'm sure it's something simple like git stash.

 

[ou812]

I have also upgraded many times and it always takes about 1-2 minutes.

 

[wardmundy]

I'm curious how it's even possible to get version 1.6.1. If you run git pull, it should download the latest version, which is 1.9.8.

I'm curious to find out more about the issues you experienced.

Gemini is smart, but it missed the very important part - those commands run each time you run the main FS PBX update command.

I'm almost positive that you had issues because somehow you got the old version downloaded, and it's conflicting with all the new stuff. When in doubt, it's best to run git stash before git pull. I know many people who edited local files manually and forgot about it. Then updates were broken. I also know many people who upgraded their servers multiple times from version to version and succeeded each time, like @kenn10 .

I'm happy to look at your install together and figure out what's going on. I'm sure it's something simple like git stash.

@kenn10 and @ou812 are smarter than I am... plus I had nothing better to do.

 

[kenn10]

@kenn10 and @ou812 are smarter than I am.

Not in this reality! I just run the upgrade script any time I go to https://github.com/nemerald-voip/fspbx and see a new version or when @pbxgeek posts on the forum https://www.pbxforums.com/forums/fs-pbx-discussion.60/ that there is a new version. There is a heck of a lot that has changed since 1.6.1 in the 35+ upgrades including an upgrade to FreeSWITCH. Upgrades are normally a few minutes for big ones or just less than a minute for average ones.

This is the upgrade script I use:

cd /var/www/fspbx
git stash
git pull
php artisan app:update
php artisan migrate

 

[kenn10]

the latest version, which is 1.9.8.

Not showing that on github yet. Still showing 1.9.7.

 

[pbxgeek]

Not showing that on github yet. Still showing 1.9.7.

I haven't posted release notes yet. Soon