Advertisement

Server update broke site with "500 - Whoops, looks like something went wrong" Topic is solved

General questions relating to Joomla! 5.x.

Moderator: General Support Moderators

Forum rules
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting.
Forum Post Assistant - If you are serious about wanting help, you should use this tool to help you post.
Windows Defender SmartScreen Issues <-- please read this if using Windows 10
Post Reply
KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 2:44 am

I am facing this same issue but it's after my hosting provider did some update on their servers. How can i fix this?
Last edited by toivo on Thu Feb 13, 2025 3:50 am, edited 1 time in total.
Reason: mod note: split from https://forum.joomla.org/viewtopic.php?f=841&t=1012789 - please create your own topics in the future!

Advertisement
User avatar
toivo
Joomla! Master
Joomla! Master
Posts: 18077
Joined: Thu Feb 15, 2007 5:48 am
Location: Sydney, Australia

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by toivo » Thu Feb 13, 2025 4:02 am

Your reply was split from a different, already resolved topic.

More information is required. Please edit the file configuration.php in the main Joomla folder and make the following changes, then post the PHP error message and the lines from the PHP call stack into your reply:

Code: Select all

	public $error_reporting = 'maximum';
	public $debug = true;
The error message will contain the name of the script and the line number in the third party extension that is incompatible with your version of Joomla or PHP.

Please also post the results from the Forum Post Assistant (FPA) by following the instructions at https://forumpostassistant.github.io/docs/ so that the configuration can be reviewed.
Toivo Talikka, Global Moderator

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 2:10 pm

this is the error I am getting now after doing what you recommended. I wanted to provide a screenshot but I was unable to but here is the link to the website you can go there and you will see it. https://kemtaqtechnologies.com

error: Can't create more than max_prepared_stmt_count statements (current value: 100000)

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 3:47 pm

@smmsharks how is this going to help me get back my site online?

gsmela
Joomla! Explorer
Joomla! Explorer
Posts: 460
Joined: Thu Jun 10, 2010 12:38 pm

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by gsmela » Thu Feb 13, 2025 4:53 pm

Follow the suggestions that Volvo made above. Nobody can help you if you don't provide what is asked of you.

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 5:12 pm

gsmela wrote: Thu Feb 13, 2025 4:53 pm Follow the suggestions that Volvo made above. Nobody can help you if you don't provide what is asked of you.
I am new to joomla and all. I look through and I did not see anyone name Volvo gave me any instructions to do, the only person gave me something to do is toivo which I tried my best to do.

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 5:14 pm

toivo wrote: Thu Feb 13, 2025 4:02 am Your reply was split from a different, already resolved topic.

More information is required. Please edit the file configuration.php in the main Joomla folder and make the following changes, then post the PHP error message and the lines from the PHP call stack into your reply:

Code: Select all

	public $error_reporting = 'maximum';
	public $debug = true;
The error message will contain the name of the script and the line number in the third party extension that is incompatible with your version of Joomla or PHP.

Please also post the results from the Forum Post Assistant (FPA) by following the instructions at https://forumpostassistant.github.io/docs/ so that the configuration can be reviewed.

I was able to update a screenshot
You do not have the required permissions to view the files attached to this post.

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 5:29 pm

"Please also post the results from the Forum Post Assistant (FPA) by following the instructions at https://forumpostassistant.github.io/docs/ so that the configuration can be reviewed. "

for the instructions above please see the screenshot below.
You do not have the required permissions to view the files attached to this post.

gsmela
Joomla! Explorer
Joomla! Explorer
Posts: 460
Joined: Thu Jun 10, 2010 12:38 pm

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by gsmela » Thu Feb 13, 2025 5:45 pm

Forum Post Assistant (v1.6.7) : 13-Feb-2025 wrote:
Basic Environment :: wrote:Joomla! Instance :: Joomla! 5.2.3-Stable (Uthabiti) 7-January-2025
Joomla! Configured :: Yes | Writable (644) |
Configuration Options :: Offline: false | SEF: true | SEF Suffix: false | SEF ReWrite: true | .htaccess/web.config: Yes | GZip: false | Cache: false | CacheTime: 15 | CacheHandler: file | CachePlatformPrefix: false | FTP Layer: false | Proxy: false | LiveSite: Is Not Empty | Session lifetime: 15 | Session handler: database | Shared sessions: false | SSL: 0 | Error Reporting: maximum | Site Debug: true | Language Debug: false | Default Access: Public | Unicode Slugs: false | dbConnection Type: mysqli | PHP Supports J! 5.2.3: Yes | Database Supports J! 5.2.3: Yes | Database Credentials Present: Yes |

Host Configuration :: OS: Linux | OS Version: 5.14.0-503.15.1.el9_5.x86_64 | Technology: x86_64 | Web Server: LiteSpeed | Encoding: gzip, deflate, br | System TMP Writable: Yes | Free Disk Space : 14813.83 GiB |

PHP Configuration :: Version: 8.2.27 | PHP API: litespeed | Session Path Writable: Yes | Display Errors: 0 | Error Reporting: 22527 | Log Errors To: /home/u678752818/.logs/error_log_kemtaqtechnologies_com | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 2048M | Max. POST Size: 2048M | Max. Input Time: 360 | Max. Execution Time: 360 | Memory Limit: 2048M

Database Configuration :: Version: 10.11.10-MariaDB (Client:mysqlnd 8.2.27) | Database Size: 11.41 MiB | #of Tables with config prefix:  92 | #of other Tables:  0 | User Privileges : GRANT ALL
Detailed Environment :: wrote:PHP Extensions :: Core (8.2.27) | date (8.2.27) | libxml (8.2.27) | openssl (8.2.27) | pcre (8.2.27) | sqlite3 (8.2.27) | zlib (8.2.27) | bz2 (8.2.27) | calendar (8.2.27) | ctype (8.2.27) | curl (8.2.27) | hash (8.2.27) | filter (8.2.27) | ftp (8.2.27) | gettext (8.2.27) | json (8.2.27) | iconv (8.2.27) | SPL (8.2.27) | pcntl (8.2.27) | random (8.2.27) | readline (8.2.27) | Reflection (8.2.27) | session (8.2.27) | standard (8.2.27) | mbstring (8.2.27) | shmop (8.2.27) | SimpleXML (8.2.27) | tokenizer (8.2.27) | xml (8.2.27) | litespeed () | bcmath (8.2.27) | dom (20031129) | fileinfo (8.2.27) | gd (8.2.27) | gmp (8.2.27) | igbinary (3.2.15) | imagick (3.7.0) | imap (8.2.27) | intl (8.2.27) | exif (8.2.27) | monarxprotect (5.1.51) | msgpack (2.2.0) | PDO (8.2.27) | mysqlnd (mysqlnd 8.2.27) | mysqli (8.2.27) | pdo_mysql (8.2.27) | pdo_sqlite (8.2.27) | Phar (8.2.27) | posix (8.2.27) | redis (5.3.7) | soap (8.2.27) | sockets (8.2.27) | sysvmsg (8.2.27) | sysvsem (8.2.27) | sysvshm (8.2.27) | tidy (8.2.27) | timezonedb (2024.2) | xmlreader (8.2.27) | xmlrpc (1.0.0RC3) | xmlwriter (8.2.27) | xsl (8.2.27) | zip (1.21.1) | Zend OPcache (8.2.27) | Zend Engine (4.2.27) |
Potential Missing Extensions ::
Disabled Functions :: system | exec | shell_exec | passthru | mysql_list_dbs | ini_alter | dl | symlink | link | chgrp | leak | popen | apache_child_terminate | virtual | mb_send_mail |

Switch User Environment :: PHP CGI: Yes | Server SU: No | PHP SU: Yes | Potential Ownership Issues: No
Folder Permissions :: wrote:Core Folders :: images/ (755) | components/ (755) | modules/ (755) | plugins/ (755) | language/ (755) | templates/ (755) | cache/ (755) | logs/ (---) | tmp/ (755) | administrator/components/ (755) | administrator/modules/ (755) | administrator/language/ (755) | administrator/templates/ (755) | administrator/logs/ (755) | api/ (755) |

Elevated Permissions (First 10) ::
Database Information :: wrote:Database statistics :: Uptime: 1501118 | Threads: 362 | Questions: 14354980872 | Slow queries: 18047 | Opens: 2657806 | Open tables: 511999 | Queries per second avg: 9562.859 |
Extensions Discovered :: wrote:Components :: Site ::
Core ::
3rd Party::

Components :: Admin ::
Core :: com_modules (4.0.0) 1 | com_languages (4.0.0) 1 | com_actionlogs (3.9.0) 1 | com_joomlaupdate (4.0.3) 1 | com_cache (4.0.0) 1 | com_templates (4.0.0) 1 | com_cpanel (4.0.0) 1 | com_media (3.0.0) 1 | com_wrapper (4.0.0) 1 | com_redirect (4.0.0) 1 | com_banners (4.0.0) 1 | com_associations (4.0.0) 1 | com_workflow (4.0.0) 1 | com_users (4.0.0) 1 | com_privacy (3.9.0) 1 | com_finder (4.0.0) 1 | com_fields (4.0.0) 1 | com_tags (4.0.0) 1 | com_login (4.0.0) 1 | com_mails (4.0.0) 1 | com_plugins (4.0.0) 1 | com_checkin (4.0.0) 1 | com_contenthistory (4.0.0) 1 | com_messages (4.0.0) 1 | com_postinstall (4.0.0) 1 | com_ajax (4.0.0) 1 | com_menus (4.0.0) 1 | com_categories (4.0.0) 1 | com_installer (4.0.0) 1 | com_guidedtours (4.3.0) 1 | com_content (4.0.0) 1 | com_admin (4.0.0) 1 | com_scheduler (4.1.0) 1 | com_config (4.0.0) 1 | com_newsfeeds (4.0.0) 1 |
3rd Party:: com_akeebabackup (9.9.11) 1 | SP Page Builder (5.1.8) 1 | COM_FFEXPLORER (1.0.7) 1 | SP Simple Portfolio (2.1.0) 1 |

Modules :: Site ::
Core :: mod_articles_category (3.0.0) 1 | mod_custom (3.0.0) 1 | mod_menu (3.0.0) 1 | mod_syndicate (3.0.0) 1 | mod_login (3.0.0) 1 | mod_articles_news (3.0.0) 1 | mod_random_image (3.0.0) 1 | mod_wrapper (3.0.0) 1 | mod_related_items (3.0.0) 1 | mod_banners (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_articles_archive (3.0.0) 1 | mod_users_latest (3.0.0) 1 | mod_finder (3.0.0) 1 | mod_articles_categories (3.0.0) 1 | mod_stats (3.0.0) 1 | mod_languages (3.5.0) 1 | mod_whosonline (3.0.0) 1 | mod_breadcrumbs (3.0.0) 1 | mod_articles_popular (3.0.0) 1 | mod_articles_latest (3.0.0) 1 | mod_footer (3.0.0) 1 | MOD_ARTICLES (5.2.0) 1 | mod_tags_popular (3.1.0) 1 | mod_tags_similar (3.1.0) 1 |
3rd Party:: SP Page Builder (5.1.8) 1 | SP Simple Portfolio Module (2.1.0) 1 |

Modules :: Admin ::
Core :: mod_logged (3.0.0) 1 | mod_custom (3.0.0) 1 | mod_sampledata (3.8.0) 1 | mod_menu (3.0.0) 1 | mod_quickicon (3.0.0) 1 | mod_loginsupport (4.0.0) 1 | mod_latestactions (3.9.0) 1 | mod_login (3.0.0) 1 | mod_user (4.0.0) 1 | mod_post_installation_messages (4.0.0) 1 | mod_title (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_guidedtours (4.3.0) 1 | mod_privacy_status (4.0.0) 1 | mod_latest (3.0.0) 1 | mod_messages (4.0.0) 1 | mod_stats_admin (3.0.0) 1 | mod_multilangstatus (3.0.0) 1 | mod_submenu (3.0.0) 1 | mod_version (3.0.0) 1 | mod_popular (3.0.0) 1 | mod_toolbar (3.0.0) 1 | mod_privacy_dashboard (3.9.0) 1 | mod_frontend (4.0.0) 1 |
3rd Party::

Libraries ::
Core ::
3rd Party::

Plugins ::
Core :: plg_api-authentication_token (4.0.0) 1 | plg_api-authentication_basic (4.0.0) 0 | plg_sampledata_multilang (4.0.0) 1 | plg_media-action_resize (4.0.0) 1 | plg_media-action_rotate (4.0.0) 1 | plg_media-action_crop (4.0.0) 1 | plg_task_rotatelogs (5.0.0) 1 | plg_task_requests (4.1) 1 | plg_task_check_files (4.1) 1 | plg_task_sessiongc (5.0.0) 1 | plg_task_globalcheckin (5.0.0) 1 | plg_task_site_status (4.1) 1 | plg_task_updatenotification (5.0.0) 1 | plg_task_privacyconsent (5.0.0) 1 | plg_task_deleteactionlogs (5.0.0) 1 | plg_user_contactcreator (3.0.0) 0 | plg_user_token (3.9.0) 1 | plg_user_profile (3.0.0) 0 | plg_user_joomla (3.0.0) 1 | plg_user_terms (3.9.0) 0 | plg_privacy_consents (3.9.0) 1 | plg_privacy_user (3.9.0) 1 | plg_privacy_content (3.9.0) 1 | plg_privacy_actionlogs (3.9.0) 1 | plg_privacy_message (3.9.0) 1 | plg_multifactorauth_webauthn (4.2.0) 0 | plg_multifactorauth_yubikey (3.2.0) 0 | plg_multifactorauth_totp (3.2.0) 0 | plg_multifactorauth_email (4.2.0) 0 | plg_multifactorauth_fixed (4.2.0) 0 | plg_system_sef (3.0.0) 1 | plg_system_debug (3.0.0) 1 | plg_system_languagefilter (3.0.0) 0 | plg_system_webauthn (4.0.0) 1 | plg_system_guidedtours (4.3.0) 1 | plg_system_remember (3.0.0) 1 | plg_system_cache (3.0.0) 0 | plg_system_actionlogs (3.9.0) 1 | plg_system_stats (3.5.0) 0 | plg_system_redirect (3.0.0) 0 | plg_system_schedulerunner (4.1) 1 | plg_system_logout (3.0.0) 1 | plg_system_accessibility (4.0.0) 0 | plg_system_task_notification (4.1) 1 | plg_system_shortcut (4.2.0) 1 | plg_system_httpheaders (4.0.0) 1 | plg_system_jooa11y (4.2.0) 1 | plg_system_languagecode (3.0.0) 0 | plg_system_fields (3.7.0) 1 | plg_system_skipto (4.0.0) 1 | plg_system_log (3.0.0) 1 | plg_system_highlight (3.0.0) 1 | plg_system_schemaorg (5.0.0) 1 | plg_system_privacyconsent (3.9.0) 0 | plg_editors-xtd_menu (3.7.0) 1 | plg_editors-xtd_module (3.5.0) 1 | plg_editors-xtd_image (3.0.0) 1 | plg_editors-xtd_readmore (3.0.0) 1 | plg_editors-xtd_article (3.0.0) 1 | plg_editors-xtd_pagebreak (3.0.0) 1 | plg_editors-xtd_fields (3.7.0) 1 | plg_quickicon_privacycheck (3.9.0) 1 | plg_quickicon_eos (4.4.0) 1 | plg_quickicon_phpversioncheck (3.7.0) 1 | plg_quickicon_overridecheck (4.0.0) 1 | plg_quickicon_downloadkey (4.0.0) 1 | plg_quickicon_extensionupdate (3.0.0) 1 | plg_quickicon_joomlaupdate (3.0.0) 1 | plg_captcha_recaptcha_invisible (3.8) 0 | plg_extension_namespacemap (4.0.0) 1 | plg_extension_joomla (3.0.0) 1 | plg_extension_finder (4.0.0) 1 | Content - SP Page Builder (5.1.8) 1 | plg_content_pagenavigation (3.0.0) 1 | plg_content_emailcloak (3.0.0) 1 | plg_content_vote (3.0.0) 0 | plg_content_loadmodule (3.0.0) 1 | plg_content_joomla (3.0.0) 1 | plg_content_confirmconsent (3.9.0) 0 | plg_content_pagebreak (3.0.0) 1 | plg_content_fields (3.7.0) 1 | plg_content_finder (3.0.0) 1 | K2 - SP Page Builder (3.8.10) 0 | plg_filesystem_local (4.0.0) 1 | plg_authentication_ldap (3.0.0) 0 | plg_authentication_joomla (3.0.0) 1 | plg_authentication_cookie (3.0.0) 1 | plg_webservices_messages (4.0.0) 1 | plg_webservices_users (4.0.0) 1 | plg_webservices_config (4.0.0) 1 | plg_webservices_templates (4.0.0) 1 | plg_webservices_menus (4.0.0) 1 | plg_webservices_privacy (4.0.0) 1 | plg_webservices_media (4.1.0) 1 | plg_webservices_newsfeeds (4.0.0) 1 | plg_webservices_languages (4.0.0) 1 | plg_webservices_content (4.0.0) 1 | plg_webservices_redirect (4.0.0) 1 | plg_webservices_modules (4.0.0) 1 | plg_webservices_tags (4.0.0) 1 | plg_webservices_plugins (4.0.0) 1 | plg_webservices_installer (4.0.0) 1 | plg_webservices_banners (4.0.0) 1 | plg_fields_subform (4.0.0) 1 | plg_fields_usergrouplist (3.7.0) 1 | plg_fields_sql (3.7.0) 1 | plg_fields_text (3.7.0) 1 | plg_fields_user (3.7.0) 1 | plg_fields_color (3.7.0) 1 | plg_fields_media (3.7.0) 1 | plg_fields_editor (3.7.0) 1 | plg_fields_radio (3.7.0) 1 | plg_fields_calendar (3.7.0) 1 | plg_fields_textarea (3.7.0) 1 | plg_fields_imagelist (3.7.0) 1 | plg_fields_checkboxes (3.7.0) 1 | plg_fields_list (3.7.0) 1 | plg_fields_integer (3.7.0) 1 | plg_fields_url (3.7.0) 1 | plg_workflow_featuring (4.0.0) 1 | plg_workflow_notification (4.0.0) 1 | plg_workflow_publishing (4.0.0) 1 | plg_finder_contacts (3.0.0) 1 | plg_finder_newsfeeds (3.0.0) 1 | plg_finder_content (3.0.0) 1 | plg_finder_tags (3.0.0) 1 | plg_finder_categories (3.0.0) 1 | plg_schemaorg_organization (5.0.0) 1 | plg_schemaorg_jobposting (5.0.0) 1 | plg_schemaorg_book (5.0.0) 1 | plg_schemaorg_event (5.0.0) 1 | plg_schemaorg_blogposting (5.0.0) 1 | plg_schemaorg_article (5.1.0) 1 | plg_schemaorg_person (5.0.0) 1 | plg_schemaorg_custom (5.1.0) 1 | plg_schemaorg_recipe (5.0.0) 1 | plg_actionlog_joomla (3.9.0) 1 | plg_behaviour_versionable (4.0.0) 1 | plg_behaviour_taggable (4.0.0) 1 | plg_behaviour_compat (5.0.0) 1 | plg_installer_folderinstaller (3.6.0) 1 | plg_installer_urlinstaller (3.6.0) 1 | plg_installer_packageinstaller (3.6.0) 1 | plg_installer_override (4.0.0) 1 | plg_installer_webinstaller (4.0.0) 1 |
3rd Party:: SP Simple Portfolio - SP Page Build (5.1.8) ? | System - SP PageBuilder (5.1.8) 1 | System - SP Page Builder Pro Update (5.1.8) ? | System - Helix Ultimate Framework (2.1.1) 1 | PLG_QUICKICON_AKEEBABACKUP (9.9.11) 1 | plg_editors_tinymce (6.8.4) 1 | plg_editors_codemirror (6.0.0) 1 | plg_search_sppagebuilder (5.1.8) 0 | plg_finder_spsimpleportfolio (1.0.0) 1 | plg_finder_sppagebuilder (5.1.8) 0 |
Templates Discovered :: wrote:Templates :: Site :: cassiopeia (1.0) 1 | Crysa (2.0.9) 1 |
Templates :: Admin :: atum (1.0) 1 |

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 5:58 pm

gsmela wrote: Thu Feb 13, 2025 5:45 pm
Forum Post Assistant (v1.6.7) : 13-Feb-2025 wrote:
Basic Environment :: wrote:Joomla! Instance :: Joomla! 5.2.3-Stable (Uthabiti) 7-January-2025
Joomla! Configured :: Yes | Writable (644) |
Configuration Options :: Offline: false | SEF: true | SEF Suffix: false | SEF ReWrite: true | .htaccess/web.config: Yes | GZip: false | Cache: false | CacheTime: 15 | CacheHandler: file | CachePlatformPrefix: false | FTP Layer: false | Proxy: false | LiveSite: Is Not Empty | Session lifetime: 15 | Session handler: database | Shared sessions: false | SSL: 0 | Error Reporting: maximum | Site Debug: true | Language Debug: false | Default Access: Public | Unicode Slugs: false | dbConnection Type: mysqli | PHP Supports J! 5.2.3: Yes | Database Supports J! 5.2.3: Yes | Database Credentials Present: Yes |

Host Configuration :: OS: Linux | OS Version: 5.14.0-503.15.1.el9_5.x86_64 | Technology: x86_64 | Web Server: LiteSpeed | Encoding: gzip, deflate, br | System TMP Writable: Yes | Free Disk Space : 14813.83 GiB |

PHP Configuration :: Version: 8.2.27 | PHP API: litespeed | Session Path Writable: Yes | Display Errors: 0 | Error Reporting: 22527 | Log Errors To: /home/u678752818/.logs/error_log_kemtaqtechnologies_com | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 2048M | Max. POST Size: 2048M | Max. Input Time: 360 | Max. Execution Time: 360 | Memory Limit: 2048M

Database Configuration :: Version: 10.11.10-MariaDB (Client:mysqlnd 8.2.27) | Database Size: 11.41 MiB | #of Tables with config prefix:  92 | #of other Tables:  0 | User Privileges : GRANT ALL
Detailed Environment :: wrote:PHP Extensions :: Core (8.2.27) | date (8.2.27) | libxml (8.2.27) | openssl (8.2.27) | pcre (8.2.27) | sqlite3 (8.2.27) | zlib (8.2.27) | bz2 (8.2.27) | calendar (8.2.27) | ctype (8.2.27) | curl (8.2.27) | hash (8.2.27) | filter (8.2.27) | ftp (8.2.27) | gettext (8.2.27) | json (8.2.27) | iconv (8.2.27) | SPL (8.2.27) | pcntl (8.2.27) | random (8.2.27) | readline (8.2.27) | Reflection (8.2.27) | session (8.2.27) | standard (8.2.27) | mbstring (8.2.27) | shmop (8.2.27) | SimpleXML (8.2.27) | tokenizer (8.2.27) | xml (8.2.27) | litespeed () | bcmath (8.2.27) | dom (20031129) | fileinfo (8.2.27) | gd (8.2.27) | gmp (8.2.27) | igbinary (3.2.15) | imagick (3.7.0) | imap (8.2.27) | intl (8.2.27) | exif (8.2.27) | monarxprotect (5.1.51) | msgpack (2.2.0) | PDO (8.2.27) | mysqlnd (mysqlnd 8.2.27) | mysqli (8.2.27) | pdo_mysql (8.2.27) | pdo_sqlite (8.2.27) | Phar (8.2.27) | posix (8.2.27) | redis (5.3.7) | soap (8.2.27) | sockets (8.2.27) | sysvmsg (8.2.27) | sysvsem (8.2.27) | sysvshm (8.2.27) | tidy (8.2.27) | timezonedb (2024.2) | xmlreader (8.2.27) | xmlrpc (1.0.0RC3) | xmlwriter (8.2.27) | xsl (8.2.27) | zip (1.21.1) | Zend OPcache (8.2.27) | Zend Engine (4.2.27) |
Potential Missing Extensions ::
Disabled Functions :: system | exec | shell_exec | passthru | mysql_list_dbs | ini_alter | dl | symlink | link | chgrp | leak | popen | apache_child_terminate | virtual | mb_send_mail |

Switch User Environment :: PHP CGI: Yes | Server SU: No | PHP SU: Yes | Potential Ownership Issues: No
Folder Permissions :: wrote:Core Folders :: images/ (755) | components/ (755) | modules/ (755) | plugins/ (755) | language/ (755) | templates/ (755) | cache/ (755) | logs/ (---) | tmp/ (755) | administrator/components/ (755) | administrator/modules/ (755) | administrator/language/ (755) | administrator/templates/ (755) | administrator/logs/ (755) | api/ (755) |

Elevated Permissions (First 10) ::
Database Information :: wrote:Database statistics :: Uptime: 1501118 | Threads: 362 | Questions: 14354980872 | Slow queries: 18047 | Opens: 2657806 | Open tables: 511999 | Queries per second avg: 9562.859 |
Extensions Discovered :: wrote:Components :: Site ::
Core ::
3rd Party::

Components :: Admin ::
Core :: com_modules (4.0.0) 1 | com_languages (4.0.0) 1 | com_actionlogs (3.9.0) 1 | com_joomlaupdate (4.0.3) 1 | com_cache (4.0.0) 1 | com_templates (4.0.0) 1 | com_cpanel (4.0.0) 1 | com_media (3.0.0) 1 | com_wrapper (4.0.0) 1 | com_redirect (4.0.0) 1 | com_banners (4.0.0) 1 | com_associations (4.0.0) 1 | com_workflow (4.0.0) 1 | com_users (4.0.0) 1 | com_privacy (3.9.0) 1 | com_finder (4.0.0) 1 | com_fields (4.0.0) 1 | com_tags (4.0.0) 1 | com_login (4.0.0) 1 | com_mails (4.0.0) 1 | com_plugins (4.0.0) 1 | com_checkin (4.0.0) 1 | com_contenthistory (4.0.0) 1 | com_messages (4.0.0) 1 | com_postinstall (4.0.0) 1 | com_ajax (4.0.0) 1 | com_menus (4.0.0) 1 | com_categories (4.0.0) 1 | com_installer (4.0.0) 1 | com_guidedtours (4.3.0) 1 | com_content (4.0.0) 1 | com_admin (4.0.0) 1 | com_scheduler (4.1.0) 1 | com_config (4.0.0) 1 | com_newsfeeds (4.0.0) 1 |
3rd Party:: com_akeebabackup (9.9.11) 1 | SP Page Builder (5.1.8) 1 | COM_FFEXPLORER (1.0.7) 1 | SP Simple Portfolio (2.1.0) 1 |

Modules :: Site ::
Core :: mod_articles_category (3.0.0) 1 | mod_custom (3.0.0) 1 | mod_menu (3.0.0) 1 | mod_syndicate (3.0.0) 1 | mod_login (3.0.0) 1 | mod_articles_news (3.0.0) 1 | mod_random_image (3.0.0) 1 | mod_wrapper (3.0.0) 1 | mod_related_items (3.0.0) 1 | mod_banners (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_articles_archive (3.0.0) 1 | mod_users_latest (3.0.0) 1 | mod_finder (3.0.0) 1 | mod_articles_categories (3.0.0) 1 | mod_stats (3.0.0) 1 | mod_languages (3.5.0) 1 | mod_whosonline (3.0.0) 1 | mod_breadcrumbs (3.0.0) 1 | mod_articles_popular (3.0.0) 1 | mod_articles_latest (3.0.0) 1 | mod_footer (3.0.0) 1 | MOD_ARTICLES (5.2.0) 1 | mod_tags_popular (3.1.0) 1 | mod_tags_similar (3.1.0) 1 |
3rd Party:: SP Page Builder (5.1.8) 1 | SP Simple Portfolio Module (2.1.0) 1 |

Modules :: Admin ::
Core :: mod_logged (3.0.0) 1 | mod_custom (3.0.0) 1 | mod_sampledata (3.8.0) 1 | mod_menu (3.0.0) 1 | mod_quickicon (3.0.0) 1 | mod_loginsupport (4.0.0) 1 | mod_latestactions (3.9.0) 1 | mod_login (3.0.0) 1 | mod_user (4.0.0) 1 | mod_post_installation_messages (4.0.0) 1 | mod_title (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_guidedtours (4.3.0) 1 | mod_privacy_status (4.0.0) 1 | mod_latest (3.0.0) 1 | mod_messages (4.0.0) 1 | mod_stats_admin (3.0.0) 1 | mod_multilangstatus (3.0.0) 1 | mod_submenu (3.0.0) 1 | mod_version (3.0.0) 1 | mod_popular (3.0.0) 1 | mod_toolbar (3.0.0) 1 | mod_privacy_dashboard (3.9.0) 1 | mod_frontend (4.0.0) 1 |
3rd Party::

Libraries ::
Core ::
3rd Party::

Plugins ::
Core :: plg_api-authentication_token (4.0.0) 1 | plg_api-authentication_basic (4.0.0) 0 | plg_sampledata_multilang (4.0.0) 1 | plg_media-action_resize (4.0.0) 1 | plg_media-action_rotate (4.0.0) 1 | plg_media-action_crop (4.0.0) 1 | plg_task_rotatelogs (5.0.0) 1 | plg_task_requests (4.1) 1 | plg_task_check_files (4.1) 1 | plg_task_sessiongc (5.0.0) 1 | plg_task_globalcheckin (5.0.0) 1 | plg_task_site_status (4.1) 1 | plg_task_updatenotification (5.0.0) 1 | plg_task_privacyconsent (5.0.0) 1 | plg_task_deleteactionlogs (5.0.0) 1 | plg_user_contactcreator (3.0.0) 0 | plg_user_token (3.9.0) 1 | plg_user_profile (3.0.0) 0 | plg_user_joomla (3.0.0) 1 | plg_user_terms (3.9.0) 0 | plg_privacy_consents (3.9.0) 1 | plg_privacy_user (3.9.0) 1 | plg_privacy_content (3.9.0) 1 | plg_privacy_actionlogs (3.9.0) 1 | plg_privacy_message (3.9.0) 1 | plg_multifactorauth_webauthn (4.2.0) 0 | plg_multifactorauth_yubikey (3.2.0) 0 | plg_multifactorauth_totp (3.2.0) 0 | plg_multifactorauth_email (4.2.0) 0 | plg_multifactorauth_fixed (4.2.0) 0 | plg_system_sef (3.0.0) 1 | plg_system_debug (3.0.0) 1 | plg_system_languagefilter (3.0.0) 0 | plg_system_webauthn (4.0.0) 1 | plg_system_guidedtours (4.3.0) 1 | plg_system_remember (3.0.0) 1 | plg_system_cache (3.0.0) 0 | plg_system_actionlogs (3.9.0) 1 | plg_system_stats (3.5.0) 0 | plg_system_redirect (3.0.0) 0 | plg_system_schedulerunner (4.1) 1 | plg_system_logout (3.0.0) 1 | plg_system_accessibility (4.0.0) 0 | plg_system_task_notification (4.1) 1 | plg_system_shortcut (4.2.0) 1 | plg_system_httpheaders (4.0.0) 1 | plg_system_jooa11y (4.2.0) 1 | plg_system_languagecode (3.0.0) 0 | plg_system_fields (3.7.0) 1 | plg_system_skipto (4.0.0) 1 | plg_system_log (3.0.0) 1 | plg_system_highlight (3.0.0) 1 | plg_system_schemaorg (5.0.0) 1 | plg_system_privacyconsent (3.9.0) 0 | plg_editors-xtd_menu (3.7.0) 1 | plg_editors-xtd_module (3.5.0) 1 | plg_editors-xtd_image (3.0.0) 1 | plg_editors-xtd_readmore (3.0.0) 1 | plg_editors-xtd_article (3.0.0) 1 | plg_editors-xtd_pagebreak (3.0.0) 1 | plg_editors-xtd_fields (3.7.0) 1 | plg_quickicon_privacycheck (3.9.0) 1 | plg_quickicon_eos (4.4.0) 1 | plg_quickicon_phpversioncheck (3.7.0) 1 | plg_quickicon_overridecheck (4.0.0) 1 | plg_quickicon_downloadkey (4.0.0) 1 | plg_quickicon_extensionupdate (3.0.0) 1 | plg_quickicon_joomlaupdate (3.0.0) 1 | plg_captcha_recaptcha_invisible (3.8) 0 | plg_extension_namespacemap (4.0.0) 1 | plg_extension_joomla (3.0.0) 1 | plg_extension_finder (4.0.0) 1 | Content - SP Page Builder (5.1.8) 1 | plg_content_pagenavigation (3.0.0) 1 | plg_content_emailcloak (3.0.0) 1 | plg_content_vote (3.0.0) 0 | plg_content_loadmodule (3.0.0) 1 | plg_content_joomla (3.0.0) 1 | plg_content_confirmconsent (3.9.0) 0 | plg_content_pagebreak (3.0.0) 1 | plg_content_fields (3.7.0) 1 | plg_content_finder (3.0.0) 1 | K2 - SP Page Builder (3.8.10) 0 | plg_filesystem_local (4.0.0) 1 | plg_authentication_ldap (3.0.0) 0 | plg_authentication_joomla (3.0.0) 1 | plg_authentication_cookie (3.0.0) 1 | plg_webservices_messages (4.0.0) 1 | plg_webservices_users (4.0.0) 1 | plg_webservices_config (4.0.0) 1 | plg_webservices_templates (4.0.0) 1 | plg_webservices_menus (4.0.0) 1 | plg_webservices_privacy (4.0.0) 1 | plg_webservices_media (4.1.0) 1 | plg_webservices_newsfeeds (4.0.0) 1 | plg_webservices_languages (4.0.0) 1 | plg_webservices_content (4.0.0) 1 | plg_webservices_redirect (4.0.0) 1 | plg_webservices_modules (4.0.0) 1 | plg_webservices_tags (4.0.0) 1 | plg_webservices_plugins (4.0.0) 1 | plg_webservices_installer (4.0.0) 1 | plg_webservices_banners (4.0.0) 1 | plg_fields_subform (4.0.0) 1 | plg_fields_usergrouplist (3.7.0) 1 | plg_fields_sql (3.7.0) 1 | plg_fields_text (3.7.0) 1 | plg_fields_user (3.7.0) 1 | plg_fields_color (3.7.0) 1 | plg_fields_media (3.7.0) 1 | plg_fields_editor (3.7.0) 1 | plg_fields_radio (3.7.0) 1 | plg_fields_calendar (3.7.0) 1 | plg_fields_textarea (3.7.0) 1 | plg_fields_imagelist (3.7.0) 1 | plg_fields_checkboxes (3.7.0) 1 | plg_fields_list (3.7.0) 1 | plg_fields_integer (3.7.0) 1 | plg_fields_url (3.7.0) 1 | plg_workflow_featuring (4.0.0) 1 | plg_workflow_notification (4.0.0) 1 | plg_workflow_publishing (4.0.0) 1 | plg_finder_contacts (3.0.0) 1 | plg_finder_newsfeeds (3.0.0) 1 | plg_finder_content (3.0.0) 1 | plg_finder_tags (3.0.0) 1 | plg_finder_categories (3.0.0) 1 | plg_schemaorg_organization (5.0.0) 1 | plg_schemaorg_jobposting (5.0.0) 1 | plg_schemaorg_book (5.0.0) 1 | plg_schemaorg_event (5.0.0) 1 | plg_schemaorg_blogposting (5.0.0) 1 | plg_schemaorg_article (5.1.0) 1 | plg_schemaorg_person (5.0.0) 1 | plg_schemaorg_custom (5.1.0) 1 | plg_schemaorg_recipe (5.0.0) 1 | plg_actionlog_joomla (3.9.0) 1 | plg_behaviour_versionable (4.0.0) 1 | plg_behaviour_taggable (4.0.0) 1 | plg_behaviour_compat (5.0.0) 1 | plg_installer_folderinstaller (3.6.0) 1 | plg_installer_urlinstaller (3.6.0) 1 | plg_installer_packageinstaller (3.6.0) 1 | plg_installer_override (4.0.0) 1 | plg_installer_webinstaller (4.0.0) 1 |
3rd Party:: SP Simple Portfolio - SP Page Build (5.1.8) ? | System - SP PageBuilder (5.1.8) 1 | System - SP Page Builder Pro Update (5.1.8) ? | System - Helix Ultimate Framework (2.1.1) 1 | PLG_QUICKICON_AKEEBABACKUP (9.9.11) 1 | plg_editors_tinymce (6.8.4) 1 | plg_editors_codemirror (6.0.0) 1 | plg_search_sppagebuilder (5.1.8) 0 | plg_finder_spsimpleportfolio (1.0.0) 1 | plg_finder_sppagebuilder (5.1.8) 0 |
Templates Discovered :: wrote:Templates :: Site :: cassiopeia (1.0) 1 | Crysa (2.0.9) 1 |
Templates :: Admin :: atum (1.0) 1 |

Was this a fix to my issue? I kinda new to this was looking through but it is so confusing. is it possible for you tell me which steps I need to follow?
Last edited by toivo on Thu Feb 13, 2025 9:01 pm, edited 1 time in total.
Reason: mod note: disabled smilies in post Options for readability

gsmela
Joomla! Explorer
Joomla! Explorer
Posts: 460
Joined: Thu Jun 10, 2010 12:38 pm

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by gsmela » Thu Feb 13, 2025 6:30 pm

LiveSite: Is Not Empty

That should be empty. Open the configuration.php file on the server and look for this line except yours will have a domain in between the quote marks. Remove that so it looks like this:

It will look something like this:
var $live_site = 'https://example.com';

You want to change it to:
var $live_site = '';

User avatar
Per Yngve Berg
Joomla! Master
Joomla! Master
Posts: 31667
Joined: Mon Oct 27, 2008 9:27 pm
Location: Romerike, Norway

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by Per Yngve Berg » Thu Feb 13, 2025 6:42 pm

error: Can't create more than max_prepared_stmt_count statements (current value: 100000)
This is a limitation set in the configuration of your database server

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 7:03 pm

gsmela wrote: Thu Feb 13, 2025 6:30 pm LiveSite: Is Not Empty

That should be empty. Open the configuration.php file on the server and look for this line except yours will have a domain in between the quote marks. Remove that so it looks like this:

It will look something like this:
var $live_site = 'https://example.com';

You want to change it to:
var $live_site = '';
I change it but it did not fix the issue.
You do not have the required permissions to view the files attached to this post.

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 7:05 pm

Per Yngve Berg wrote: Thu Feb 13, 2025 6:42 pm
error: Can't create more than max_prepared_stmt_count statements (current value: 100000)
This is a limitation set in the configuration of your database server

Yes i think its my host provider did something. Because they had some maintenance upgrade and from they did that upgrade my site is no longer reachable and then there are telling to fix the issue I have to upgrade my hosting plan to fix this.

User avatar
JAVesey
Joomla! Hero
Joomla! Hero
Posts: 2780
Joined: Tue May 14, 2013 1:21 pm
Location: Cardiff, Wales, UK
Contact:

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by JAVesey » Thu Feb 13, 2025 7:43 pm

KemarArt wrote: Thu Feb 13, 2025 7:05 pm Yes i think its my host provider did something. Because they had some maintenance upgrade and from they did that upgrade my site is no longer reachable and then there are telling to fix the issue I have to upgrade my hosting plan to fix this.
Whenever I get the “Whoops… 500…” message it’s usually because of a confict caused by a directive in the .htaccess file (which I note you’re using).

Try this:

1. Rename your .htaccess file to something like htaccess.bak (to keep a copy just in case)
2. Rename the standard Joomla htaccess.txt file to .htaccess

This will give you a default Joomla .htaccess file rather than one which might have modifications/server conflicts in it.

If it doesn’t help, reverse the process. Worth a try in my experience.
John V
Cardiff, Wales, UK
Joomla 5.2.5 "live" site on PHP 8.3.16 and MariaDB 10.11.10 (with b/c plugin enabled)
Joomla 5.2.5 on MAMP Pro 7.2.2 with PHP 8.3.14 and MySQL 8.0.40 (with b/c plugin enabled)

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Thu Feb 13, 2025 8:01 pm

JAVesey wrote: Thu Feb 13, 2025 7:43 pm
KemarArt wrote: Thu Feb 13, 2025 7:05 pm Yes i think its my host provider did something. Because they had some maintenance upgrade and from they did that upgrade my site is no longer reachable and then there are telling to fix the issue I have to upgrade my hosting plan to fix this.
Whenever I get the “Whoops… 500…” message it’s usually because of a confict caused by a directive in the .htaccess file (which I note you’re using).

Try this:

1. Rename your .htaccess file to something like htaccess.bak (to keep a copy just in case)
2. Rename the standard Joomla htaccess.txt file to .htaccess

This will give you a default Joomla .htaccess file rather than one which might have modifications/server conflicts in it.

If it doesn’t help, reverse the process. Worth a try in my experience.
I rename the .htaccess file but I am not seeing the default Joomla .htaccess in the pic below these are all the files in my root directory.
You do not have the required permissions to view the files attached to this post.

gws
Joomla! Champion
Joomla! Champion
Posts: 6607
Joined: Tue Aug 23, 2005 1:56 pm
Location: South coast, UK
Contact:

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by gws » Thu Feb 13, 2025 9:32 pm

Check if your file explorer on the server has show hidden files checked, usually in the options.

User avatar
toivo
Joomla! Master
Joomla! Master
Posts: 18077
Joined: Thu Feb 15, 2007 5:48 am
Location: Sydney, Australia

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by toivo » Thu Feb 13, 2025 9:44 pm

KemarArt wrote: Thu Feb 13, 2025 5:58 pm3rd Party:: SP Simple Portfolio - SP Page Build (5.1.8) ? | System - SP PageBuilder (5.1.8) 1 | System - SP Page Builder Pro Update (5.1.8) ?
Use phpMyAdmin or a similar utility from the cPanel, provided by your host, and edit the database table _extensions. Locate the rows that contain the plugins listed above and change the column 'enabled' from 1 to 0, then apply the changes. That will hopefully allow you to access the website.

The reason for this advice is the fact that SP Page Builder 5.1.8 was released on 10 November, 2023, less than a month after Joomla 5.0.0. It is likely that the plugins that came with it are no longer compatible with the current version of Joomla 5 and for some reason use excessive resources when accessing the database.

The latest version of SP Page Builder is 5.5.1, released last week. Once you get access to the backend of the website, you need to uninstall the plugin 'System - SP Page Builder Pro Update' and update the SP Page Builder free version, if that is the version you are using.
Toivo Talikka, Global Moderator

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Fri Feb 14, 2025 12:31 am

toivo wrote: Thu Feb 13, 2025 9:44 pm
KemarArt wrote: Thu Feb 13, 2025 5:58 pm3rd Party:: SP Simple Portfolio - SP Page Build (5.1.8) ? | System - SP PageBuilder (5.1.8) 1 | System - SP Page Builder Pro Update (5.1.8) ?
Use phpMyAdmin or a similar utility from the cPanel, provided by your host, and edit the database table _extensions. Locate the rows that contain the plugins listed above and change the column 'enabled' from 1 to 0, then apply the changes. That will hopefully allow you to access the website.

The reason for this advice is the fact that SP Page Builder 5.1.8 was released on 10 November, 2023, less than a month after Joomla 5.0.0. It is likely that the plugins that came with it are no longer compatible with the current version of Joomla 5 and for some reason use excessive resources when accessing the database.

The latest version of SP Page Builder is 5.5.1, released last week. Once you get access to the backend of the website, you need to uninstall the plugin 'System - SP Page Builder Pro Update' and update the SP Page Builder free version, if that is the version you are using.


These are the only 3 table I am seeing and only the crys_extensions table have something close to what you are taking about. I have provided a screenshot of that table below has well and I am not able to see SP Builder in that table
You do not have the required permissions to view the files attached to this post.
Last edited by toivo on Fri Feb 14, 2025 1:01 am, edited 1 time in total.
Reason: mod note: disabled smilies in post Options for readability

User avatar
toivo
Joomla! Master
Joomla! Master
Posts: 18077
Joined: Thu Feb 15, 2007 5:48 am
Location: Sydney, Australia

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by toivo » Fri Feb 14, 2025 1:00 am

It is the crys_extensions table. Click the right arrow > to browse to the next pages and locate the rows for the plugins.
next-pages.png
You do not have the required permissions to view the files attached to this post.
Toivo Talikka, Global Moderator

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Fri Feb 14, 2025 1:49 am

toivo wrote: Fri Feb 14, 2025 1:00 am It is the crys_extensions table. Click the right arrow > to browse to the next pages and locate the rows for the plugins.

next-pages.png
This are all the ones I find I when through all the pages and has you can see I 0 them all but I am still having the issue
You do not have the required permissions to view the files attached to this post.

User avatar
toivo
Joomla! Master
Joomla! Master
Posts: 18077
Joined: Thu Feb 15, 2007 5:48 am
Location: Sydney, Australia

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by toivo » Fri Feb 14, 2025 2:18 am

KemarArt wrote: Thu Feb 13, 2025 5:58 pm3rd Party:: System - SP PageBuilder (5.1.8) 1 | System - SP Page Builder Pro Update (5.1.8) ?
Locate the above two system plugins and disable them, too.
Toivo Talikka, Global Moderator

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Fri Feb 14, 2025 2:49 am

toivo wrote: Fri Feb 14, 2025 2:18 am
KemarArt wrote: Thu Feb 13, 2025 5:58 pm3rd Party:: System - SP PageBuilder (5.1.8) 1 | System - SP Page Builder Pro Update (5.1.8) ?
Locate the above two system plugins and disable them, too.

I found them and disable them has well but I am still getting the error
You do not have the required permissions to view the files attached to this post.
Last edited by toivo on Fri Feb 14, 2025 3:14 am, edited 1 time in total.
Reason: mod note: disabled smilies in post Options for readability

User avatar
toivo
Joomla! Master
Joomla! Master
Posts: 18077
Joined: Thu Feb 15, 2007 5:48 am
Location: Sydney, Australia

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by toivo » Fri Feb 14, 2025 3:36 am

KemarArt wrote: Thu Feb 13, 2025 2:10 pmerror: Can't create more than max_prepared_stmt_count statements (current value: 100000)
According to the MariaDB Knowledge Base, the default value for the variable max_prepared_stmt_count is 16382. Those default values are meant to work in most application environments. That makes 100000 look like an attempt to fix something.

Ref. https://mariadb.com/kb/en/server-system ... stmt_count

Do you happen to know what was the software your hosting provider updated in their servers?

Was the website updated to Joomla 5.2.3 before or after the host updated their servers? Which version of Joomla was the Joomla update done from?
Toivo Talikka, Global Moderator

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Fri Feb 14, 2025 2:26 pm

My website is back online now.

I want to thank you guys for all the help you provided but the issue was not with Joomla. It was with the hosting platform which I suspected form get go. Once they roll back the maintenance they did my site stared to work again.

KemarArt
Joomla! Apprentice
Joomla! Apprentice
Posts: 15
Joined: Thu Feb 13, 2025 1:56 am

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by KemarArt » Fri Feb 14, 2025 2:44 pm

I only want to ask one more thing here.

write not to get to my admin panel I have to do mywebsite/administrator.

how can I change the admin folder I trying by adding another folder but it field I feel I have to make changes else where

User avatar
toivo
Joomla! Master
Joomla! Master
Posts: 18077
Joined: Thu Feb 15, 2007 5:48 am
Location: Sydney, Australia

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by toivo » Fri Feb 14, 2025 9:11 pm

Good to hear that the website is now online.

There are third party extensions that use different methods to hide or protect the administrator folder, for example Admin Tools Professional.

If your web server is Apache, you could set up .htaccess and .htpasswd files by yourself, but, IMHO, the simplest way to protect the administrator folder is to use the cPanel feature called 'Directory Privacy', ref. https://docs.cpanel.net/cpanel/files/directory-privacy/.
Toivo Talikka, Global Moderator

User avatar
JAVesey
Joomla! Hero
Joomla! Hero
Posts: 2780
Joined: Tue May 14, 2013 1:21 pm
Location: Cardiff, Wales, UK
Contact:

Re: Server update broke site with "500 - Whoops, looks like something went wrong"

Post by JAVesey » Sun Feb 16, 2025 10:10 am

toivo wrote: Fri Feb 14, 2025 9:11 pm There are third party extensions that use different methods to hide or protect the administrator folder...
See this:
viewtopic.php?f=844&t=1014716
John V
Cardiff, Wales, UK
Joomla 5.2.5 "live" site on PHP 8.3.16 and MariaDB 10.11.10 (with b/c plugin enabled)
Joomla 5.2.5 on MAMP Pro 7.2.2 with PHP 8.3.14 and MySQL 8.0.40 (with b/c plugin enabled)

Advertisement

Post Reply

Return to “General Questions/New to Joomla! 5.x”