Many hackers will use a port scanner to probe your system for specific ports and at a slow rate which may allow them to evade your auto block feature. Seafile installation process should be changed or better documented. To my system, every port after 50 will appear closed, but to a hacker starting their port scan against you at port 80 will see that it is really wide open. Since I have installed Seafile always with Apache proxy before it’s the first time I faced this issue. because you use VPN, like I do), than change file /seafile-install-path/seafile/haiwen/conf/nf like that: If you want to access Seafile directly by port 8000 (e.g.

If you want to access Seafile by Nginx HTTP proxy (which is the best and common way, I admit, because you want to use secure https), than leave everthing in Seafile as it is and configure Nginx as proxy following the steps of the official documentation. However, accessing Seafile by port 8000 is the out-of-the-box configuration which is decribed in the documention as immediately working after installation. They determine this by sending client requests to ports on a host (an IP. Port scanners test open ports and display the ones open for communication. These tools are used to scan for vulnerabilities, because open ports can act as security holes attackers may exploit. On the next page, click 'Allow the Connection' and then click 'Next. If you need to open a range of ports, use a hyphen (-). If you're opening more than one port, you can separate them by commas.

Indeed it was NOT an issue of Hestia or firewall but of Seafile.īy default Seafile installation binds to “127.0.0.1:8000” in file nf which works with further configuration of Nginx as HTTP proxy but not with direct access via port 8000 ( ). An open port scanner tool is designed to scan a server or a host for open ports. Nmap is the world’s leading port security network scanner. Select the 'Specific Local Ports' option and then type the port number into the field provided. Restarting iptables by the panel button had no effect, neither rebooting the server. Nmap done: 1 IP address (1 host up) scanned in 1.63 seconds RULE=‘12’ ACTION=‘ACCEPT’ PROTOCOL=‘TCP’ PORT=‘8080’ IP=‘0.0.0.0/0’ COMMENT=‘Seafdav’ SUSPENDED=‘no’ TIME=‘23:01:59’ DATE=‘’ iptables -L -vĠ 0 ACCEPT tcp - any any anywhere anywhere tcp dpt:8080Ģ 104 ACCEPT tcp - any any anywhere anywhere tcp dpt:8000Įverything seems to be o.k., but besides refused connections nmap doesn’t list the ports open: nmap -p 8000-9000

A INPUT -p tcp -m tcp -dport 8000 -j ACCEPT A INPUT -p tcp -m tcp -dport 8080 -j ACCEPT I opened two ports in the panel (8000 tcp and 8080 tcp) but connections are refused.īoth files /etc/les and /usr/local/hestia/data/firewall/nf seem to have been properly updated: Setting up “Seafile” on my test server took me to a new problem with Hestia CP:

Scan my firewall for open ports