An unexpected error occurred in some of the pages, including login
Permalink
Hope someone could help me, because I'm starting run out ideas.
Some of my webpages give an error message "An unexpected error occurred. An error occurred while processing this request." some don't e.g.
Working:
https://pamaus.fi/index.php/seura...
https://pamaus.fi/index.php/toiminta...
Not working:
http://pamaus.fi/
https://pamaus.fi/index.php/toiminta/esitelmat...
https://pamaus.fi/index.php/seura/kirjat...
Also login won't work... so I try fix this from server side.
What I have tried.
1. I have downgrade the lowest PHP Version (7.2.) on server and disable manually all add-ons, but there is no positive effect. My Concrete versio is 8.3.1.
NOTE: PHP Versio could still be a problem as the latest functional version on my records is 5.6., thus I haven't followed or write down PHP version chances since 2018... so don't know. ;-) My server provider said they haven't done any chances, but to be honest their answer wasn't bullet proof so it is possible that they have disabled older PHP version so my server was forced to PHP 7.2.
2. I have tried to activate error display through /application/config/app.php to track the error, but won't get any more detailed error than "An unexpected..."
3. error_log on /concrete/ doesn't give any detail that could give a better understanding, only old "30-Sep-2019 PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 25395713 bytes)" there.
4. None of the administrators or editors has confessed that they have done something on the Concrete5 side, but this is a possibility. ;-)
I have manually clear the cache in server /application/files/cache/
Any ideas?
Some of my webpages give an error message "An unexpected error occurred. An error occurred while processing this request." some don't e.g.
Working:
https://pamaus.fi/index.php/seura...
https://pamaus.fi/index.php/toiminta...
Not working:
http://pamaus.fi/
https://pamaus.fi/index.php/toiminta/esitelmat...
https://pamaus.fi/index.php/seura/kirjat...
Also login won't work... so I try fix this from server side.
What I have tried.
1. I have downgrade the lowest PHP Version (7.2.) on server and disable manually all add-ons, but there is no positive effect. My Concrete versio is 8.3.1.
NOTE: PHP Versio could still be a problem as the latest functional version on my records is 5.6., thus I haven't followed or write down PHP version chances since 2018... so don't know. ;-) My server provider said they haven't done any chances, but to be honest their answer wasn't bullet proof so it is possible that they have disabled older PHP version so my server was forced to PHP 7.2.
2. I have tried to activate error display through /application/config/app.php to track the error, but won't get any more detailed error than "An unexpected..."
3. error_log on /concrete/ doesn't give any detail that could give a better understanding, only old "30-Sep-2019 PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 25395713 bytes)" there.
4. None of the administrators or editors has confessed that they have done something on the Concrete5 side, but this is a possibility. ;-)
I have manually clear the cache in server /application/files/cache/
Any ideas?
I can't login to dashboard, because of "unexpected error". See:https://pamaus.fi/index.php/login... and won't be able to switch on debug through browser. Any idea to do this from server side. I have tried to activate debugging with editing /application/config/app.php as someone guided on this forum with:
<?php return array( ); 'debug' => [ /* * Display errors * * @var bool */ 'display_errors' => true, /* * Site debug level * * @var string (message|debug) */
Viewing 15 lines of 17 lines. View entire code block.
That's almost right but not quite, try this
<?php return array( 'debug' => [ /* * Display errors * * @var bool */ 'display_errors' => true, /* * Site debug level * * @var string (message|debug) */ 'detail' => 'debug',
Viewing 15 lines of 17 lines. View entire code block.
Noup. No difference. Same old "An unexpected..." without any helping debug details.
I did clear the cache manually on server before try outs and check that the error_log didn't give any PHP parse errors. Any more ideas to get debug information or just something I could check or try? I'm quite open to any ideas because my full backup is from March.
I did clear the cache manually on server before try outs and check that the error_log didn't give any PHP parse errors. Any more ideas to get debug information or just something I could check or try? I'm quite open to any ideas because my full backup is from March.
With dashboard and debug not working, your problem is likely to be something truly global, such as broken code. That could include any of your config files, which are actually all code. However, not so fundamental that it stops the error message appearing and being styled.
Your server should have error logs for apache and for php which may give some clues.
Your server should have error logs for apache and for php which may give some clues.
If you have access to the database you might be able to see the error in the Logs table as the latest entry.
Advice to check database Logs was useful. I wasn't able to fix this problem with database logs information, but detected and fixed one error with the "password request" add-on.
I was able to solve the problem by changing current PHP version from native 7.2 to 7.3 and back to core 7.2. This normalized the web page. I noted PHP error when checked suEXEC error log messages like "[2020-08-27 18:39:01]: uid: (1316/pamaus) gid: (1310/pamaus) cmd: ea-php72" on server.
https://c5magic.co.uk/index.php/dashboard/system/environment/debug...
- Output error information to site users
- Show the debug error output