Issue Update manual instructions for upgrading Debian

[Daveo]

Server operating system version

Debian 12.15

Plesk version and microupdate number

18.0.81

Can the upgrade instructions here be updated to include both manual and automated instructions on upgrading Debian from 12 to 13 please, now that Plesk officially supports upgrading Debian from 12 to 13 (as of Plesk 18.0.81).

Currently only lists Debian 9 to 10, 10 to 11 & 11 to 12.

 

[Martin Dias]

The article does state that dist upgrade is NOT yet supported to Debian 13



Additional information:

https://support.plesk.com/hc/en-us/articles/34096772343959-Does-Plesk-support-Debian-13-Trixie

We will add instructions as soon as they are supported

 

[Daveo]

OK.

Release notes make it a bit confusing, I though they are now implying that dist upgrade from 12 to 13 is supported.

Sorry if I got confused over this.

 

[Hangover2]

No need to apologize, @Daveo - your confusion is completely understandable.

@Martin Dias , could you please clarify why this is considered unsupported?

Plesk has already published an automated upgrade script directly under the verified Plesk GitHub organization:
The tool to dist-upgrade servers with Plesk from Debian 12 to 13

Even more importantly, this is explicitly listed in the official Plesk Obsidian 18.0.81 changelog:
Plesk Obsidian 18.0.81

Prepared a script to automate dist-upgrade from Debian 12 to Debian 13.
Note that MariaDB 10.11 is upgraded to MariaDB 11.8 as part of the procedure, because Debian 13 no longer ships MariaDB 10.x.
Learn how to dist-upgrade to Debian 13.

If dist-upgrading to Debian 13 is genuinely not supported yet, either the support article is outdated, or the 18.0.81 release notes and the official repository are providing misleading information to users.

 

[Martin Dias]

I am sorry all for the confusion, my information was somewhat outdated.
I requested to the responsible team to update both articles.

 

[Martin Dias]

FYI, Automated upgrade section was added, manual steps will be added later by the support team, I have no ETA for now.