Posts by technotravel

    Maybe really a silly question - but I just can't get Nextcloud 18 installed. It requires minimum php 7.2.


    I have installed and added to PhpSwitcher php 7.3, and put it active for the domain in question. Otherwise, there is just the standard php 7.1 installed.


    Still on the console php -v only shows php 7.1.


    And when I come to this step of upgrading my Nextcloud installation:

    Code
    1. sudo -u vu2004 ./occ upgrade

    I get

    Code
    1. This version of Nextcloud requires at least PHP 7.2<br/>You are currently running 7.1.33-15+0~20200419.36+debian9~1.gbp2384b3. Please update your PHP version.

    Any suggestions how to proceed?


    Many thanks for advice

    Chris


    Debian 9

    i-MSCP 1.5.3

    PhpSwitcher 5.0.5

    Other plugins in the most recent versions (fresh install): LetsEncrypt, Mailman, OpenDKIM, RoundcubePlugins, SpamAssassin

    It was resolved indeed and many thanks to f4Nm1Z9k2P for his friendly assistance :thumbsup:


    The basic problem was the format of the TXT entry for the mail record in the DNS. It has been mentioned already here in the forum - in the case of some external DNS providers, it is necessary to remove quotation marks and empty spaces of the key for that field.


    I had done this, but my Thunderbird Addon DKIM-verifier still indicated a problem (as indicated in the opening post), which made me think that the DKIM settings for my server aren't working.


    f4Nm1Z9k2P pointed out to me that the Addon is actually caching old DNS records. After I deleted the file "dkimKey.sqlite" in my Thunderbird profile, the DKIM-verifier shows a positive result.


    I am mentioning this here in case another user runs into the same problems. I have written to the developer of the Addon about this problem, and will eventually update this post with additional information.

    OpenDKIM doesn't work on my server.


    I use an external DNS Service and have entered the TXT record for mail as instructed.


    Output from mail-tester: "Wir konnten Ihren öffentlichen Schlüssel nicht empfangen."


    DKIM-Verifier, an AddOn for Thunderbird, reports for mails from my server: "Ungültig (Kein DKIM Schlüssel im DNS Server gefunden)"


    What can I do to correct this?


    i-MSCP 1.5.3 Build: 20180516

    OpenDKIM Version 2.0.0 (Build 2017090800)


    Das ist ein bisschen blöd gelöst - die Filter sind per default nicht aktiviert.


    Aktiviert wird das in:

    /var/www/imscp/gui/plugins/RoundcubePlugins/config.php


    Stehen sollte dort:

    'managesieve_plugin' => 'yes',


    Danach im Plugin Interface noch mal alle Plugins aktualisieren, dann sollte es gehen.


    Viel Erfolg!
    Chris


    Oops sorry for the reply in German - but I think you will understand it anyway ;-)


    Don't forget to update the plugin in the Plugin Control page after having saved your changes to the config.php - good luck!

    Thank you!


    It's strange - to me all plugins showed as activated, checked it just before I posted.


    letsencypt and Sieve work now. OpenDKIM not at first try, but I probably have to control / re-enter the keys again. Will revert when done.


    Would you mind telling me what was the configuration error with OpenDKIM?


    Thanks again!
    Chris

    I have upgraded my vserver to Debian 9 (stretch) with a complete fresh install. On the previous Debian version, all imscp services and plugins have been functioning flawlessly. imspc has been upgraded to 1.5.3. Now a number of plugins are not working as they should:


    - letsencrypt (3.3.0): there are no buttons for letsencrypt anymore, neither in the admin nor in any customer interface. The certificates exist, but some are close to expiration and I can't renew them.


    - RoundcubePlugins (2.0.2): the Sieve filters are not functional, despite having them activated in /var/www/imscp/gui/plugins/RoundcubePlugins/config.php ('managesieve_plugin' => 'yes',)



    - OpenDKIM (2.0.0): external DNS server (inwx.de), I have tried the key-entries both with and without quotes. Mail-tester reports "message not signed with DKIM".



    Given that 3 plugins are failing, I am suspecting an issue with the plugin-architecture as such, but I have no clue where to check this. What I have tried so far without any improvement:
    - deactivated and reactivated all plugins
    - reconfigure imscp (perl /var/www/imscp/engine/setup/imscp-reconfigure -danv)
    - reboot the vserver



    Other installed plugins: Mailman (2.0.4), PhpSwitcher (4.0.3), SpamAssassin (2.0.1)



    I would appreciate some help on this and am ready to provide logs, once I know which ones are required. Many Thanks in advance!
    Chris