Code: #begin htf_report.txt ##### SERVER ##### IP-address (as per hostname): ***.***.***.*** [WARN] could not determine server's ip address by ifconfig [INFO] ISPConfig is installed. ##### ISPCONFIG ##### ISPConfig version is 3.1.11 ##### VERSION CHECK ##### [INFO] php (cli) version is 7.0.27-0+deb9u1 ##### PORT CHECK ##### [WARN] Port 8080 (ISPConfig) seems NOT to be listening [WARN] Port 443 (Webserver SSL) seems NOT to be listening [WARN] Port 25 (SMTP server) seems NOT to be listening [WARN] Port 465 (SMTP server SSL) seems NOT to be listening [WARN] Port 25 (SMTP server) seems NOT to be listening ##### MAIL SERVER CHECK ##### ##### RUNNING SERVER PROCESSES ##### [INFO] I found the following web server(s): Unknown process (nginx:) (PID 13028) [WARN] I could not determine which mail server is running. [INFO] I found the following pop3 server(s): Dovecot (PID 12948) [INFO] I found the following imap server(s): Dovecot (PID 12948) [INFO] I found the following ftp server(s): PureFTP (PID 13002) ##### LISTENING PORTS ##### (only () Local (Address) [anywhere]:993 (12948/dovecot) [anywhere]:995 (12948/dovecot) [localhost]:10023 (2812/postgrey) [localhost]:10024 (12923/amavisd-new) [localhost]:10026 (12923/amavisd-new) [localhost]:11211 (18255/memcached) [anywhere]:8333 (13028/nginx:) [anywhere]:110 (12948/dovecot) [anywhere]:143 (12948/dovecot) [anywhere]:80 (13028/nginx:) [anywhere]:8081 (13028/nginx:) ***.***.***.***:53 (13006/named) [localhost]:53 (13006/named) [anywhere]:21 (13002/pure-ftpd) [anywhere]:22 (2186/sshd) [localhost]:953 (13006/named) *:*:*:*::*:993 (12948/dovecot) *:*:*:*::*:995 (12948/dovecot) *:*:*:*::*:10023 (2812/postgrey) *:*:*:*::*:10024 (12923/amavisd-new) *:*:*:*::*:10026 (12923/amavisd-new) *:*:*:*::*:3306 (12842/mysqld) *:*:*:*::*:8333 (13028/nginx:) [localhost]10 (12948/dovecot) [localhost]43 (12948/dovecot) *:*:*:*::*:80 (13028/nginx:) *:*:*:*::*:8081 (13028/nginx:) *:*:*:*::*:53 (13006/named) *:*:*:*::*:21 (13002/pure-ftpd) *:*:*:*::*:22 (2186/sshd) *:*:*:*::*:953 (13006/named) ##### IPTABLES ##### Chain INPUT (policy ACCEPT) target prot opt source destination f2b-postfix-sasl tcp -- [anywhere]/0 [anywhere]/0 multi port dports 25 f2b-dovecot tcp -- [anywhere]/0 [anywhere]/0 multiport dports 110,995,143,993,587,465,4190 f2b-pure-ftpd tcp -- [anywhere]/0 [anywhere]/0 multipor t dports 21 f2b-sshd tcp -- [anywhere]/0 [anywhere]/0 multiport dp orts 22 Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain f2b-dovecot (1 references) target prot opt source destination RETURN all -- [anywhere]/0 [anywhere]/0 Chain f2b-postfix-sasl (1 references) target prot opt source destination RETURN all -- [anywhere]/0 [anywhere]/0 Chain f2b-pure-ftpd (1 references) target prot opt source destination RETURN all -- [anywhere]/0 [anywhere]/0 Chain f2b-sshd (1 references) target prot opt source destination RETURN all -- [anywhere]/0 #end htf_report.txt ISPConfig configured to port 8333 during installation I've followed this tutorial https://www.howtoforge.com/tutorial...-9-stretch-apache-bind-dovecot-ispconfig-3-1/ to install ISPConfig but i've installed it with nginx webserver! First what i see is this: I get a NET::ERR_CERT_AUTHORITY_INVALID error. Is this normal...? Can a hacker that is listening on this ip adress and port catch my login credentials? It says here: This connection is unsecure when i go to the ISPConfig Login page. But i have installed ISPConfig with a secure connection (SSL)!!!? Second: the SMPT deamon is not running even when i restart the system... #Please move this thread to the following forum: https://www.howtoforge.com/community/forums/installation-configuration.27/
Yes. This just means that you use a self-signed SSL cert. No. The encryption of a self-signed ssl connection is as secure as any other ssl encryption. It's just about the authority which created the SSL cert which is you in this case. The message in the browser is not quite accurate in this regard as it is intended towards end users, when a end user would find a self signed ssl cert when he connects to his bank, then the connection is broken indeed, but when you created your own ssl cert, then you know that you created it so that's ok as encryption is the same. But you can also install a free let's encrypt ssl cert to get rid of that warning. https://www.ispconfig.org/blog/securing-ispconfig-3-1-free-lets-encrypt-ssl-certificate/
