SOLVED Can't Login After Upgrading to Lastest Master Branch (v5.3.4)

[kagbasi]

Good-day Folks,

I trust you're all doing well. I have a FusionPBX instance running in a test lab that I hadn't updated for a while, so today I wanted to bring it up to the latest master branch - v5.3.4 (Commit: 9815d319e66d3490cff5233d1347b1232ee2d4c5). As I have always done, I logged in and ran the upgrade (from the GUI). I logged out, like I always do, and now I can't get back in.

I've even logged into the database and attempted to manipulate the public.v_users table and place an old password that I had from an old backup, but doesn't seem to be helping. Anybody know of a way around this issue?

PS. Unfortunately, I do no have a backup. This system is running on a small physical box, so no snapshots either.

 

[kagbasi]

Issue resolved, thanks to @markjcrane .

Turns out the previously documented (and still available online) method for resetting the password is out of date. Mark explained to me that the config.php and config.lua files are no longer relevant, and it's the config.conf file that's now referenced.

So for anybody else who runs into this problem, you can still follow the instructions in the documentation and that video on YouTube (don't have it now) but target the config.conf file instead.

 

[markjcrane]

I'll provide a little more information to help people out.

You need a file called config.conf in the /etc/fusionpbx directory. Here is an example file you will need to update the database password which you can get from the config.php file.

#database system settings
database.0.type = pgsql
database.0.host = localhost
database.0.port = 5432
database.0.sslmode = prefer
database.0.name = fusionpbx
database.0.username = fusionpbx
database.0.password = YourFusionPBXDatabaseUserPassword

#database switch settings
database.1.type = sqlite
database.1.path = /var/lib/freeswitch/db
database.1.name = core.db

#general settings
document.root = /var/www/fusionpbx
project.path =
temp.dir = /tmp
php.dir = /usr/bin
php.bin = php

#cache settings
cache.method = file
cache.location = /var/cache/fusionpbx
cache.settings = true

#switch settings
switch.conf.dir = /etc/freeswitch
switch.sounds.dir = /usr/share/freeswitch/sounds
switch.database.dir = /var/lib/freeswitch/db
switch.recordings.dir = /var/lib/freeswitch/recordings
switch.storage.dir = /var/lib/freeswitch/storage
switch.voicemail.dir = /var/lib/freeswitch/storage/voicemail
switch.scripts.dir = /usr/share/freeswitch/scripts

#switch xml handler
xml_handler.fs_path = false
xml_handler.reg_as_number_alias = false
xml_handler.number_as_presence_id = true

#error reporting options: user,dev,all
error.reporting = user

For some time the upgrade would make this file for you if /etc/fusionpbx directory was writable. New installs will have this file by default.

So why use a new config.conf file instead of config.php and config.lua. In my point of view, it was more Unix-friendly to use a standard config file. Also, both lua and PHP can use the same file.