Web Site wont load after alias/subdomain was removed
Hi,
We have a web site that we tried to upgrade to PHP 8.3. After doing this we noticed a couple of pages with errors. The web master was looking into it and supposedly resolved the issue. During this time he had us remove their staging site which had it's own document root from what I could tell. After deleting this sub domain or whatever you want to call it, the main site will not function, doesn't load at all. 505 error I believe. He put back the staging site, and that works but the main site still will not load. He can't figure it out. He said, "From what we can tell, there's a configuration error with cPanel, which controls the server on which the site lives."
More info below...
-
One thing I noticed is that when you try to bring up the site it shows a "wordpress" icon on the tab in the browser.
Also, the Chrome browser shows: (firefox comes up with nothing).
This page isn’t working
example.com is currently unable to handle this request.
HTTP ERROR 5000 -
WP Toolkit shows the site as "broken" and one of the errors is, "[error]FailedToExecuteWpCliCommand: exit status 254[/error] Parse error: syntax error, unexpected 'define' (T_STRING) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1343) : eval()'d code on line 37"
0 -
Another error:
Site data was not refreshed due to the following error: Failed to reset cache for the instance #7: Fatal error: Uncaught Error: Undefined constant "THEME_NAME" in /home/bmda/public_html/staging/wp-content/themes/jupiter-child/framework/metaboxes/metabox-pages.php:8 Stack trace: #0 /home/bmda/public_html/staging/wp-content/plugins/jupiter-donut/includes/meta-boxes/class.php(1086): include_once() #1 /home/bmda/public_html/staging/wp-content/plugins/jupiter-donut/includes/meta-boxes/class.php(1094): mk_load_metaboxes() #2 /home/bmda/public_html/staging/wp-content/plugins/jupiter-donut/jupiter-donut.php(463): require_once('/home/bmda/publ...') #3 /home/bmda/public_html/staging/wp-content/plugins/jupiter-donut/jupiter-donut.php(183): Jupiter_Donut->load_files(Array) #4 /home/bmda/public_html/staging/wp-includes/class-wp-hook.php(324): Jupiter_Donut->{closure}('') #5 /home/bmda/public_html/staging/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #6 /home/bmda/public_html/staging/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /home/bmda/public_html/staging/wp-settings.php(643): do_action('init') #8 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1383): require('/home/bmda/publ...') #9 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1302): WP_CLI\Runner->load_wordpress() #10 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start() #11 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState)) #12 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap() #13 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('/usr/local/cpan...') #14 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/wpt-wp-cli.php(31): require_once('/usr/local/cpan...') #15 Command line code(1): require('/usr/local/cpan...') #16 {main} thrown in /home/bmda/public_html/staging/wp-content/themes/jupiter-child/framework/metaboxes/metabox-pages.php on line 8 Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website. [error]FailedToExecuteWpCliCommand: exit status 1[/error] . Cache tags: ["action-log-existence","main-information","ip","ssl-statuses","remote-agent-instance","cloud-linux-cagefs","cpanel-links","admin-credentials","admin-login-link","php","plugins","themes","config","nginx-caching","maintenance-mode","table-prefix","force-updates","security-measures","protected-dir","screenshot","virtual-patches","available-minor-update-version"]
0 -
Not sure how deleting the subdomain caused the main site to crash when they had separate document roots and supposedly the document root for the subdomain wasn't deleted during the process. The web developer is just going to reload the web site and see if that works.
0 -
Web designer reloaded the site and its working fine now. It's also working with PHP 8.3. He deleted the staging site (subdomain) again. Apparently removing it the first time wasn't the cause of the main site to crash. He doesn't know what caused the issue but the reload fixed it.
0 -
I'm glad you were able to get that working! It sounds like the wrong files were removed, as cPanel configurations don't suddenly make a site stop working right after an admin makes changes ;)
0
Please sign in to leave a comment.
Comments
6 comments