• zedomingues

    (@zedomingues)


    Hello, first, congratulations on the excellent Plugin

    I’ve been experiencing some problems with the plugin a new site.

    I already use the plugin on other sites (hosted on a different company’s of the new website wich is in trouble).

    with LOCAWEB hosting company, the plugin backs up, connects with the azure microsof server and correctly sends the ZIP file.

    the new hosting company (HostGator), I’ve been experiencing for days connection problems with azure services.

    for example, HostGator blocks output ports for pens cache service. I had to ask to change.

    however, in hostgator the plugin always shows this error (reported in the log)

    [INFO] BackWPup 3.3.1; A project of Inpsyde GmbH
    [INFO] Log Level: Normal
    [INFO] BackWPup job: Backup Manual2
    [INFO] Logfile is: backwpup_*****_2016-05-11_15-15-41.html
    [INFO] Backup file is: backwpup_****_2016-05-11_15-15-41.zip
    [11-May-2016 15:15:41] 1. Try to backup database …
    [11-May-2016 15:15:41] Connected to database *****
    [11-May-2016 15:15:43] Added database dump “****” with 425,53 kB to backup file list
    [11-May-2016 15:15:43] Database backup done!
    [11-May-2016 15:15:43] 1. Trying to make a list of folders to back up …
    [11-May-2016 15:15:44] Added “wp-config.php” to backup file list
    [11-May-2016 15:15:44] 570 folders to backup.
    [11-May-2016 15:15:44] 1. Trying to generate a file with installed plugin names …
    [11-May-2016 15:15:44] Added plugin list file “*****” with 1,76 kB to backup file list.
    [11-May-2016 15:15:44] 1. Trying to generate a manifest file …
    [11-May-2016 15:15:44] Added manifest.json file with 4,26 kB to backup file list.
    [11-May-2016 15:15:45] 1. Trying to create backup archive …
    [11-May-2016 15:15:45] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [11-May-2016 15:18:22] Backup archive created.
    [11-May-2016 15:18:22] Archive size is 25,28 MB.
    [11-May-2016 15:18:22] 4373 Files with 56,07 MB in Archive.
    [11-May-2016 15:18:23] 1. Try sending backup to a Microsoft Azure (Blob) …
    [11-May-2016 15:18:23] Connected to MS Azure container “****”.
    [11-May-2016 15:18:23] Starting upload to MS Azure …
    [11-May-2016 15:19:24] ERROR: Microsoft Azure API: Request timed out due to default_socket_timeout php.ini setting
    [11-May-2016 15:19:26] 2. Try sending backup to a Microsoft Azure (Blob) …
    [11-May-2016 15:19:26] Connected to MS Azure container “****”.
    [11-May-2016 15:19:26] Starting upload to MS Azure …
    [11-May-2016 15:20:27] ERROR: Microsoft Azure API: Request timed out due to default_socket_timeout php.ini setting
    [11-May-2016 15:20:28] 3. Try sending backup to a Microsoft Azure (Blob) …
    [11-May-2016 15:20:29] Connected to MS Azure container “*****”.
    [11-May-2016 15:20:29] Starting upload to MS Azure …
    [11-May-2016 15:21:31] ERROR: Microsoft Azure API: Request timed out due to default_socket_timeout php.ini setting
    [11-May-2016 15:21:32] ERROR: Step aborted: too many attempts!
    [11-May-2016 15:21:32] ERROR: Job has ended with errors in 351 seconds. You must resolve the errors for correct execution.

    when I look at the input values “default_socket_timeout” in php.info, the value is 60 (and the maximum allowed on the server is also 60).

    But, in hosting where the plugin work perfectly(LOCAWEB), the value of the “default_socket_timeout” entry is also 60.

    there is another plugin on the site that also connects to the storage service azure (https://br.ww.wp.xz.cn/plugins/windows-azure-storage/) and has worked properly.

    Finally, there is some news that HostGator blocks the use of the plugin or interfere in its use?

    I need to ask for Hostgator release any more port? I need to get some file? Because I’m not seeing exits.

    tks for your attention

    https://ww.wp.xz.cn/plugins/backwpup/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    BackWPup uploads the archive in chunks, because files can be go very large. That can be the differnce to the other plugin.

    Normle the connect to Azur will be done over port 443 (https) and the normely connection will work. That is why i think it has nothing to to with opening ports.

    I will update Azure to a newer SDK but that SDK will have minimum PHP Version of 5.5. In the newer SDK they will change the way how the files will be uploaded.

    Thread Starter zedomingues

    (@zedomingues)

    Hello Daniel Hüsken

    I Got it.

    The plugin is running an apache server with php 7.

    Or contrary to another company (LOCAWEB) that runs on php 5.5

    Can it be that so?

    tks

    Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    Nomely not. I will look that i update the SDK. But that will take some time.

    Thread Starter zedomingues

    (@zedomingues)

    Dear, Daniel Hüsken

    I did a downgrade in php version (to 5.5). Unfortunately the problem still persists.

    I thank helpfulness, wait for the update the SDK.

    Thread Starter zedomingues

    (@zedomingues)

    *I will wait for the update

    Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    Ok i will test it in the next time and respond you.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘icrosoft Azure API: Request timed out due to default_socket_timeout php.ini’ is closed to new replies.