open_basedir restriction in effect

Hello,

Thank you for bringing this to our attention.

We are aware of the issues some users are facing with the latest version of BackWPUp and are currently working on a solution. In the meantime, you can try rolling back to an older version of the plugin. You can download previous versions from here and see if it helps.

We appreciate your patience and understanding.

Best regards,

When I turn on the fileinfo module for php, I encounter the same fault, and the fault remains after turning off the fileinfo module for php.

Solution:

Find fastcgi.conf in /usr/local/nginx/conf/ directory, regarding open_basedir the default configuration should be: fastcgi_param PHP_ADMIN_VALUE "open_basedir=$document_root/:/tmp/:/proc/";

Modify to: fastcgi_param PHP_ADMIN_VALUE "open_basedir=/home/wwwroot/:/tmp/:/proc/";

refer to: https://blog.csdn.net/peng646138471/article/details/105636617

Hello @youngtimer,

Thank you for your patience as we work on resolving the issue with the latest version.

To help us address the problem more effectively, could you please provide us with the following details:

1. Your PHP version.
2. Your Nginx version.
3. Debug information from the BackWPUp plugin settings. You can find this information by navigating to BackWPUp > Settings > Information and clicking on “Download Debug Info.”

This information will greatly assist us in identifying the cause of the issue and implementing a solution more quickly.

Thank you for your cooperation.

Best regards,

Hello,

Thank you so much for your cooperation.

We have identified the bug, and our development team is working on a fix. We appreciate your patience and understanding as we address this issue.

Thank you again for your support.

Best regards,

PHP-Version	8.1.10 (64bit)
Server	nginx/1.18.0

WordPress-Version: 6.5.4
BackWPup-Version: 4.1.1
PHP-Version: 8.1.10  (64bit)
MySQL-Version: 10.3.39-MariaDB-0ubuntu0.20.04.2
cURL-Version: 7.68.0
cURL-SSL-Version: OpenSSL/1.1.1f
WP-Cron-URL: https://example.com/wp-cron.php
Server-Selbstverbindung: Nicht erwartete HTTP-Antwort:
Status-Code: 200
Date: Mon, 24 Jun 2024 17:48:28 GMT
Content-type: text/html; charset=UTF-8
Vary: Accept-Encoding
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-control: no-cache, must-revalidate, max-age=0
Cf-cache-status: DYNAMIC
Report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=ER0U49OeAETE7zXcIyG8gfrvE8cjs38nuz8s%2FQrhyJxuFDTEGIn4JcrP3lWEyM0Jo2pGtadgsUKiPzLMrwILK061ECE5Y7KkInbAliPMOmgBnXsKk7p5%2FBZgl5TeFZqgSygZ"}],"group":"cf-nel","max_age":604800}
Nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
Cf-ray: 898e8c833b9701ed-CDG
Content-encoding: br
Alt-svc: h3=":443"; ma=86400

Document root: /var/www/example.com/web
Temp-Verzeichnis: /var/www/clients/client21/web24/web/wp-content/uploads/backwpup/0c4ffc/temp/
Protokoll-Verzeichnis: /var/www/clients/client21/web24/web/wp-content/uploads/backwpup-0c4ffc-logs/
Server: nginx/1.18.0
Betriebssystem: Linux
PHP-SAPI: fpm-fcgi
Aktueller PHP-User: web24
Maximale Skript-Laufzeit: 360 Sekunden
BackWPup Maximale Script-Ausführungszeit: 30 Sekunden
Alternative WP Cron: Aus
WP Cron abgeschaltet: An
Verzeichnis-Rechte: 493
Server-Zeit: 17:48
Zeit der Website: 19:48
Zeitzone der Website: Europe/Vienna
Zeitverschiebung der Website: 2 Stunden
Sprache der Website: de-DE
Zeichensatz des MySQL-Clients: utf8
PHP-Memory-Limit: 256M
WordPress-Memory-Limit: 40M
Maximales WordPress-Memory-Limit: 256M
Benutzter Speicher: 42,00 MB
Geladene PHP-Erweiterungen:: Core, FFI, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, imagick, imap, intl, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_sqlite, posix, pspell, readline, session, shmop, soap, sockets, sodium, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib

—

PS: Version 4.1.0 funktioniert wie immer perfekt!

• This reply was modified 9 months ago by Anonymous User 22040435.

Hello,

Thank you so much for your patience.

We have been able to fix the bug and would like to test if it is working for you before releasing it. Could you please download this patched version – https://we.tl/t-zHbF66Fvoz and test it on your staging site where the issue replicates?

Your confirmation and cooperation will be very helpful in ensuring the fix is effective.

Best regards,

Ja, hat fehlerfrei funktioniert! Danke!

Darf, soll man diese Version belassen oder besser auf die offizielle Version 4.1.2 warten?

Hello,

I’m glad to hear the version worked for you! Yes, you can continue using this version.

If you’re happy with the fix and overall experience, we would really appreciate it if you could leave a review at this link.

Thank you for your cooperation and support!

Best regards,

Hi, saranshwpm,

Your transfer expired. Would you please resend a transfer again?

Thanks,
Wyat

Hi @sunwei922,

We’ve released the fix in the latest version.

You can reinstall latest version and if issue persists, I would suggest to open new thread elaborating the issue you’re experiencing.

Best Regards,