SOLVED Missing Login Button or Login Does Nothing

Yes I did but no luck. Still can not log into the Web GUI. I am running 2027-D when I look at the versions they are mostly 16.
IncrediblePBX is 17.0.3 is that OK? see attached txt file.
Thanks
 

Attachments

Yes I did but no luck. Still can not log into the Web GUI. I am running 2027-D when I look at the versions they are mostly 16.
IncrediblePBX is 17.0.3 is that OK? see attached txt file.
Thanks
You don't have the current version of framework or core. That may be your problem. Have you updated all your modules from the command line?? If not, please do so.
 
I run this /root/upgrade-fpbx-modules
that is this:

#!/bin/bash
rm -f /tmp/*
fwconsole ma upgradeall
fwconsole reload
/root/sig-fix
systemctl restart httpd.service
/root/sig-fix

but it does not find any updates for some reason?
 
Last edited:
OK I got it going I uninstalled with command fwconsole ma remove incrediblepbx

then got in to the FreePBX GUI and updated the Modules. Then SSH in and reinstalled incrediblepbx 17.0.3
and its all back and working!!

I just need to clean up this entry in Modules left over from me trying to install it through the command line not sure how to do it ? I restarted and its still there in red.
Can not install this version because PHP needs to be updated (PHP version 8.2.0 or higher is required, you have 7.4.33) and since everything is working now I did not want to possibly mess everything up.
 

Attachments

  • disabled.JPG
    disabled.JPG
    89.4 KB · Views: 10
Last edited:
@Hometech: I think it's fair to say that Sangoma's framework f*ck up made quite a mess for many folks, not just IncrediblePBX users.
 
Try this to download the FreePBX-16 version of framework.
Code:
fwconsole ma downloadinstall framework --tag=16.0.41
fwconsole reload
 
Thanks ken10 that fixed it !!
Its all good now thanks for the help.

No issues Ward it was out of your control....force majeure
 
OK I got it going I uninstalled with command fwconsole ma remove incrediblepbx

then got in to the FreePBX GUI and updated the Modules. Then SSH in and reinstalled incrediblepbx 17.0.3
and its all back and working!!

I just need to clean up this entry in Modules left over from me trying to install it through the command line not sure how to do it ? I restarted and its still there in red.
Can not install this version because PHP needs to be updated (PHP version 8.2.0 or higher is required, you have 7.4.33) and since everything is working now I did not want to possibly mess everything up.
I had to do the same thing and remove incredible. @Hometech how did you reinstall incrediblepbx 17.0.3? And it didnt break anything when you reinstalled? TIA
 

kmcdaniel, After I uninstalled the incrediblepbx I was able to use the GUI interface for FreePBX and I had to upgrade many Modules that were needing it including framework. Up until now I had only been upgrading through SSH using command (fwconsole ma upgradeall) (because I thought that it was said we should not upgrade through the Module Admin because it would brake incrediblepbx) anyways it was not updating all the modules for some reason. Once I did all that then Reinstall incrediblepbx module the correct version for me it was all working. In the future I will check the module admin and update as needed. glad you got it working correctly again.
 
(because I thought that it was said we should not upgrade through the Module Admin because it would brake incrediblepbx)
This is the first time Sangoma has done something to FreePBX that badly broke the IncrediblePBX module. At one point, the IncrdiblePBX module had to be converted to run with PHP 8.2 so it would work with FreePBX-17. This last login screen issue wasn't just IncrediblePBX that it broke. Most people who compiled FreePBX from scratch using the open source modules had the same issue. I've always used the module manager in the GUI unless some craziness cropped up with FreePBX that forced me to drop to the command line and do a delete, update or install.

fwconsole ma upgradeall can bite you on the *ss if you aren't careful.
 
I am encountering similar issues with login. My framework version is 16.0.40.4 and I do have the login button, but when I click nothing happens (no HTTP request in the browser console or server logs).

When I remove the incrediblepbx module the style of the login page changes and I am able to login.

I think installing a version 17 module would be a mistake, although I wouldn't mind upgrading everything to the latest version. The current setup is Incredible PBX 2027-D for Ubuntu 22.04.5 LTS
 
Have you tried some of the previous suggestions? post #44 or #46?
From post #46 it looks like you need framework 16.0.41
 
@rob92: If you get a login button but nothing happens, here is the fix you need. Reproduced below:
Code:
fwconsole ma remove incrediblepbx
fwconsole reload
fwconsole ma upgradeall
fwconsole reload
fwconsole ma downloadinstall https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/IncrediblePBX-Branding-Module/incrediblepbx-17.0.3.tgz
fwconsole reload
/root/sig-fix
/root/sig-fix
 
Thanks, that works. I was just unsure about installing Incredible PBX v17 module when everything else is v16.
 
Here is some further background regarding the underlying problem (submitted by Piero Andreini):

Environment:
- OS: Rocky Linux 8.8
- IncrediblePBX module: 13.0.10
- FreePBX framework: 16.0.40.4
- FreePBX core: 16.0.68.20

The issue is in:
/var/www/html/admin/modules/incrediblepbx/views/login.php

The fallback stub for checkPasswordReminder() returns Promise.resolve() with no argument:

function checkPasswordReminder(currentForm) {
return Promise.resolve(); // resolves with undefined
}

Since handleMFAFunc() checks if(response) before triggering the form submit, a resolved Promise with undefined is treated as false, and the login form is never submitted. The user sees the credential dialog but clicking Continue does nothing — no POST request is ever sent to the server.

This only manifests when no MFA or password-reminder module is installed that would otherwise define a real checkPasswordReminder() function. In that case the stub is used, and the bug surfaces.

The fix is trivial:

return Promise.resolve(true);

This was discovered after significant debugging on a production system.
 
I also just ran into this one and "return Promise.resolve(true);" worked for me. I appreciate you guys figuring that out. Not sure how long it would have taken me to find that.
 

Members online

No members online now.

Forum statistics

Threads
26,718
Messages
174,602
Members
20,285
Latest member
Theo21
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top