New Website Installation Problem - 404 Error

Support and Discussion Web Server
, ,
1

Hi Guys,

@usmannasir,

I’m facing a Big Issue for two weeks with a new installation of a WordPress website.

Yesterday, I updated Cyberpanel to version 2.3, but nothing changed.

Cyberpanel Current Version: 2.3
Build: 5Current Commit: f5008094520cce6524435c867f452de3915c993e
Latest Version: 2.3
Latest Build: 5Latest Commit: f5008094520cce6524435c867f452de3915c993e
OS: Ubuntu 22.04

  1. I completed the first step of the standard installation through Cyberpanel.
  2. I already had the website running on another server, which has a system developed in WP running on Cyberpanel.
  3. After creating the Website in Cyberpanel, I uploaded the files directly to the ROOT directory through Cyberpanel as soon as the directory was created via the standard Cyberpanel installation. actual Path: /home/website.com/public_html
  4. First problem: The site is down. When I access the URL, it shows a 404 page.
  5. Second problem: I have enabled all three DEBUG configurations available in wp-config.php file, but the Log files are NOT being generated in the default directory within WP. Therefore, I cannot read what is happening with the installed files. I am using PHP 8.2 and the display_errors module is also enabled to display any error messages, but nothing is shown in the browser.
  6. Third problem: I have run a PING on the URL and received a positive response from the server. The VPS server is running normally, but the Website is not loading in the browser.
  7. Fourth problem: I was using the Wordfence Firewall, but I have already renamed and disabled the folder within the Plugin directory to ensure it is not causing the issue.
  8. Fifth problem: I have recreated the .htaccess file, but it does not seem to be the cause of the problem either.
  9. Sixth problem: I have reboot both servers, VPS and openlitespeed servers a hundred of times and this is not Problem.
    Again, I uploaded a 100% of the website files directly into the Root folder. Could this be the problem?
  10. Seventh: I have already cleared the cache of the following directory via ssh, but this does not seem to be the problem. /usr/local/lsws/cachedata

What can I do beyond what I have already done to debug the error?

What can I enable or disable to see any error messages and find out what is causing the error?

I appreciate any help in advance.