Search results

It was desired that the tls1 and 1.1 e-mail services remain activated, which is why it is on the server server_pref -u -ssl-protocols 'TLSv1 TLSv1.1 TLSv1.2' set. for nginx we had edited this extra so that TLSv1 TLSv1.1 are deactivated. until the update to 18.0.38 that was always retained. Ok...

Some time ago we set up /etc/nginx/conf.d/ssl.conf on all servers ---- ssl_ciphers...

I can also confirm. For example, customers cannot create new email addresses because various buttons are simply missing.

did you initiate the update to 18.0.37 manually or was it an automatic update? Scary when such an effort arises from an update.

Yes that is a fact. If Virtuozzo is used then it is now very close that in a few years or earlier the centos 7 machines will be migrated to vzlinux 8. Especially because Virtuozzo wants to make it easier "we are currently building already is a tool to convert CentOS 7 -> VzLinux 8" The number...

Hi, "not" reseller-wide but server-wide see: https://support.plesk.com/hc/en-us/articles/115003160145--Site-on-Plesk-is-not-available-ModSecurity-Response-body-too-large

In the last few days there have been various messages here in the forum that the update of the comodo ruleset has failed. we have also had this for a few days on different servers centos 7 and 8.

according to the roadmap (VzLinux), the release should be Q2-2021. What could also be very exciting is "simple and on-the-fly conversion from CentOS 8 to VzLinux 8 plus the possibility to convert CentOS 7 directly to VzLinux 8" It would be a dream if you first update a centos7 Plesk server to...

See here: https://talk.plesk.com/threads/please-follow-this-instruction-if-you-believe-that-found-a-bug.339636/

the diskspace can e.g. be different because backups are calculated for the source but not for the target because the plesk migrator does not take over any backups. I can't say anything about possible database problems with the migrator. we migrated thousands of databases during server changes...

I don't know of any solution. the customer has to change his email address for his distribution.

sorry - please move this post from -Plesk Onyx for Linux to -Plesk Obsidian for Linux

Centos 7.9 Plesk Obsidian 18.0.33 a long time ago the customer set up an email distribution list based on forwarding. He added a plus sign to the email address. for example [email protected] that has worked normally for the last few years. an interim transfer to another server with the plesk...

Could we get feedback on this from the team, please?

this can take weeks until the updates are made. this is also completely different for my servers. some after 1-2 weeks some after 3-4 weeks. What is also added is that the update times day / time are completely ignored. there is sometimes the update from 31 to 32 in the middle of the day...

where did you do this setting? I would like to set it that way too, but in the update settings I only see the option that automatic updates are activated or not. And this probably also applies to version upgrades.

centos 6 look here: https://support.plesk.com/hc/en-us/articles/360017922619-After-November-30th-2020-updating-system-packages-on-Plesk-server-with-CentOS-6-fails-Cannot-find-a-valid-baseurl-for-repo-base

this sounds interesting if plesk may also support it. https://blog.cloudlinux.com/announcing-open-sourced-community-driven-rhel-fork-by-cloudlinux

swap the baseurl to vault.centos.org in CentOS-Base.repo [base] name=CentOS-$releasever - Base #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/...