Deployment failed at Deploying Core Archive on Install - Githubissues

rainlab / deploy-plugin

A simple way to deploy your application to a remote location.

Other

16 stars 15 forks source link

Deployment failed at Deploying Core Archive on Install #55

Closed kevinvermeulenn closed 8 months ago

kevinvermeulenn commented 8 months ago

Hi! I've a beacon connection between local and live production. I'm getting an update failed after hitting the button Install October CMS at the stage of Deploying Core Archive.

I'm running php 8.2 and tried with php 8.3 too. Nothing works..

Error code below

October\Rain\Network\Http Object
(
    [url] => https://staging.domain.nl/?XOB_CMD=fileUpload&XOB=9870a6ec54644f188a19fc90a063cdfe&XOB_PAYLOAD=eyJjbWQiOiJmaWxlVXBsb2FkIiwibm9uY2UiOjE3MDkwMjk4MDAwfQ%3D%3D&XOB_SIGNATURE=wF%2BJl3i0bbj0oz8GMtn8TM1Fz6Q%2BhGqvb4h80adGWtT94zVrs2wsq9I%2FabH0upKnjMH4tXKwr%2F6sN84esYknHBxgpBpIUfz7B3ysenuel4aAvvqedcTE5iOjl5GE6wMgvjJXsHDAGJQaSUgyc372cgTRJWChPeYs1K473wGkqGbOaQuxe18kvKijDkqUOJ8R5UoiSwOiC71z1RqVBYlAxmHreT0Nq4WrtT1gHf1lRer8ds70dARaUtu42eBGgUgF04hPc2j0GTlNy3wbxGY4sLOVN3etzSM0YJF3NX2nof0A8P3JP4NOCgiH5GgOWD%2FMLZdqrxtnuCo5hmWhIq8fvw%3D%3D&XOB_FILENAME=07921ddf2cbe64d57578d98d171273fa&XOB_FILEHASH=3ba58395a1f9067defe6d221839d9142
    [method] => POST
    [headers] => Array
        (
            [HTTP/2] => 502
            [date] => Tue, 27 Feb 2024 10:31:51 GMT
            [content-type] => text/html; charset=iso-8859-1
            [content-length] => 320
            [server] => Apache/2.4.25 (Debian)
            [x-varnish-host] => ip-172-16-1-33
            [x-varnish] => 97112186
            [age] => 0
            [via] => 1.1 varnish (Varnish/5.0)
        )

    [headerCallbackFunc] =>
    [body] => <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Bad Gateway</title>
</head><body>
<h1>Bad Gateway</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
</p>
<hr>
<address>Apache/2.4.25 (Debian) Server at staging.domain.nl Port 8081</address>
</body></html>

    [rawBody] => HTTP/2 502
date: Tue, 27 Feb 2024 10:31:51 GMT
content-type: text/html; charset=iso-8859-1
content-length: 320
server: Apache/2.4.25 (Debian)
x-varnish-host: ip-172-16-1-33
x-varnish: 97112186
age: 0
via: 1.1 varnish (Varnish/5.0)

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Bad Gateway</title>
</head><body>
<h1>Bad Gateway</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
</p>
<hr>
<address>Apache/2.4.25 (Debian) Server at staging.domain.nl Port 8081</address>
</body></html>

    [code] => 502
    [info] => Array
        (
            [url] => https://staging.domain.nl/?XOB_CMD=fileUpload&XOB=9870a6ec54644f188a19fc90a063cdfe&XOB_PAYLOAD=eyJjbWQiOiJmaWxlVXBsb2FkIiwibm9uY2UiOjE3MDkwMjk4MDAwfQ%3D%3D&XOB_SIGNATURE=wF%2BJl3i0bbj0oz8GMtn8TM1Fz6Q%2BhGqvb4h80adGWtT94zVrs2wsq9I%2FabH0upKnjMH4tXKwr%2F6sN84esYknHBxgpBpIUfz7B3ysenuel4aAvvqedcTE5iOjl5GE6wMgvjJXsHDAGJQaSUgyc372cgTRJWChPeYs1K473wGkqGbOaQuxe18kvKijDkqUOJ8R5UoiSwOiC71z1RqVBYlAxmHreT0Nq4WrtT1gHf1lRer8ds70dARaUtu42eBGgUgF04hPc2j0GTlNy3wbxGY4sLOVN3etzSM0YJF3NX2nof0A8P3JP4NOCgiH5GgOWD%2FMLZdqrxtnuCo5hmWhIq8fvw%3D%3D&XOB_FILENAME=07921ddf2cbe64d57578d98d171273fa&XOB_FILEHASH=3ba58395a1f9067defe6d221839d9142
            [content_type] => text/html; charset=iso-8859-1
            [http_code] => 502
            [header_size] => 243
            [request_size] => 764
            [filetime] => -1
            [ssl_verify_result] => 0
            [redirect_count] => 0
            [total_time] => 110.936217
            [namelookup_time] => 0.002905
            [connect_time] => 0.333403
            [pretransfer_time] => 0.970401
            [size_upload] => 17158134
            [size_download] => 320
            [speed_download] => 2
            [speed_upload] => 154666
            [download_content_length] => 320
            [upload_content_length] => 17158134
            [starttransfer_time] => 0.970408
            [redirect_time] => 0
            [redirect_url] =>
            [primary_ip] => 2a05:d018:964:c0a:a58f:6b32:e401:3d8a
            [certinfo] => Array
                (
                )

            [primary_port] => 443
            [local_ip] => 2406:2d40:4417:f910:2cbc:fef4:d567:9a8e
            [local_port] => 61389
            [http_version] => 3
            [protocol] => 2
            [ssl_verifyresult] => 0
            [scheme] => HTTPS
            [appconnect_time_us] => 970106
            [connect_time_us] => 333403
            [namelookup_time_us] => 2905
            [pretransfer_time_us] => 970401
            [redirect_time_us] => 0
            [starttransfer_time_us] => 970408
            [total_time_us] => 110936217
        )

    [requestOptions] =>
    [requestData] => Array
        (
            [file] => CURLFile Object
                (
                    [name] => /Applications/MAMP/htdocs/website2024/storage/temp/ocbl-ba2381297a34e4933f78914fb3bfb00a.arc
                    [mime] =>
                    [postname] =>
                )

        )

    [requestHeaders] =>
    [argumentSeparator] => &
    [streamFile] =>
    [streamFilter] =>
    [maxRedirects] => 10
    [redirectCount:protected] =>
    [hasFileData:protected] => 1
)

daftspunk commented 8 months ago

Hi @kevinvermeulenn

This looks like your server has not accepted the core archive file as an upload, which can be up to 20mb. To solve this, increase the acceptable upload size from the server to around 32mb.

To increase the maximum upload size in PHP, you need to modify some settings in your php.ini file. Specifically, the upload_max_filesize and post_max_size directives are of interest:

upload_max_filesize: This directive controls the maximum size for uploaded files.
post_max_size: This directive limits the maximum size for POST data, which should be larger than upload_max_filesize to account for all form data.

I hope this helps!

kevinvermeulenn commented 8 months ago

Unfortunately, this doesn't work. The hosting company updated it at their side. Assuming it is something at the hosting's to be fixed. I'm running on the main domain already a live OC2 website. And a live OC3 on other domain (same hosting company).

Also, I tried with a clean installation but it doesn't work either.

daftspunk commented 8 months ago

No worries. This is only a guess since the underlying error message is hidden by a reverse proxy (Varnish)

This is the only error message: The proxy server received an invalid response from an upstream server.

Please ask the hosting company to check the web server error logs for the exact error message at the given timestamp: Tue, 27 Feb 2024 10:31:51 GMT

I hope this helps.