After manually stopping nginx or hestia service via “systemctl stop …”, I am unable to make both of them work.
As it warns me about 8083 port being in use.
If I comment out the server part of handling the 8083 in /etc/nginx/nginx.conf then I can make them run.
But I need to block any request coming to the port 8083 for a certain domain. So I really need to make this config work.
I tried uncommenting that part and stopping both nginx and hestia services.
I checked the codes of /etc/init.d/hestia, so I ran ./hestia start but no help
You shouldn’t have anything related to port 8083 in /etc/nginx/nginx.conf, that Nginx doesn’t manage Hestia’s port. That port is managed by hestia service running its own Nginx and the conf is here /usr/local/hestia/nginx/conf/
How about configuring and changing port Hestia uses to the one of your choice with the following command:
v-change-sys-port PortNumber
You can do anything you want in the nginx.conf for all kinds of blocking. As both these servers are seperated through different ports, they can’t have any conflicts after running the above command and changing it forcefully.
Thank you for everybody.
Seems like it was completely my mistake.
I thought the /etc/nginx/nginx.conf had the 8083 configuration in it by default.
But then I checked HestiaCP Github Nginx Conf and didn’t see it there.
As @sahsanu said, it was managed in /usr/local/hestia/nginx/conf/nginx.conf file.
So I was able to limit the access to the panel only for a specific domain name via that file