Regardless the message error above, did the archive compressed/uploaded correctly at the expected WebDAV path?
The CURL message “An easy handle already added to a multi handle was attempted to get added a second time. (Added in 7.32.1)” is an warning due to some options that the plug-in used to connect the WebDAV remote host, but it’s not something critical.
Regarding the “curl_setopt_array(): CURLOPT_FOLLOWLOCATION cannot be activated when an open_basedir is set” this seems a bug in plug-in. It seems that while the PHP open_basedir is set the CURL option CURLOPT_FOLLOWLOCATION I’ve used should not be set. This is also a warning, not a critical issue. But thanks for reporting it, I will fix the code such that this will be avoided in the future.
As for the last message “PHP Warning: is_dir(): open_basedir restriction in effect. File(/tmp/mysql.sock) is not within the allowed path(s)” it looks like the plug-in attempted to scan the /tmp directory which seems that it’s not in the PHP allowed path (remember, your PHP configuration has open_basedir enabled). I guess your WP is hosted on a (free) shared web-server, right? Check to see if the plug-in Working Directory is set to /tmp/ and if that’s true then change it to a path within the allowed path(s), like /home/gameofsk/public_html/wp-content/plugins/wp-mybackup/tmp/my-tmp/
Thread Starter
rvnner
(@rvnner)
I changed the working dir and I can see now the archives created during backup, but there are no files copied to the owncloud.
There is no connection from the wp server to the apache server (access.log) on the owncloud.
Also, when I click on “backup targets->WebDav” it takes about two minutes for the page to load and in the Debug error log I get a record like:
[31-Jan-2016 19:43:45 Europe/Bucharest] PHP Warning: is_dir(): open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/gameofsk:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/gameofsk/public_html/wp-content/plugins/wp-mybackup/class/lib/editor/DiskTargetEditor.php on line 43
Curl debug log is empty.
My first guess is that your WebDAV settings are faulty (the host,path).
Please export your settings (.json format) and share them with me.
A .json file has a nice format (JSON) which can be viewed with some online tools like http://json.parser.online.fr
PS: Open the .json file and strip the sensitive credentials, if any.
If you can create for me a temporary WebDAV user/password on your WebDAV server (restricted to some tmp folder, I mean, secure it as needed) then I might try to test your scenario and come up with a solution. Eventually I will try to test the same scenario on my WebDAV test server, hopefully I got the same response like you.
Thread Starter
rvnner
(@rvnner)
I activated curl debug and I get the following error:
——————————————————————————–
[2016-01-31 20:00:50] URL=https://***/owncloud/remote.php/webdav
——————————————————————————–
[2016-01-31 20:00:50] Curl error code=7, HTTP code=0
——————————————————————————–
WebDAV like any other remote target is accessed via Curl library. So activating the Curl Debug was a wise thing.
Now, regarding the Curl error code 7, here is the list of Curl errors:
http://curl.haxx.se/libcurl/c/libcurl-errors.html
CURLE_COULDNT_CONNECT (7)
Failed to connect() to host or proxy.
Btw: do you use a proxy? If not then are you sure your webDAV host is visible from your WordPress server?
Thread Starter
rvnner
(@rvnner)
I use the same settings to backup to the owncloud some other apps via webdav (phone, laptop) and I checked them and they are working.
I will have to check with the hosting provider if there are some firewall rules preventing the connection to exit the wp server (the owncloud is in my house and I checked it’s firewall rules).
There is no proxy used.
Trying to export the settings I get:
File “/home/gameofsk/public_html/wp-content/plugins/wp-mybackup/tmp/logs/wpmybackup-options.json” does not exist. That`s rather odd
I checked with the file manager and the file isn’t there. I tried xml and ini with the same result.
File "xxxx" does not exist. That's rather odd
must be a bug. I’m going to check/fix it.
Thread Starter
rvnner
(@rvnner)
Ok, my provider allows only TCP 80 and 443 and I am using 8443, that’s why it’s not working.
So you sorted it out eventually, right?
