8083 port already in use

Community Support
1

Currently installed version: v1.9.3

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

2

reboot ok？

3

I tried to reboot 2 days ago but got the same result.
If you have any questions for me to show the configs, I can provide them

4

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/

5

image
image2162×1352 361 KB

here’s what I get if I uncomment that part in /etc/nginx/nginx.conf and try to start the hestia service

6

turn off your server and reboot.

7

image
image2520×1576 427 KB

image
image2234×1600 278 KB

I have done it but same result. Just so you know I use a digital ocean droplet, but it might not be relevant

8

You need to fix nginx not booting and you can view the error log

9

Hi,

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.