ISPC3 login time

Discussion in 'General' started by mrbronz, Mar 30, 2021.

Tags:
  1. mrbronz

    mrbronz Member HowtoForge Supporter

    Hi guys

    I've noticed that to log in to CP of ISPC3 is taking a long time, also moving from tab to tab is also taking some time, approx 60 seconds.

    Is there something I have misconfigured or can I do something to speed this up?

    Many thanks
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Something must be wrong with your setup. Try using a different browser and use the dev functions to analyze what is taking so long.
     
  3. mrbronz

    mrbronz Member HowtoForge Supporter

    Hi Thom
    Thanks for the quick reply

    I have tried Brave Firefox and chrome all the same...

    I have noticed if I use the local IP address 192.168.1.1:8080 the CP is operating normally
     
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

  5. mrbronz

    mrbronz Member HowtoForge Supporter

  6. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    I send you the link to the read before posting, which mentions the script in the second sentence.
     
  7. mrbronz

    mrbronz Member HowtoForge Supporter

    The only thing I can see is this

    ##### SERVER #####
    IP-address (as per hostname): ***.***.***.***
    [WARN] could not determine server's ip address by ifconfig
     
  8. mrbronz

    mrbronz Member HowtoForge Supporter

    Code:
    ##### SERVER #####
    IP-address (as per hostname): ***.***.***.***
    [WARN] could not determine server's ip address by ifconfig
    [INFO] OS version is Debian GNU/Linux 10 (buster)
    
    [INFO] uptime:  12:20:17 up 23 min,  1 user,  load average: 0.95, 0.58, 0.61
    
    [INFO] memory:
                  total        used        free      shared  buff/cache   available
    Mem:          1.7Gi       1.4Gi       108Mi        20Mi       184Mi       129Mi
    Swap:         1.7Gi       265Mi       1.5Gi
    
    [INFO] systemd failed services status:
    0 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.
    
    [INFO] ISPConfig is installed.
    
    ##### ISPCONFIG #####
    ISPConfig version is 3.2.3
    
    [WARN] Could not use mysql command line to connect to the database. Check your mysql config!
    
    ##### VERSION CHECK #####
    
    [INFO] php (cli) version is 7.3.27-1~deb10u1
    
    ##### PORT CHECK #####
    
    [WARN] Port 22 (SSH server) seems NOT to be listening
    
    ##### MAIL SERVER CHECK #####
    
    
    ##### RUNNING SERVER PROCESSES #####
    
    [INFO] I found the following web server(s):
            Apache 2 (PID 905)
    [INFO] I found the following mail server(s):
            Postfix (PID 753)
    [INFO] I found the following pop3 server(s):
            Dovecot (PID 393)
    [INFO] I found the following imap server(s):
            Dovecot (PID 393)
    [INFO] I found the following ftp server(s):
            PureFTP (PID 825)
    
    ##### LISTENING PORTS #####
    (only           ()
    Local           (Address)
    [localhost]:10023               (584/postgrey)
    [localhost]:10024               (987/amavisd-new)
    [localhost]:10025               (753/master)
    [localhost]:10026               (987/amavisd-new)
    [localhost]:10027               (753/master)
    [anywhere]:587          (753/master)
    [localhost]:11211               (383/memcached)
    [anywhere]:110          (393/dovecot)
    [anywhere]:143          (393/dovecot)
    [anywhere]:465          (753/master)
    [anywhere]:21           (825/pure-ftpd)
    ***.***.***.***:53              (418/named)
    [localhost]:53          (418/named)
    [anywhere]:2293         (470/sshd)
    [anywhere]:25           (753/master)
    [localhost]:953         (418/named)
    ***.***.***.***:40127           (2096/pure-ftpd)
    [anywhere]:993          (393/dovecot)
    [anywhere]:995          (393/dovecot)
    ***.***.***.***:40198           (2079/pure-ftpd)
    *:*:*:*::*:10023                (584/postgrey)
    *:*:*:*::*:10024                (987/amavisd-new)
    *:*:*:*::*:10026                (987/amavisd-new)
    *:*:*:*::*:3306         (467/mysqld)
    *:*:*:*::*:587          (753/master)
    [localhost]10           (393/dovecot)
    [localhost]43           (393/dovecot)
    *:*:*:*::*:8080         (905/apache2)
    *:*:*:*::*:80           (905/apache2)
    *:*:*:*::*:8081         (905/apache2)
    *:*:*:*::*:465          (753/master)
    *:*:*:*::*:21           (825/pure-ftpd)
    *:*:*:*::*:53           (418/named)
    *:*:*:*::*:2293         (470/sshd)
    *:*:*:*::*:25           (753/master)
    *:*:*:*::*:953          (418/named)
    *:*:*:*::*:443          (905/apache2)
    *:*:*:*::*:993          (393/dovecot)
    *:*:*:*::*:995          (393/dovecot)
    
    
    
    
    ##### IPTABLES #####
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    f2b-postfix-sasl  tcp  --  [anywhere]/0            [anywhere]/0            multiport dports 25
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    
    Chain f2b-postfix-sasl (1 references)
    target     prot opt source               destination
    REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
    RETURN     all  --  [anywhere]/0            [anywhere]/0
    
     
  9. mrbronz

    mrbronz Member HowtoForge Supporter

    After a bit of testing and research, it seems the problem is the Nameserver part is not resolving very quick.

    If I use the public IP address I can get the site up in no time but because I'm running my own DNS zones when I use the full URL it's so slow.

    Any ideas as to how I test where the slow response is coming from?
     
  10. mrbronz

    mrbronz Member HowtoForge Supporter

    It's OK I've sorted it out myself thanks for your help guys
     
  11. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    You have pointed martin.gregson.me.uk to 4 public IPv4 addresses, this could/will cause trouble
     
  12. mrbronz

    mrbronz Member HowtoForge Supporter

    THanks Thom

    Can you explain how this would be a problem please?

    edit
    So from what I understand I only need an rDNS for email servers is this correct?
     
    Last edited: Mar 31, 2021
  13. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    No.
    If you mean that only e-mail servers need rDNS PTR record, that is partly true, other kinds of servers may not need PTR record but there is little reason not to create one.
     
  14. mrbronz

    mrbronz Member HowtoForge Supporter

    Thanks Taleman

    So the mistake I have made is just pointing several rDNS records to one server or should I say different public IP addresses to "A" records on the same zone?

    That makes sense, now I have disabled the other "A" records IPC3 is working at normal speed

    Ones again thank you
     
  15. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    It has nothing to do with rDNS. Why are you pointing traffic for that domain to 4 different IP's?
     
  16. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    You should read again the DNS tutorial, link in my signature. Read also the additional info, links in the tutorial.
     
  17. mrbronz

    mrbronz Member HowtoForge Supporter

    What the correct thing to do?
     
  18. mrbronz

    mrbronz Member HowtoForge Supporter

    I have read it but have not fully understood it. Understanding takes time.
     
  19. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Does this server use all 4 of those IP addresses? Is the web server available on all of those?

    Usually you point such records to one IP.
     

Share This Page