Recent content by sjaakfaal

  1. S

    Server migration and license invalidity

    Thank you @Active8 Sorry, but I am negligent in following the latest developments. I will contact DA support and/or will checkout a trial license request. I assume it is easy to switch license (https://docs.directadmin.com/directadmin/general-usage/licensing.html)
  2. S

    Server migration and license invalidity

    Hello all, I have 2 DA licences and (ofcourse) two servers. A few weeks ago i did a final migration; before that a few years ago: - installed a new server; - installed DA with license of server that is phased out; - the moment i moved the license from old to new server the old server still had...
  3. S

    Cannot update: MySQL 5.7.33 update to 5.7.35 is available

    Update. In cd /usr/local i removed mysql-5.7.35-linux-glibc2.12-x86_64.tar.gz and the dir mysql-5.7.35-linux-glibc2.12-x86_64. Started the update again, some errors but i lost them. But the update succeeded!
  4. S

    Cannot update: MySQL 5.7.33 update to 5.7.35 is available

    Thank you for your reply. These are the contents of /usr/local: So it seems mysql-5.7.35-linux-glibc2.12-x86_64.tar.gz is extracted to mysql-5.7.35-linux-glibc2.12-x86_64 but thats it?
  5. S

    Cannot update: MySQL 5.7.33 update to 5.7.35 is available

    When i click the button "update" near "MySQL 5.7.33 update to 5.7.35 is available" i get:
  6. S

    ./build rewrite_confs errors

    Hi Guys, Lately i have a weird error when i execute ./build rewrite_confs This is the output: But no effect. Any thoughts?
  7. S

    Apache's failing because of FollowSymlinks in 2.4.48

    Thanks; i did and all went fine except for the last step; see the error log (also see above):
  8. S

    Apache's failing because of FollowSymlinks in 2.4.48

    Hi guys, still having troubles on my server. My history: When i updated Apache ofcourse the |UNIT_PROXY| appeared in all .conf files. I removed all of them using "sed -i" (see above) and all was fine. Then i did all the steps @smtalk suggested; all went fine. Then i created a new virtual host...
  9. S

    Weird connectivity problems on Centos7 / DirectAdmin

    I've edited: - /usr/lib/sysctl.d//usr/lib/sysctl.d/ - executed: sysctl -p - disabled ipv6 hosts in resolv.conf and added: nameserver 1.1.1.1 nameserver 8.8.8.8 nameserver 8.8.4.4 - executed: sudo systemctl restart network Server runs like a battleship!
  10. S

    Weird connectivity problems on Centos7 / DirectAdmin

    That should be both in DA and Centos Centos: https://www.thegeekdiary.com/centos-rhel-7-how-to-disable-ipv6/ DA: https://help.directadmin.com/item.php?id=353 On the other hand; resolving a domainname based on IPV6 should be a standard procedure in a OS :)
  11. S

    Weird connectivity problems on Centos7 / DirectAdmin

    It seems it is a IPV6 problem. Ping to a IPV6 address fails most of the times, IPV4 goes well
  12. S

    Weird connectivity problems on Centos7 / DirectAdmin

    Finally one little (but important) fix. I am able to recreive email again thanks to this thread: https://forum.directadmin.com/threads/mail-received-by-server-but-not-delivered.40542/
  13. S

    Mail received by server but not delivered

    Old thread; 2020 answer; this helped fix one of my problems. Many thanks!
  14. S

    Weird connectivity problems on Centos7 / DirectAdmin

    Warning: firewalld.service changed on disk. Run 'systemctl daemon-reload' to reload units. First time curl example.com shows code; second time: [root@ronald exim]# curl example.com [root@ronald exim]# Noting happens. Same problem. Dig: [root@ronald exim]# dig example.com ; <<>> DiG...
Back
Top