Search results

See https://support.plesk.com/hc/en-us/articles/12377563705623 which at the moment is missing one part (support has been informed). You need to uncomment the following line in "/etc/apparmor.d/usr.sbin.named": include <local/usr.sbin.named> Then add the following line to...

Just got the information that "it should work since Plesk Obsidian 18.0.39". There was no mention of the bug in the changelog, because "the bug was fixed in scope of implementing the following feature": (Kind of confusing, but ok)

Should have been released in July. Still no fix in November =(

It just so happened that I came upon this bug myself using "plesk bin reconfigurator". Plesk has confirmed this bug and PPPM-13049 should be fixed in the upcoming release. Almost 10 years later...

Came here looking for a solution to the horde problem. For me, turned out that "/etc/psa-webmail/horde/horde/conf.php" was missing. Restored from backup.

Bumping this old thread as I have noticed a very similar problem with Plesk Obsidian 18.0.30.1 after a recent upgrade from Debian Jessie to Stretch. On a website running a PHP version installed by Plesk, users couldn't login anymore. Turned out the "session.save_path" was still set to...

Anscheinend erkennt Plesk ja Debian Bullseye, womit es derzeit noch nicht kompatibel ist. Nach Deiner Aussage "Debian 10" wäre es Buster, was ok wäre. Entweder erkennt Plesk also irgendetwas falsch oder Dein System ist durcheinander. Bitte die Ausgaben der folgenden Befehle posten: lsb_release...

@mow Good catch. I was in the original thread about compatibility between Plesk and Debian Buster and when the new version came out, I didn't notice that thread was in the Onyx section. So yes, this thread should be moved to Obsidian (@IgorG ?).

As I said in my last post, it's possible to upgrade from Stretch to Buster. Have upgraded around 10 servers without problems so far. As the helper script used to reset some settings before updating, it's now even smoother with less interference IMHO. Takes around one hour to upgrade a server...

Could you describe your problem in more detail in a separate thread and put a link to it here?

Figured out a way to dist-upgrade an existing server to Debian Buster. Not exactly user-friendly... https://talk.plesk.com/threads/instructions-on-upgrading-an-existing-debian-stretch-with-plesk-to-debian-buster.357293

I did a lot of testing to get the update right from Debian Stretch to Debian Buster running Plesk 18.0.28.2. Unfortunately, Plesk currently doesn't officially support this like it used to do in previous versions. It's possible if you adhere to some specific steps. Caveats: Contrary to previous...

We have servers that have been upgraded to a recent release again and again, going from Debian Lenny to Wheezy to Jessie to Stretch. Therefore keeping systems up-to-date and secure. This is what I loved about Plesk and why we never considered any other control panel. I just tried to upgrade a...

Not yet, see compatibility here Software Requirements for Plesk Software Requirements for Plesk and vote here Be prepared for Debian Buster

My workflow has become quite large over the years so I can't post all the details here, but in general: - inform yourself: How to perform dist-upgrade procedure on server with Plesk Chapter 4. Upgrades from Debian 8 (jessie) - make sure that your domains will be compatible with the new version...

Ok. Though, it doesn't look that way as Change Log for Plesk doesn't list 17.8 as beta anymore and https://www.plesk.com/lifecycle-policy/ lists Debian 9 as supported by 17.8. However, I have upgraded all my Plesk servers with 17.5 to 17.8 in the last weeks without any problems, and...

There is a "/opt/psa/bin/distupgrade.helper.deb8-deb9_pre.x64.sh" and later on a "/opt/psa/bin/distupgrade.helper.deb8-deb9_post.x64.sh", so I doubt that.

@IgorD: The document you linked has not been updated with information for Debian Stretch.

I see that the previous upgrade guide "Parallels HowTo: Perform dist-upgrade procedure on server with Plesk 12.5" (KB Odin) has been removed. @IgorG: Will there be an easy way to upgrade existing servers (than running Plesk 17.8 (or whatever it will be)) from Debian Jessie to Debian Stretch? As...

The reason for the problem seems to be that entries in the table "domains" have a "cert_rep_id" of NULL. Setting this to 0, the error didn't show up anymore. UPDATE domains SET cert_rep_id = 0 WHERE cert_rep_id IS NULL;