Custom Config not working

Discussion in 'Installation/Configuration' started by FSNTiger, Apr 2, 2021.

  1. FSNTiger

    FSNTiger Member

    After creating a custom config in these two files after the 3.2.3 update, the 3.2.4 update saw them there but did not use them.


    Update Log (Cleaned):

    Operating System: CentOS 7.9
    This application will update ISPConfig 3 on your server.
    Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]:
    Creating backup of "/usr/local/ispconfig" directory...
    Creating backup of "/etc" directory...
    Checking ISPConfig database .. OK
    Starting incremental database update.
    Loading SQL patch file: /tmp/
    Reconfigure Permissions in master database? (yes,no) [no]:
    Service 'firewall_server' has been detected (currently disabled) do you want to enable and configure it? (yes,no) [no]:
    Reconfigure Services? (yes,no,selected) [yes]:
    The following custom templates were found:
    Do you want to rename these conf-custom templates now so the default templates are used? (yes,no) [no]:
    The following local config override templates were found, be sure to incorporate upstream changes if needed:
    Configuring Postfix
    Configuring Dovecot
    Configuring Spamassassin
    Configuring Amavisd
    Configuring Getmail
    Configuring BIND
    Configuring Pureftpd
    Configuring Apache
    Configuring vlogger
    Configuring Apps vhost
    Configuring Jailkit
    Configuring Database
    Updating ISPConfig
    ISPConfig Port [808X]:
    Create new ISPConfig SSL certificate (yes,no) [no]:
    which: no in (/usr/local/ispconfig/server/scripts)
    which: no in (/root/
    Reconfigure Crontab? (yes,no) [yes]:
    Updating Crontab
    Restarting services ...
    Update finished.

    My custom configs:

    Postfix custom config:
    greylisting = check_policy_service unix:postgrey/socket
    smtpd_tls_cert_file = /var/system/ssl/cert.pem
    smtpd_tls_key_file = /var/system/ssl/privatekey.pem

    Dovecot custom config:
    ssl_cert = </var/system/ssl/chain.pem
    ssl_key = </var/system/ssl/privatekey.pem

    Am I missing something or is something broken?
  2. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    So those values are not in, and no 99-ispconfig* file created in /etc/dovecot/conf.d?
  3. FSNTiger

    FSNTiger Member

    No, the default values still appear in the and dovecot config files. After swapping them to my custom config settings and restarting the services all runs fine. There is no 99-ispconfig file in the folder specified. I did notice in that the 3 lines I had in my custom file where moved out of the flow and appeared at the bottom, but still had the default values. Like it tried to change, knew which lines to change and just did not. Dovecot conf was not that way however.

    As a side note, the other custom config service is Pure-FTP. The settings for TLS, ports and SSL also have to be reset. Is there a custom config spot for Pure-FTP as well?
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Could you try running a force update and see if it works then?
    Code: --force
  5. FSNTiger

    FSNTiger Member

    I did try that before posting, as it was recommended in the Dovecot config file. The result was the same as a normal update.
  6. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

  7. FSNTiger

    FSNTiger Member

    Sounds good. Thanks
    Going forward in the next year or so I plan on transitioning from CentOS, 7 currently and I don't want to move to 8 which has no life, to either Debian or Ubuntu. Would you recommend one over the other in terms of performance and security?
  8. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    I am personally using Debian. I think this is the best distribution for professional users.
  9. FSNTiger

    FSNTiger Member

    Ok. I was leaning that way. I like that debian is entirely community vs having a company that controls the course of changes. Both LTS end in 2022 for core support and move into extended. I can see some tweaks I will add in any case, such as postgrey which does not appear to be in the perfect server tutorials for debian. And it will take some other learning to adjust some other settings, but that's not that big of a deal.

Share This Page