I have made sure to immigrate to the nginx server and set up the requirements I need to run WordPress site:
Here is the server I am currently running my WordPress site on:
Nginx
Ubuntu 22.04
Hestia Control Panel v1.8.8
My question is why I always see We’re working on it! page even though I hadn’t touched the website file? Is there any thing I investigate further to check where the error is?
Are you sure you assigned Web template wordpress to your site in Hestia?
You could check the nginx logs:
/home/USER/web/DOMAIN/logs/
As you can see, I’ve chosen WordPress template for nginx
and here is the error I’ve found in the error.log
2023/10/02 10:11:28 [error] 193520#193520: *2275 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.38.22.71, se>
2023/10/02 21:33:55 [error] 193520#193520: *4485 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 41.216.188.92, s>
2023/10/02 22:04:16 [error] 193520#193520: *4619 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.23, >
2023/10/02 22:04:17 [error] 193520#193520: *4621 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.23, >
2023/10/02 22:04:17 [error] 193520#193520: *4623 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.23, >
2023/10/02 22:04:17 [error] 193520#193520: *4625 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.23, >
2023/10/02 22:04:18 [error] 193520#193520: *4627 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.23, >
2023/10/02 22:04:18 [error] 193520#193520: *4629 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.23, >
2023/10/02 23:33:07 [error] 193520#193520: *4964 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.93, >
2023/10/02 23:33:19 [error] 193520#193520: *4966 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.93, >
2023/10/02 23:33:29 [error] 193520#193520: *4970 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.93, >
2023/10/02 23:33:39 [error] 193520#193520: *4972 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.93, >
2023/10/02 23:33:53 [error] 193520#193520: *4976 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 194.169.175.93, >
2023/10/03 04:42:45 [error] 193520#193520: *5964 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 80.208.234.133, >
2023/10/03 08:10:55 [error] 469445#469445: *6613 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 20.81.219.37, se>
2023/10/03 08:10:55 [error] 469445#469445: *6615 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 20.81.219.37, se>
2023/10/03 08:11:18 [error] 469445#469445: *6617 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 20.81.219.37, se>
2
ls /home/user/web/domain.com/public_html/
It looks like index.php doesn’t exists yet
@Hussein
It is nginx configuration giving preference to .html BEFORE .php
IF both index.html AND index.php (wordpress) are present.
SOLVE it:
a) delete index.htm OR rename it to index.hestia
b) change your nginx configuration to load .php FIRST
ONE of the two will do…
good luck
PS: AND if you have apache2 as the backend ADD a configuration overide as follows
# -------------------------------------------------------------------------------------------
# edit/create this file nano /etc/apache2/conf.d/Dir1PHP.conf
# -------------------------------------------------------------------------------------------
# IMPORTANT this directive is to override previous settings.../default in
# /etc/apache2/mods-enabled/dir.conf (putting it HERE survives upgrades...)
# NOTE: apache default handling is to just ADD to the list which will not give the required change
# HENCE we must first clear the list with 'disabled' option!
# -------------------------------------------------------------------------------------------
DirectoryIndex disabled
DirectoryIndex index.php index.cgi index.html index.pl index.xhtml index.htm