Edit and ExtensionError! Request failed with status code 500

Andyd358

Andyd358

Member
Aug 23, 2018
267
11
18
56
UK
Just setup a fresh install to test, and after I have created an Extension if I go to view it/edit it, I get fspbx edit ext Error! Request failed with status code 500
 
@Andyd358 I'm sorry it happened to you. It happened to a couple of other people this month. Here is a quick fix. Run the updates


Code: 
cd /var/www/fspbx
php artisan app:update
php artisan migrate

Before you do this, could you please go to the log file
Code: 
tail -f /var/www/fspbx/storage/logs/laravel.log


and post your last error here. Once you run the tail command, you can go back to the extensions page and throw the error one more time. This will help me fix ir permanently for all future installs.
 
#62 /var/www/fspbx/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php(99): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#63 /var/www/fspbx/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Foundation\\Http\\Middleware\\PreventRequestsDuringMaintenance->handle()
#64 /var/www/fspbx/vendor/laravel/framework/src/Illuminate/Http/Middleware/TrustProxies.php(39): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#65 /var/www/fspbx/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(180): Illuminate\\Http\\Middleware\\TrustProxies->handle()
#66 /var/www/fspbx/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(116): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}()
#67 /var/www/fspbx/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(175): Illuminate\\Pipeline\\Pipeline->then()
#68 /var/www/fspbx/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(144): Illuminate\\Foundation\\Http\\Kernel->sendRequestThroughRouter()
#69 /var/www/fspbx/public/index.php(52): Illuminate\\Foundation\\Http\\Kernel->handle()
#70 {main}
 
tail doesn’t open the whole log—logs can be huge. It shows the end of the file and then streams new lines as they’re written (like watching fs_cli events). So start tail, then reproduce the issue; the latest error will appear live.
 
you can also force it to open more recent lines by runnign this command

Code: 
tail -n 200 -f /path/to/log.log
 
pbxgeek said:
tail doesn’t open the whole log—logs can be huge. It shows the end of the file and then streams new lines as they’re written (like watching fs_cli events). So start tail, then reproduce the issue; the latest error will appear live.
Click to expand...
Sorry bud Ive already ran the commands
 
You must log in or register to reply here.
Top Bottom