•  
      request #33996 Received HTTP code 400 from proxy after CONNECT
    Infos
    #33996
    Jörg Bernau (joerg_bernau)
    2023-08-29 09:37
    2023-08-23 19:33
    35635
    Details
    Received HTTP code 400 from proxy after CONNECT

    When Connectiong to gitlan a project is accessable/choosable, but whe we try to link it tuleap reports:

    500: Internal Server Error: Error returned by the GitLab server: cURL error 56: Received HTTP code 400 from proxy after CONNECT (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://git.example.com/api/v4/projects/55

    but

    curl --header "PRIVATE-TOKEN: glpat-AbTe8UpTi3gfNG9amUMn" --request GET "https://git.example.com/api/v4/projects/55/"

    returns a valid JSON object.

    Empty
    14.12
    EL9 (RockyLinux|AlmaLinux|RHEL)
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2023-08-29
    Attachments
    References
    References list is empty

    Follow-ups

    User avatar
    last edited by: Jörg Bernau (joerg_bernau) 2023-08-28 20:26

    Manuel, THX, you are right. Well git.example.com:443 is the nginx-proxy for gitlab worhhouse. So I removed sys_proxy and ended up in 500: Internal Server Error

    2023-08-28T19:49:47+02:00 [18138] [error] Unhandled exception: Encryption key must be SODIUM_CRYPTO_SECRETBOX_KEYBYTES long but is: 0 bytes: *)
    #0 /usr/share/tuleap/src/common/Cryptography/KeyFactory.php(45): Tuleap\Cryptography\Symmetric\EncryptionKey->__construct()
    #1 /usr/share/tuleap/plugins/gitlab/include/Repository/Webhook/WebhookCreator.php(99): Tuleap\Cryptography\KeyFactory->getEncryptionKey()
    #2 /usr/share/tuleap/plugins/gitlab/include/Repository/Webhook/WebhookCreator.php(80): Tuleap\Gitlab\Repository\Webhook\WebhookCreator->createNewGitlabWebhook()
    #3 /usr/share/tuleap/plugins/gitlab/include/Repository/GitlabRepositoryCreator.php(140): Tuleap\Gitlab\Repository\Webhook\WebhookCreator->generateWebhookInGitlabProject()
    #4 /usr/share/tuleap/plugins/gitlab/include/Repository/GitlabRepositoryCreator.php(115): Tuleap\Gitlab\Repository\GitlabRepositoryCreator->createGitlabRepositoryIntegration()
    #5 /usr/share/tuleap/src/vendor/paragonie/easydb/src/EasyDB.php(1263): Tuleap\Gitlab\Repository\GitlabRepositoryCreator->Tuleap\Gitlab\Repository\{closure}()
    #6 /usr/share/tuleap/src/common/DB/DBTransactionExecutorWithConnection.php(44): ParagonIE\EasyDB\EasyDB->tryFlatTransaction()
    #7 /usr/share/tuleap/plugins/gitlab/include/Repository/GitlabRepositoryCreator.php(120): Tuleap\DB\DBTransactionExecutorWithConnection->execute()
    #8 /usr/share/tuleap/plugins/gitlab/include/REST/v1/GitlabRepositoryResource.php(177): Tuleap\Gitlab\Repository\GitlabRepositoryCreator->integrateGitlabRepositoryInProject()
    #9 [internal function]: Tuleap\Gitlab\REST\v1\GitlabRepositoryResource->createGitlabRepository()
    #10 /usr/share/tuleap/src/vendor/luracast/restler/vendor/Luracast/Restler/Restler.php(1058): ReflectionMethod->invokeArgs()
    #11 /usr/share/tuleap/src/vendor/luracast/restler/vendor/Luracast/Restler/Restler.php(304): Luracast\Restler\Restler->call()
    #12 /usr/share/tuleap/src/www/api/index.php(91): Luracast\Restler\Restler->handle()
    #13 {main}
    

    *) source code modified for debugging

    FIXED: Just for google search: /etc/tuleap/conf/encryption_secret.key was empty. So close this request. Thanks for your support.

    User avatar

    I doubt that git.example.com is actually a proxy server so it's likely that tuleap config-set sys_proxy: git.example.com:443 causes the issue.

    User avatar
    last edited by: Jörg Bernau (joerg_bernau) 2023-08-25 17:34

    @vaceletm

    #> tuleap config-set sys_proxy: git.example.com:443

    #> tuleap config-get http_outbound_requests_deny_ranges: 0.0.0.0/0,::/0

    #> tuleap config-get http_outbound_requests_allow_ranges: '172.XXX.AAA.192/32,172.XXX.BBB.0/24,192.168.CCC.0/24'

    with 172.XXX.AAA.192/32 IP to public VPN proxy (nginx) on that gitlab is accessible externally; 172.XXX.BBB.0/24 company's VPN net and 192.168.CCC.0/24 LAN I which both servers are running (tuleap and gitlab are on the same machine)

    User avatar
    Thomas Gerbet (tgerbet)2023-08-25 15:46

    On a side note you have leaked what looks like a GitLab token, I would strongly recommend to revoke it if it is a valid one.