Search results

Thank you. I will go through these steps. I juststarted plesk repair installation and it seems that the last update from .48 to .49 was not registered successfully in th Plesk-DB. I'll let you know what happened once I have applied the steps of the older thread.

After a restart of the Amavis component of the Plesk E-Mal Security extension I receive the following errors concerning missing modules: Any idea why amavis does not find the following decoders? I.e. I have stored rar und unrar in /usr/local/bin The files got owner:group amavis:amavis...

Checking the protocols I found as recent error: "Autoinstaller exited with error: The product 'plesk' is not installed yet." and also the error: "Unable to get information about updates for current release". Any proposal thow to get rid of this error? By the way, Plesk is installed and works.

Done:-)

As I only use nginx I guess it would be interesting to install for fail2ban an additional jail + filter just for nginx. Are there proposals to enhance the Plesk-fail2ban configuration for doing this?

So, I finally made it. After failing with setting up a Wireguard-VPN I went back to OpenVPN and found the following solution: I simply installed: mkdir -p /dev/net mknod /dev/net/tun c 10 200 chmod 600 /dev/net/tun Then I could install OpenVPN using a skript. The only problem of this approach...

Ok, that explains it. Thank you. I now have asked my VPS-host to provide an ubuntu kernel with the necessary TUN/TAP-module. Hopefully it will work. However, if they are not willing to do this your OpenVPN hint will be Plan B as it is only free of charge for two connections.

After an upgrade from my old to a new VPS my dev/tun device including its module disappeared. :~# modprobe tun modprobe: FATAL: Module tun not found in directory /lib/modules/5.4.0 So my OpenVPN does not work any longer. Question: Is it possible to install the necessary TUN module using Plesk...

I just did it and ... it works! Thank you for your quick help:-)

Thank you. Will this solve my problem, that currently test.domain.de (which does not exist) points to www.domain.de (what I do not want)?

I upgraded from Plesk V. ...48 to Plesk ...49. Now I found out by chance, that a deleted subdomain subXXX.domain.de is now pointing to www.domain.de . After discovering this I also found out that ALL possible subXXX.domain.de are pointing to www.domain.de. I am afraid that this could harm my...

I guess, you are right. I will start with a ticket next year when I have more time to go through the drush problem, too:-) However, thank you for your kind help:-)

Hi Peter, yes it is about "drush" which is very comfortable to manage my drupal-site. I just tried to follow you proposal but unfortunately failed. Result: ... root@mail:~# ./update-chroot.sh --add /usr/local/bin/ | drush WARNING: /usr/local/bin/ is not a program (filetype inode/directory...

I just checked the whole log and found, that 5th of November it happened first time, then one time each day [2022-11-05 04:23:52.738] 1821513:6365d748b3d6c ERR [panel] Unable to get key: Repository is not opened [2022-11-05 04:23:52.752] 1821513:6365d748b3d6c ERR [panel] Unable to get key...

Yes, all steps without any errors.

2022-12-19 03:30:29 ERR panel [814933:639fccc52e65d] Unable to get key: Repository is not opened 2022-12-19 03:30:29 ERR panel [814933:639fccc52e65d] Unable to get key: Repository is not opened 2022-12-19 03:30:29 ERR panel [814933:639fccc52e65d] Unable to get key: Repository is not opened...

The error came up today: 2022-12-18 11:05:11 ERR panel [580152:639ee5d7ca4d5] Unable to get key: Repository is not opened 2022-12-18 11:05:11 ERR panel [580152:639ee5d7ca4d5] Unable to get key: Repository is not opened 2022-12-18 11:05:11 ERR panel [580152:639ee5d7ca4d5] Unable to...

I saw this artcle but as the content of /etc/sw/keys/info is sw-key-repository-1.0 what seems to be correct I did not proceed further.

Just checked whether the plesk license key can be received via command line. Result: # plesk bin license --retrieve Updating Plesk license key: Done So it seems not to be the old bug #PPPM-9001 However, I have no idea from where the panel errors come from.

Thank you for the help. This is the result: plesk repair fs -system -y Checking Linux system files ......................................... [OK] Error messages: 0; Warnings: 0; Errors resolved: 0 Could it be, that the Plesk bug with ID #PPPM-9001 fixed in Plesk Onyx 17.8 for Windows on...