Search results

  1. Invader Zim

    updating bind

    When you have a brand-new server and you run the DA install script, it supposedly installs all the software prerequisites you need. And as far as I can tell, it does. It also installs bind. Earlier this year (in March) I installed a new server. Installed DA. DA installed BIND 9.16.23. BIND...
  2. Invader Zim

    AUTH_BLOCK_SENDER_SPOOFING granular config-support

    What would be the contents (format) of /etc/virtual/${domain:$sender_address}/spoofing_allowed?
  3. Invader Zim

    AUTH_BLOCK_SENDER_SPOOFING granular config-support

    Yes, but when you look at the examples given it shows that a list is proposed of which account can spoof, even when spooging protection is enabled. At least, that's what I got from it.
  4. Invader Zim

    AUTH_BLOCK_SENDER_SPOOFING granular config-support

    I'm pretty sure shanti did check it and discovered it's either on or off. Not granular.
  5. Invader Zim

    CSF pulling the plug

    As this blog post states, end of august csf and some other configserver products will not be available anymore. Will DirectAdmin still support it/keep the installer on the download servers? I mean, just over a month is not exactly ample time to change all our security measures that rely on csf.
  6. Invader Zim

    Incorrect SPF record after restoring backup on a different server

    That's what I'm saying. It used to be like that, automatically. Move to new server, zone file gets updated where all instances of the old ip address (including the spf record) get changed. So it's not a feature request, but more of a revert-to-the-old-situation request.
  7. Invader Zim

    Incorrect SPF record after restoring backup on a different server

    Hi all. For many years now when wanting to move a user to another server I've done so by creating a reseller-level backup of that user with all data, move the backup to the target server and then restore it on the new server where you tell DA to use a different ip address than can be found in...
  8. Invader Zim

    Note: the previous Let's Encrypt config is still set to renew in 4750 days.

    Even when clicken "disable autorenew" before saving the new certificate i get the message "Note: the previous Let's Encrypt config is still set to renew in x days". When I then press the disable auto renew button you would think everything is fine. Paste the same certificate information again...
  9. Invader Zim

    5th instance of php not working

    I was 100% certain I had. But it turns out I did not. Good spot. :oops:
  10. Invader Zim

    5th instance of php not working

    We were happy to see we can use 5 more versions of php now on the same server. Not that we'd ever do that, but when you've got customers using all the 4 currently installed versions that are older than 8.3 it's nice to be able to add a 5th. However, we couldn't get it to work. The socket was...
  11. Invader Zim

    exim didn't want to build, the fix broke the server

    I fixed it by editing the config file for the version of php in /usr/local/directadmin/custombuild/custom/litespeed, by removing the lines --with-icu-dir --with-pcre-regex followed by yum install libmcrypt-devel da build restore_old_local libiconv After that da build php x.xworks again.
  12. Invader Zim

    exim didn't want to build, the fix broke the server

    Yes, I installed both. # yum list | grep pcre alt-pcre.x86_64 8.41-1.el7 @cloudlinux-imunify360 alt-pcre2.x86_64 10.34-1.el7 @cloudlinux-x86_64-server-7 alt-pcre802.x86_64 8.02-7.el7 @cloudlinux-x86_64-server-7 pcre.x86_64...
  13. Invader Zim

    exim didn't want to build, the fix broke the server

    Can't build pcre with custombuild. # da build pcre +-----------------------------------------------------------+ | DirectAdmin WebServices Installer | | Written by Martynas Bendorius and DirectAdmin | | Version: 2.0.0 | +-----------------------------------------------------------+ | To build...
  14. Invader Zim

    exim didn't want to build, the fix broke the server

    Yeah, I didn't mention that in my post, but i already did that. Doesn't make a difference
  15. Invader Zim

    exim didn't want to build, the fix broke the server

    da build prce doesnt work anymore
  16. Invader Zim

    exim didn't want to build, the fix broke the server

    Once again got the message that exim couldn't be built, and so I did the da build remove_old_local libiconv but that didn't work. First I had to da build remove_items da build all but that failed on nginx, because modsecurity wasn't installed, so I installed that first. When 'da build all'...
  17. Invader Zim

    reseller's creator keeps getting changed to root

    We use installatron to offer our clients (and the resellers' clients) an easy way to install/backup/update their websites. I'm certain many others have at least heard of it. Now, last week we started getting complaints that backups no longer worked. Mind, this is about the installatron backups...
  18. Invader Zim

    CentOS 7.9 and da build php (y/n)

    I tried the options mentioned in the link johannes provided. During build all whilst configuring for nginx it threw configuring additional modules adding module in ../modsecurity-nginx-v1.0.3 checking for ModSecurity library ... not found checking for ModSecurity library in...
  19. Invader Zim

    CentOS 7.9 and da build php (y/n)

    I did exactly what it said in that post. da build remove_old_local libzip. That made it so both 8.1 and 8.2 couldn't even start, and compiling was a bust too.
Back
Top