Recent content by agarzon

2 years later, the BUG is still unresolved.

Is there any update about this bug?, is polluting the log system very hard.

You can set UMASK 022 in the /etc/login.defs that is what I found in my other Plesk server but with Centos 7 There are plenty docs in internet about UMASK, but as quick summary: 077 Very restrictive, so more secure but causing errors here and there. 027 A bit more restrictive than the common...

Not yet, something in Plesk is changing the UMASK in the file /etc/login.defs probably one of his multiple extensions, not sure which one yet.

Yes, exactly as is. Still does not work. :(

Now I strongly believe this is related with umask which is 077 in both (my production and my experimental server Cetos 8 both) Interestingly they were 022 before I installed Plesk and becomes 077 after plesk was installed. Now I need to double check when exactly changes to 077 since I was...

Thank you, but it does not work as the others in the blacklist, still being shown in Advisor. Maybe is the wrong name or maybe advisor is ignoring that specific extension to be blacklistted?

Hi. Anyone knows what is the name of the extension: Plesk Email Security ? so I can add it to my blacklist. This is my current blacklist if anyone is looking for somethig similar: [ext-advisor] allowCovid19Recomendation = off blacklist = GoogleAuthenticator, KernelCare, SeoToolkit, SpeedKit...

User name: agarzon TITLE plesk repair dns changing permissions to 0600 PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian Versión 18.0.30 CentOS Linux 8.2.2004 (Core) PROBLEM DESCRIPTION When I executed the command: plesk repair dns The file /var/named/chroot/etc/named.conf...

Asking if there is any update in this matter.

Did you found the solution for this?

Why this is mark as resolved?

Look like a micro-update from phpmyadmin (4.9.0.1-2.centos.7+p18.0.19.2+t190926.1641) introduced a change in the file /usr/local/psa/admin/htdocs/domains/databases/phpMyAdmin/libraries/config.default.php causing to store the session in './tmp/session' instead...

Solved: * yum remove postfix-perl-scripts * Upgrade to obsidian (plesk installer) Upgraded successfully. So basically pflogsumm does not support postfix 3.x and now I will consider it as deprecated.

* Brand new server setup with Onyx 7.8.11 few days ago. Centos 7.7 Fully updated and operative, only standar repositories enabled. Executed plesk installer from command line to upgrade to Obsidian. You have the product version Plesk 17.8.11 installed. Do you want to upgrade it? [Y/n]: y...