cat /etc/os-release
NAME=“Ubuntu”
VERSION=“20.04.3 LTS (Focal Fossa)”
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=“Ubuntu 20.04.3 LTS”
VERSION_ID=“20.04”
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
Hestia Control Panel:
v1.4.13
nginx -v
nginx version: nginx/1.21.3
nano /var/log/nginx/error.log
shows no error today.
I didn’t make any changes to config files, always was using wordpress template provided by hestia cp for nginx, And all updates went fine before from cronjobs.
Only that website is not working or any other?
Dit you try restarting nginx?
There is total 3 domains and all of them returns same message. 2 domains on one user, 1 domain on a separate user account.
webmail subdomain do the same.
Nginx restarts without any error.
Is there a way to roll back to version v1.4.12?
No, Also we haven’t changed any thing regarding web…
What happens when you rebuild the user
v-rebuild-web-domains user
Nothing happened. Did to both users. Clean finish without any message.
At the moment I removed ssl not to mess with ssl conf too.
From back up: /home/user/conf/web/domain.lt/nginx.conf looks identical as the one on server.
Same file at /etc/nginx/conf.d/domains/domain.lt.conf
root /home/user/web/domain.lt/public_html;
what else can be that nginx started to read from a wrong root?
How many different websites do you have. Have them all issues or only a few?
Indicates the config for the domain does not exists…
I got 3 website on this server.
All of them suddenly gave me same landing page today.
http://ip/phpmyadmin 404 error
http://domain.lt/phpmyadmin 404 error
nginx.conf
user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log notice;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
sendfile on;
#tcp_nopush on;
keepalive_timeout 65;
#gzip on;
include /etc/nginx/conf.d/*.conf;
}
it include /etc/nginx/conf.d/*.conf;
What other conf files you need to see from conf.d?
You also replaced then nginx during the update when nginx also updated
Remove nginx.conf and use:
That’s it thanks…
But that I didn’t made any changes to nginx.conf file.
After update it will be change and I could get same problem? If yes where is the nginx.conf file location that westa use to overwrite?
The only reason nginx.conf will be overwritten, is during the upgrade over apt-get upgrade - hestia doesnt touch the nginx.conf file.
Hmm strange. After I got a message “Your new web server is ready to use.” I did login to ssh and used commands.
apt-get update
apt-get upgrade
next time will know 
thanks for support. You guys are best
my i know… you do this on root or on admin hestia ?
upgrading the system? usualy root, can be done aswell on admin but you need to run sudo infront.
Replace /etc/nginx/nginx.conf with https://github.com/hestiacp/hestiacp/blob/main/install/deb/nginx/nginx.conf
then systemctl restart nginx
But u need to get someone which help you out or switch to a shared webhosting, it sounds like a big lack of strongly needed knowledge.
Thks I have backup all my file, so i think the big risk is doesn’t matter. I want to try your suggest
Great, i have done your suggest and it is succes. 
all be normal. I edit using winscp and copy the code from your here : https://github.com/hestiacp/hestiacp/blob/main/install/deb/nginx/nginx.conf
and then after that, i restart nginx
once again …thks very much… i proud can do it by my self
keep healthy for all Team dev of hestia
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
