Open Phones Provisioning ends in Exception

I’m on:
VitalPBX 3.1.0-1
Asterisk 18.4.0-1
Phones Provisioning 1.0.2-4

The issue:
Opening Phones Provisioning AddOn…
Admin > Add-ons > Add-ons > Phones Provisioning
…ends in the following exception:

Exception: [0-get] {https://127.0.0.1/provisioning/api/devices}: at file /usr/share/vitalpbx/www/includes/components/provisioning/RestClient.php on line 0

VitalPbxPhonesProvisioningException

Similar issue by
PBX > Provisioning > Provisioning

Any idea how to solve this?

Thanks!

Try reinstalling the provisioning add-on.

yum clean all
yum reinstall provisioning-core -y
yum reinstall vitalpbx-phones-provisioning -y

No, unfortunately that did not help.
The problem still exists.

Just as a note: “I have tested in a brand new installation, and I am not able to reproduce this issue.”

Try executing the commands below.

/usr/share/vitalpbx/scripts/apply_migrations "provisioning"
/usr/share/provisioning/artisan migrate --force

Let me know if any of these commands generate an error during its execution.

No error, I just get back…

/usr/share/vitalpbx/scripts/apply_migrations "provisioning"
/usr/share/provisioning/artisan migrate --force
Nothing to migrate.

The problem still exists.

Check the log in the following path:

/usr/share/provisioning/storage/logs/laravel.log

The logs folder is completely empty.

Well, there’s nothing else to try then.

The only other thing I can think of, is either permissions or a software version that is incompatible.

How did you install VitalPBX?

It was installed by vitalpbx-3.0.6-1.iso, around 02/2021.

Then multiple times updated by ‘yum update’ to the latest version.

It’s running as a long term test and intended for internal use for now and as soon as the API has the necessary functionality, it was planned to use it as solution for customers.

I know that the phone provisioning add-on worked in the past, at least it was possible to open it.

Since which update it doesn’t work anymore… I don’t know.

Current Linux Version: CentOS Linux release 7.9.2009 (Core)

We have the latest version working fine on several servers.

Try running:

vitalpbx check-integrity

You can also try to reboot the PBX.

This brought some errors to light…

vitalpbx check-integrity

Issues Found:
The folder or file "/var/lib/vitalpbx/static" had the group "none" instead of "apache" (fixed up)
The folder or file "/var/lib/vitalpbx/static/backup" had the group "none" instead of "apache" (fixed up)
Folder "/var/lib/vitalpbx/static/fax" didn't exist (fixed up)
The folder or file "/var/lib/vitalpbx/static/fax" had the permissions 3325 instead of 2775 (fixed up)
The folder or file "/var/lib/vitalpbx/static/fax" had the owner "root" instead of "apache" (fixed up)
The folder or file "/var/lib/vitalpbx/static/pictures" had the group "none" instead of "apache" (fixed up)
Folder "/var/lib/vitalpbx/static/recordings" didn't exist (fixed up)
The folder or file "/var/lib/vitalpbx/static/recordings" had the permissions 3325 instead of 2775 (fixed up)
The folder or file "/var/lib/vitalpbx/static/recordings" had the owner "root" instead of "apache" (fixed up)

But unfortunately this did not solve the problem.

Even a reboot did not solve the problem.

Btw:
Here is someone who obviously has the same problem, the screenshot looks suspiciously similar…

Hooray, I am not alone :slight_smile:

Anyway, I solved the problem for me by installing a new VM and by transferring the backup. On the new installation I can open the add-on.

It feels like there is a migration error in one of the past updates!?

The old VM is still running, so if anyone is interested in determining the problem - it’s still available for a while.

I also facing same provision. I found the error due to we have change the default https port to any other port will have such error.
I think is a bugs,