ISPConfig access

Discussion in 'Installation/Configuration' started by Creps, Jun 16, 2023.

  1. Creps

    Creps New Member

    Hello guys, I'm a beginner with the ISPConfig and Postfix. So, my apologies for any dumb question here.
    At my boss's request, I installed ISPConfig on a CentOS 8 machine on AWS some time ago. I did some tests and can't send emails at all.
    Checking this forum's posts, I've found some really nice tips about how to make things work.
    But due to a carelessness of mine, I forgot how to access the IPSConfig control panel. I've tried to access using:
    • https:// hotsname.com :8080
    • http:// hotsname.com :8080
    • https:// ipaddress :8080
    • http:// ipaddress :8080
    Also tried with "/login" at the end and with the 80 and 81 ports, no results at all.
    I'd be very grateful for any tip on how to access the panel again, how to change the access URL or even how to clean up the installation so I can reinstall it without any bugs.
    Thank you very much.
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Any of the https:// URL's will work as ISPConfig listens on all IP's and domains o port 8080, with IP you will get an SSL error though as SSL certs are for domains and not an IP. If its not on port 8080, then you either changed the port manually or the web server is not started (or your IP or hostname does not point to an ISPConfig server). You can e.g. check with:

    netstat -ntap | grep 8080

    if there is a process listening on that port.

    In case you want to reinstall, use Debian 11 (12 not supported yet) or Ubuntu 22.04 and not CentOS. Debian and Ubuntu are the recommended distributions, installations are much easier and more stable than on centOS. Plus you can install it automatically using the auto installer: https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/
     
  3. Creps

    Creps New Member

    Thank you for the answer, but since that my boss's told me to, I really need to use CentOS. =(
    I tried netstat -ntap | grep 8080 but the command wasn't found. Then I tried sudo yum install net-tools and got the "Killed" result.
    Is there any way to change the access URL?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

  5. Creps

    Creps New Member

    We have many CentOS servers on the company I work, all with WHM/cPanel and EXIM running, with which I have some more experience. So my boss's to get rid of many cPanel's bugs choose ISPConfig, and of EXIM's bugs choose Postfix, and asked me to learn how to configure a server with this tools from scratch.

    I've installed the server with apache as my web service.

    Here's the output of my test script:

    Code:
    ##### SERVER #####
    IP-address (as per hostname): [localhost]
    [WARN] could not determine server's ip address by ifconfig
    [INFO] OS version is CentOS Stream release 8
    
    [INFO] uptime:  17:03:58 up  5:21,  1 user,  load average: 0.00, 0.00, 0.00
    
    [INFO] memory:
                  total        used        free      shared  buff/cache   available
    Mem:          808Mi       329Mi       249Mi        25Mi       229Mi       338Mi
    Swap:            0B          0B          0B
    
    [INFO] systemd failed services status:
      UNIT                  LOAD   ACTIVE SUB    DESCRIPTION
    ● dnf-makecache.service loaded failed failed dnf makecache
    
    LOAD   = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB    = The low-level unit activation state, values depend on unit type.
    
    1 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    
    [INFO] No ISPConfig found.
    
    ##### VERSION CHECK #####
    
    [INFO] php (cli) version is 8.1.17
    [INFO] php-cgi (used for cgi php in default vhost!) is version 8.1.17
    
    ##### PORT CHECK #####
    
    [WARN] Port 80 (Webserver) seems NOT to be listening
    [WARN] Port 443 (Webserver SSL) seems NOT to be listening
    [WARN] Port 143 (IMAP server) seems NOT to be listening
    [WARN] Port 993 (IMAP server SSL) seems NOT to be listening
    [WARN] Port 110 (POP3 server) seems NOT to be listening
    [WARN] Port 995 (POP3 server 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 21 (FTP server) seems NOT to be listening
    [WARN] Port 22 (SSH server) seems NOT to be listening
    [WARN] Port 25 (SMTP server) seems NOT to be listening
    
    ##### MAIL SERVER CHECK #####
    
    [WARN] I found no "submission" entry in your postfix master.cf
    [INFO] this is not critical, but if you want to offer port 587 for smtp connections you have to enable this.
    [WARN] I found no "smtps" entry in your postfix master.cf
    [INFO] this is not critical, but if you want to offer SSL for smtp (not TLS) connections you have to enable this.
    
    ##### RUNNING SERVER PROCESSES #####
    
    [WARN] I could not determine which web server is running.
    [WARN] I could not determine which mail server is running.
    [WARN] I could not determine which pop3 server is running.
    [WARN] I could not determine which imap server is running.
    [WARN] I could not determine which ftp server is running.
    
    ##### LISTENING PORTS #####
    
    
    
    
    ##### IPTABLES #####
    
    
    
    
    ##### LET'S ENCRYPT #####
    
    
    
    
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Did you run the test script as root user?

    And if he would have chosen Debian 11 or Ubuntu 22.04 as basis, he would have got rid of the CentOS issues as well :) The main problem of CentOS and other RHEL derivates is the lack of a central repository that provides all packages in a uniform way. Yes, there is Epel and Remi but it does not match stability-wise what you get with Debian and Ubuntu as a platform.
     
  7. Creps

    Creps New Member

    Yes, I run the command logged as the root user.

    I really didn't know that. Even not knowing if he will accept, surely I'll suggest that we change the CentOS too.
     
  8. Creps

    Creps New Member

    Man, sorry, I made a mistake, the server distro is already Ubuntu. I was reading a tutorial on How to Forge named "The Perfect Server CentOS 8 with Apache, PHP, Postfix, Dovecot, Pure-FTPD, BIND and ISPConfig 3.2" and got confused.
    Now I'm able to access using my ip address with https. I'll search in the topics something to help me with the mail sending problem.
    Just a question, is there a way to access using the subdomain that I define as host?
    Just if you need, there's my test script results:
    Code:
    ##### SERVER #####
    IP-address (as per hostname): ***.***.***.***
    [WARN] could not determine server's ip address by ifconfig
    [INFO] OS version is Ubuntu 20.04.6 LTS
    
    [INFO] uptime:  19:07:09 up 66 days,  6:31,  1 user,  load average: 0.02, 0.07, 0.05
    
    [INFO] memory:
                  total        used        free      shared  buff/cache   available
    Mem:          976Mi       450Mi        82Mi        11Mi       443Mi       358Mi
    Swap:            0B          0B          0B
    
    [INFO] systemd failed services status:
      UNIT LOAD ACTIVE SUB DESCRIPTION
    0 loaded units listed.
    
    [INFO] ISPConfig is installed.
    
    ##### ISPCONFIG #####
    ISPConfig version is 3.2.9p1
    
    
    ##### VERSION CHECK #####
    
    [INFO] php (cli) version is 7.4.3-4ubuntu2.18
    [INFO] php-cgi (used for cgi php in default vhost!) is version 7.4.3
    
    ##### PORT CHECK #####
    
    [WARN] Port 465 (SMTP server SSL) seems NOT to be listening
    
    ##### MAIL SERVER CHECK #####
    
    [WARN] I found no "submission" entry in your postfix master.cf
    [INFO] this is not critical, but if you want to offer port 587 for smtp connections you have to enable this.
    [WARN] I found no "smtps" entry in your postfix master.cf
    [INFO] this is not critical, but if you want to offer SSL for smtp (not TLS) connections you have to enable this.
    
    ##### RUNNING SERVER PROCESSES #####
    
    [INFO] I found the following web server(s):
            Apache 2 (PID 685331)
    [INFO] I found the following mail server(s):
            Postfix (PID 1633278)
    [INFO] I found the following pop3 server(s):
            Dovecot (PID 104654)
    [INFO] I found the following imap server(s):
            Dovecot (PID 104654)
    [INFO] I found the following ftp server(s):
            PureFTP (PID 106553)
    
    ##### LISTENING PORTS #####
    (only           ()
    Local           (Address)
    [anywhere]:993          (104654/dovecot)
    [anywhere]:995          (104654/dovecot)
    [localhost]:11211               (73428/memcached)
    [anywhere]:110          (104654/dovecot)
    [anywhere]:143          (104654/dovecot)
    ***.***.***.***:53              (108140/named)
    ***.***.***.***:53              (108140/named)
    ***.***.***.***:53              (108140/named)
    [localhost]:53          (108140/named)
    [anywhere]:21           (106553/pure-ftpd)
    ***.***.***.***:53              (12098/systemd-resol)
    [anywhere]:22           (817/sshd:)
    [anywhere]:25           (1633278/master)
    [localhost]:953         (108140/named)
    *:*:*:*::*:993          (104654/dovecot)
    *:*:*:*::*:995          (104654/dovecot)
    *:*:*:*::*:3306         (100537/mysqld)
    [localhost]10           (104654/dovecot)
    [localhost]43           (104654/dovecot)
    *:*:*:*::*:8080         (685331/apache2)
    *:*:*:*::*:80           (685331/apache2)
    *:*:*:*::*:8081         (685331/apache2)
    *:*:*:*::*4c1f:f0ff:fe8d:53             (108140/named)
    *:*:*:*::*389a:3eff:fe7c:53             (108140/named)
    *:*:*:*::*:53           (108140/named)
    *:*:*:*::*:21           (106553/pure-ftpd)
    *:*:*:*::*:22           (817/sshd:)
    *:*:*:*::*:25           (1633278/master)
    *:*:*:*::*:953          (108140/named)
    *:*:*:*::*:443          (685331/apache2)
    
    
    
    
    ##### IPTABLES #####
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    f2b-dovecot-pop3imap  tcp  --  [anywhere]/0            [anywhere]/0            multiport dports 110,995,143,993
    f2b-pure-ftpd  tcp  --  [anywhere]/0            [anywhere]/0            multiport dports 21
    f2b-sshd   tcp  --  [anywhere]/0            [anywhere]/0            multiport dports 22
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    
    Chain f2b-dovecot-pop3imap (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            [anywhere]/0
    
    
    
    
    ##### LET'S ENCRYPT #####
    Certbot is installed in /usr/bin/letsencrypt
    
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    That's the default already. Maybe you missed pointing this subdomain to the server before installing ISPConfig? The next steps are:

    1) Check that you pointed this subdomain to the right server in DNS.
    2) Check that you configured it correctly in the os of the server, you can do that with the command:

    hostname -f

    it must show the correct fully qualified domain name of the server, e.g.: server1.example.com

    2) If 1 + 2 are correct, run:

    ispconfig_update.sh --force

    to update ISPConfig and chose to reconfigure services during update. When the updater asks to create a new SSL cert, choose yes.

    Regarding your mail problem, seems as if postfix was not configured before you installed ISPConfig, most likely, you used one of the manual install guides and missed that step to configure master.cf and not the auto-installer, which does it automatically. Post the content of the file /etc/postfix/master.cf
     
  10. Creps

    Creps New Member

    Sorry for the delay in answering, and thank you for all the support you have given me.
    Here's my /etc/postfix/master.cf content:
    Code:
    #
    # Postfix master process configuration file.  For details on the format
    # of the file, see the master(5) manual page (command: "man 5 master" or
    # on-line: http://www.postfix.org/master.5.html).
    #
    # Do not forget to execute "postfix reload" after editing this file.
    #
    # ==========================================================================
    # service type  private unpriv  chroot  wakeup  maxproc command + args
    #               (yes)   (yes)   (no)    (never) (100)
    # ==========================================================================
    smtp      inet  n       -       y       -       -       smtpd
    #smtp      inet  n       -       y       -       1       postscreen
    #smtpd     pass  -       -       y       -       -       smtpd
    #dnsblog   unix  -       -       y       -       0       dnsblog
    #tlsproxy  unix  -       -       y       -       0       tlsproxy
    #submission inet n       -       y       -       -       smtpd
      -o syslog_name=postfix/submission
      -o smtpd_tls_security_level=encrypt
      -o smtpd_sasl_auth_enable=yes
      -o smtpd_tls_auth_only=yes
      -o smtpd_client_restrictions=permit_sasl_authenticated,reject
    #  -o smtpd_reject_unlisted_recipient=no
    #  -o smtpd_client_restrictions=$mua_client_restrictions
    #  -o smtpd_helo_restrictions=$mua_helo_restrictions
    #  -o smtpd_sender_restrictions=$mua_sender_restrictions
    #  -o smtpd_recipient_restrictions=
    #  -o smtpd_relay_restrictions=permit_sasl_authenticated,reject
    #  -o milter_macro_daemon_name=ORIGINATING
    #smtps     inet  n       -       y       -       -       smtpd
      -o syslog_name=postfix/smtps
      -o smtpd_tls_wrappermode=yes
      -o smtpd_sasl_auth_enable=yes
      -o smtpd_client_restrictions=permit_sasl_authenticated,reject
    #  -o smtpd_reject_unlisted_recipient=no
    #  -o smtpd_client_restrictions=$mua_client_restrictions
    #  -o smtpd_helo_restrictions=$mua_helo_restrictions
    #  -o smtpd_sender_restrictions=$mua_sender_restrictions
    #  -o smtpd_recipient_restrictions=
    #  -o smtpd_relay_restrictions=permit_sasl_authenticated,reject
    #  -o milter_macro_daemon_name=ORIGINATING
    #628       inet  n       -       y       -       -       qmqpd
    pickup    unix  n       -       y       60      1       pickup
    cleanup   unix  n       -       y       -       0       cleanup
    qmgr      unix  n       -       n       300     1       qmgr
    #qmgr     unix  n       -       n       300     1       oqmgr
    tlsmgr    unix  -       -       y       1000?   1       tlsmgr
    rewrite   unix  -       -       y       -       -       trivial-rewrite
    bounce    unix  -       -       y       -       0       bounce
    defer     unix  -       -       y       -       0       bounce
    trace     unix  -       -       y       -       0       bounce
    verify    unix  -       -       y       -       1       verify
    flush     unix  n       -       y       1000?   0       flush
    proxymap  unix  -       -       n       -       -       proxymap
    proxywrite unix -       -       n       -       1       proxymap
    smtp      unix  -       -       y       -       -       smtp
    relay     unix  -       -       y       -       -       smtp
            -o syslog_name=postfix/$service_name
    #       -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
    showq     unix  n       -       y       -       -       showq
    error     unix  -       -       y       -       -       error
    retry     unix  -       -       y       -       -       error
    discard   unix  -       -       y       -       -       discard
    local     unix  -       n       n       -       -       local
    virtual   unix  -       n       n       -       -       virtual
    lmtp      unix  -       -       y       -       -       lmtp
    anvil     unix  -       -       y       -       1       anvil
    scache    unix  -       -       y       -       1       scache
    postlog   unix-dgram n  -       n       -       1       postlogd
    #
    # ====================================================================
    # Interfaces to non-Postfix software. Be sure to examine the manual
    # pages of the non-Postfix software to find out what options it wants.
    #
    # Many of the following services use the Postfix pipe(8) delivery
    # agent.  See the pipe(8) man page for information about ${recipient}
    # and other message envelope options.
    # ====================================================================
    #
    # maildrop. See the Postfix MAILDROP_README file for details.
    # Also specify in main.cf: maildrop_destination_recipient_limit=1
    #
    maildrop  unix  -       n       n       -       -       pipe
      flags=DRhu user=vmail argv=/usr/bin/maildrop -d vmail ${extension} ${recipient} ${user} ${nexthop} ${sender}
    #
    # ====================================================================
    #
    # Recent Cyrus versions can use the existing "lmtp" master.cf entry.
    #
    # Specify in cyrus.conf:
    #   lmtp    cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4
    #
    # Specify in main.cf one or more of the following:
    #  mailbox_transport = lmtp:inet:localhost
    #  virtual_transport = lmtp:inet:localhost
    #
    # ====================================================================
    #
    # Cyrus 2.1.5 (Amos Gouaux)
    # Also specify in main.cf: cyrus_destination_recipient_limit=1
    #
    #cyrus     unix  -       n       n       -       -       pipe
    #  user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
    #
    # ====================================================================
    # Old example of delivery via Cyrus.
    #
    #old-cyrus unix  -       n       n       -       -       pipe
    #  flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
    #
    # ====================================================================
    #
    # See the Postfix UUCP_README file for configuration details.
    #
    uucp      unix  -       n       n       -       -       pipe
      flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
    #
    # Other external delivery methods.
    #
    ifmail    unix  -       n       n       -       -       pipe
      flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
    bsmtp     unix  -       n       n       -       -       pipe
      flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient
    scalemail-backend unix  -       n       n       -       2       pipe
      flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension}
    mailman   unix  -       n       n       -       -       pipe
      flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
      ${nexthop} ${user}
    
    dovecot   unix  -       n       n       -       -       pipe
      flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop}
     
  11. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    At least lines #submission and #smtps are commented out. Compare what you have written to that file to the ISPConfig installation instructions you used.
     
  12. Creps

    Creps New Member

    I reviewed and compared the master.cf of Postfix, making the changes to be exactly as the perfect server tutorial, and now, I'm no longer receiving timeout error in Roundcube, the message is that the email was sent, but it did not reach the mailbox I sent.

    Also, when I test the sending using an online SMTP test (https://dnschecker.org/smtp-test-tool.php), I can only send emails with the 25 port, but can't send with the 587 port, is there anything I can do to change it?
     
  13. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    What is in mail log when message is being sent? If your server log says message was sent, it is in the receiving e-mail server. If the message does not appear in the receiving mailbox, it is the receiving sender that has discarded the message, put it in SPAM folder or maybe the e-mail client moves message to SPAM?
    It would help if you showed exactly what the test tool diagnosed. I assume you did read my e-mail tutorial completely?
     

Share This Page