Backups to remote storage fail with "expected str, bytes or os.PathLike object, not int"

[ahoi]

Username:

TITLE

Backups to remote storage fail with "expected str, bytes or os.PathLike object, not int"

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

18.0.47, Debian 11

PROBLEM DESCRIPTION

Backups to remote storage (FTPS) are failing instantly with "expected str, bytes or os.PathLike object, not int".

Could be related to PPPM-13733.

STEPS TO REPRODUCE

Create a new backup task with remote store target.

ACTUAL RESULT

Backup fails with


Fehler: Der Backupvorgang ist fehlgeschlagen: expected str, bytes or os.PathLike object, not int

EXPECTED RESULT

Working backup

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Hangover2]

Hello,

duplicate of [Bug is confirmed: ID PPPM-13733] Scheduled Backups Fail in Plesk Obsidian 18.0.47

 

[ahoi]

Maybe. This behavior is not confirmed by the Plesk team yet.

 

[Hangover2]

@ahoi A patch release was published some minutes ago, that should fix the problem: "Plesk Obsidian 18.0.47 Update 1".

 

[Hangover2]

Hello @ahoi + Plesk team,

the new update release did not solve the problem mentioned in this bug report. It does still exist.
In our case we are using remote SFTP storage.

Server 1:

"Exclude log files" is active
"Exclude specific files from the backup" is deactivated

Server 2:

"Exclude log files" is active
"Exclude specific files from the backup" is active

Both servers fail to run the nightly backups:

The following errors occurred during the scheduled backup process:

expected str, bytes or os.PathLike object, not int

 

[brhospedagem]

I'm using the backup schedule using as amazon s3 storage and it's returning the following error:


expected str, bytes or os.PathLike object, not int


I have Plesk updated to the latest version:
Version 18.0.47 Update #1

 

[Michael Gabriel]

same problem,
LOCAL backup tho,
NO exlcuded files !
update didnt fix.
manual backup works

 

[DadoO Team]

Same Thing when I have tried to do a backups

After then, I have received the same occured
BUT
I have tried another time, directly in the Plesk Interface, Backup, and now it seems to work
But I have erased all backup pfff

I'll keep you informed after one day, after the Auto Backup has working

 

[Hangover2]

I really wonder how it is possible that such an important core feature can be broken with a new Plesk release. Even the following patch release, that was dealing with another backup issue, did not handle that obvious bug. It feels like Plesk does not have a proper (automatic) unit / functional / system testing before new releases are published. For many Plesk clients backups are part of their SLAs to their own clients. This is more than a warning to everyone to disable automatic Plesk panel updates.

 

[DadoO Team]

Automatic Mode not working : ( Snif

But yerstaday I have done a complete backup but manually

Grrr

Les erreurs suivantes se sont produites pendant le processus de sauvegarde planifiée :

expected str, bytes or os.PathLike object, not int

 

[Misho]

As a workaround, consider disabling the Create a multivolume backup, volume size (MB) option in backup task settings.
If you follow this information you can schedule the backups until the problem has been resolved.

https://support.plesk.com/hc/en-us/articles/7861784085010?page=1#comment_7906311925138

 

[W4ru]

same issue here

Plesk Obsidian 18.0.47 Update #1

job: Backup split with exclusions full backup and also incremental

Manual start with identical parameters also aborts

 

[W4ru]

same issue here

Plesk Obsidian 18.0.47 Update #1

job: Backup split with exclusions full backup and also incremental

Manual start with identical parameters also aborts

Automatic update to
Plesk Obsidian Version 18.0.47 Update #2
is done. With the latest update the error seems to be fixed. Backup ran error-free and successfully. Thanks!