Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #31956 500: Internal Server Error: Error returned by the GitLab server: cURL error 56: Received HTTP code 407 from proxy after CONNECT (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
    Actions
    Infos
    #31956
    Soumik Debnath (soumikdebnath)
    2023-05-23 12:53
    2023-05-23 11:39
    33584
    Details
    500: Internal Server Error: Error returned by the GitLab server: cURL error 56: Received HTTP code 407 from proxy after CONNECT (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

    Gitlab and Tuleap was running in the same server after upgrading to v14.8 this issue is coming, 500: Internal Server Error: Error returned by the GitLab server: cURL error 56: Received HTTP code 407 from proxy after CONNECT (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

    SCM/GitLab
    14.8
    EL7 (CentOS|RHEL)
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Declined
    2023-05-23
    Attachments
    Artifact links
    Empty
    By Soumik Debnath (soumikdebnath)
    (50 kB)
    Screenshot from 2023-05-23 15-01-27.png
    By Soumik Debnath (soumikdebnath)
    (17 kB)
    Screenshot from 2023-05-23 16-23-16.png
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Soumik Debnath (soumikdebnath)2023-05-23 12:53

    Currently this is the issue coming in the Log, The secret provided by the GitLab webhook does not match the expected secret.

    User avatar
    Thomas Gerbet (tgerbet)2023-05-23 12:43

    Failed to connect to remote host: dial tcp 127.0.0.1:443: connect: connection refused

    This likely means the service is not up.

    For information we strongly recommend against hosting Tuleap with another app on the same server because you very likely to encounter conflicts between the two.

    User avatar
    Soumik Debnath (soumikdebnath)2023-05-23 12:35

    Webhooks are now failing,

    Response 400 Headers Server: nginx Date: Tue, 23 May 2023 10:34:23 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: close Set-Cookie: __Host-TULEAP_PHPSESSID=r3l0j03kdb3t8flv36onn0vddd; path=/; secure; HttpOnly; SameSite=Lax X-Ua-Compatible: IE=Edge Referrer-Policy: no-referrer-when-downgrade, strict-origin, same-origin X-Frame-Options: DENY X-Content-Type-Options: nosniff X-Xss-Protection: 1; mode=block Content-Security-Policy: default-src 'report-sample'; base-uri 'self'; frame-ancestors 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' 'report-sample' ; style-src 'self' 'unsafe-inline' 'report-sample'; font-src 'self'; form-action 'self'; manifest-src 'self'; img-src * data: blob:; connect-src *; child-src *; upgrade-insecure-requests; report-uri /csp-violation; Cache-Control: no-store Cross-Origin-Opener-Policy: same-origin Vary: Sec-Fetch-Site

    User avatar
    Soumik Debnath (soumikdebnath)2023-05-23 12:30

    My Current settings are, http_outbound_requests_allow_ranges has been successfully updated from '127.0.0.0/24' to '10.10.10.0/24,192.168.56.0/24,127.0.0.0/24'

    Still seeing this error: (Failed to connect to remote host: dial tcp 127.0.0.1:443: connect: connection refused)