Unfortunately none of those are errors. I recommend you load the page and see if it’s still spinning and loading or if it’s just white. I suspect you aren’t giving it any time because I suspect it’s a execution timeout but I have no way of knowing from your logs
Yikes…I’d like to get affirmation from @tm1000 or similar that this is a reasonably prudent approach before I try it…I tried rc18 and rc19 today, but still no change.
The steps I posted should be followed. You shouldn’t follow what anyone else wrote.
To be honest @mkleine’s issue is all over the place and I’m still not sure that person is even talking about freepbx 12 and all of that work does not need to be done (for said person sure but not for everyone). First off deleting the module “framework” actually does nothing along with some other issues with the thread but in the end I’m glad it got fixed for @mkleine
If anyone is still having this issue feel free to PM me
I see. @beef Please remove extension routes from your machine. Your issue is (as suspected) unrelated to this thread and as I suspected this thread is filled with varying reports of different issues.
Remove extension routes. If you still can’t access module admin please let me know
For me nothing helped, after a debug that was getting into a loop it advised me to upgrade modules because some of them where disabled.
After I gave the command amportal a ma upgrade all i thought the problem was solved, i could login again but with some errors, the dashboard was the fallback page.
Then i rebooted the pi and now I only got a db error:
FATAL ERROR
DB Error: connect failed
Trace Back
/var/www/html/admin/libraries/db_connect.php:71 die_freepbx()
[0]: DB Error: connect failed
Please wait…
/usr/local/sbin/amportal: regel 47: [FATAL]: opdracht niet gevonden
/var/lib/asterisk/bin/freepbx_engine: regel 98: [FATAL]: opdracht niet gevonden
**** WARNING: ERROR IN CONFIGURATION ****
astrundir in ‘/etc/asterisk’ is set to but the directory
does not exists. Attempting to create it with: 'mkdir -p ’
mkdir: ontbrekend argument
Typ ‘mkdir --help’ voor meer informatie.
**** ERROR: COULD NOT CREATE ****
Attempt to execute 'mkdir -p ’ failed with an exit code of 1
You must create this directory and the try again.
root@raspbx:~#