Search results

Hi everyone, Can't tell for sure is it expected or not for their file in github to remain "updated 7 years ago", yet you can download the package, for example, from here: https://ubuntu.pkgs.org/22.04/ubuntu-universe-amd64/fail2ban_0.11.2-6_all.deb.html and unpack(`ar x *.deb` && `tar -xvf...

Thanks. Thought there might be an inconsistency, but table looks well. At this point, you can follow the earlier given suggestion and request support as dedicated investigation is required.

All I can see here is 404: https://dlm.mariadb.com/repo/mariadb-server/10.11.5/yum/rhel/8/x86_64 Latest MariaDB release is 11.3: MariaDB Server - All releases - MariaDB.org What's the currently installed MariaDB version? /usr/sbin/mariadbd -V or /usr/sbin/mysqld -V

And in the meanwhile, perhaps you can share the output? plesk db "select id,host,type,port,last_error,fork from DatabaseServers \G"

Could you show the contents of the mariadb repo file from /etc/yum.repos.d/ ?

>> there was a timeout error That's why the utility failed I guess. On my server I had no timeouts. Anyways, if timeout is reproducible under particular circumstances, you can file a bug report.

Try: # plesk sbin sslmng --service dovecot --strong-dh --dhparams-size=2048 # systemctl restart dovecot This will create new DH parameters set(/opt/psa/etc/dhparams2048.pem) and replace the "/opt/psa/etc/dhparams1024.pem" value at ssl_dh with it in /etc/dovecot/conf.d/11-plesk-security-ssl.conf

/etc/dovecot/conf.d/11-plesk-security-ssl.conf exists? If so, paste it's contents. also, # cat /etc/dovecot/conf.d/10-plesk-security.conf |grep -v ^# Is certificate for local mailserver set? Do you use apparmor?

Recreate the user. Then grant it with privileges on the `emailsecurity` DB. CREATE USER 'XXXXXXX'@'localhost' IDENTIFIED BY 'XXXXXXXXXXXX'; GRANT SELECT, INSERT, UPDATE, DELETE on emailsecurity.* to 'XXXXXXXXXX'@'localhost'; XXXXXXXXX's are to be replaced with the username(it starts with es_)...

Looks like you've made a query to a wrong db. Query should go to psa.

Hi, Loop devices technically consist of the exact size of the mounted filesystem content, hence they will always be 100%. No fix is needed here. https://en.wikipedia.org/wiki/Loop_device >> Mounting a file containing a file system via such a loop mount makes the files within that file system...

That prefix (es_) does belong to Email Security. For example, you can use the next query in plesk db to find credentials used by ES: select ms.name,ms.value from ModuleSettings ms join Modules m where m.id=ms.module_id and m.name='email-security'; Once these are at hand, recreate this user in...

Hi, I'd strongly recommend performing something like this in a maintenance timeframe if the server is in a production environment. Actions performed as root. 1. Create dump backup folder: # mkdir /root/dbBackups 2. Dump databases, just in case(don't proceed if this action failed): # plesk db...

Hello, PSA DB inconsistency. trace: #0 /usr/local/psa/admin/plib/modules/nodejs/library/Navigation/OverviewPage.php(15): pm_Domain->getProperty(string 'application') Here it checks the `dom_param` table if domain in question does have the `param` = "application" with `val` = "ext-nodejs" in...

Looks like Mariadb/MySQL is down due to lack of the disk space. Connect via SSH and check with: # df -hT And remove unnecessary content.

>> Is this the one I have installed manually? Most probably. Normally, authorized_keys is empty. >> And further, I could add a key. Would this key be usable in addition to the existing one? yes, authorized_keys file's structure does support multiple keys with newline as delimeter

@Kulturmensch Are you sure you've pressed the small "<" button on top right side of the panel's interface?

@Kulturmensch The menu option should be there: In case it is not, I'd recommend checking /var/log/plesk/panel.log for errors when refreshing the subscriptions' page.

Not quite casual, when containers are ran as root by default. Nonetheless, you can deploy a container manually as non-root user: https://docs.docker.com/engine/security/rootless/ I'd recommend testing that scenario on a staging server first.

Only root/sudoers have access to docker by default. Technically, you can: 1) grant the subscription's system user (at Web Hosting Access) with shell access. Then modify user by adding the docker group, for example: # usermod -aG docker jdoe and call the commands in deployment actions...