Hello,
Thanks a lot! That did the trick! I searched the entire documentation but didn't find how to overcome this specific case. But now when I try to create a component in Weblate, the server hangs. If I check the server console - I see that git waits for username/password in the server console. I want to use GitLab OAuth Authentication with gitlab application providing application id and application secret. For that I generated new application in our self-hosted GitLab server and then configured in $BASE_DIR/weblate/settings.py the following lines: SOCIAL_AUTH_GITLAB_KEY = '<application id generated by GitLab' SOCIAL_AUTH_GITLAB_SECRET = '<secret generated by GitLab>' SOCIAL_AUTH_GITLAB_SCOPE = ['api'] Do I need anything else additionally on Weblate side in order to work? I thought using Application in GiLab was enough. Or is that the GitLab OAuth Weblate Authentication works only with GitLab in the clound and not self-hosted? I don't want to provide username:password in the gitlab repository url, so the url I use is only https://gitlab.*** /<path to project>.git instead of https://username:password@gitlab.*** /<path to project>.git Or is that this type of authentication can be used only for individual user logins inside Weblate UI rather than authentication for gitlab itself? Thanks in advance! Kind regards, Anastas -----Original Message----- From: Weblate [mailto:[email protected]] On Behalf Of Michal Cihar Sent: Tuesday, September 18, 2018 9:56 PM To: [email protected] Subject: Re: [Weblate] Access https gitlab repository with invalid certificate Hello You can change Weblate git settings in $DATA_DIR/home/.gitconfig Still I'd recommend you to get have trusted SSL certs either by using globally accepted CA or installing your CA in system trusted certs. -- Michal Čihař | https://secure-web.cisco.com/1wmUo2xXBSLnDluKDKRxmYbK4fjvnFB8KHdz40AEfF_j8sXrpVjXDEFzhJz9L8fDS2Zw5oPV66VOTRSXeVxL0VPKPiczRdSJ6225Sm4g00LTKWl_hXXQF3vwdXoKMxu2_URJUAsk1aUyZFqOGNRSt_F5NBkVeV1ez7iRNKJlzEoZH7CZDvEbVSSQ4Po4G4_Qy7habVGO_W37LYc4jNGtJr2-Mi73paTxLbeBfnTajQ3pzA0iIT_2FMKjN3mxPfc5rl3oQOrCeQuN_YhlM-O3TwohtGICb5wZ4oLzIFCRQNO6Nr8pdkUPumuJcLfY3KEKkhtnu4SLOGDx4BWaKT26lpg/https%3A%2F%2Fcihar.com%2F | https://secure-web.cisco.com/1fPVz9v7jyfKgKq7hB4ezitiPV2iITOrthdQgEiNN80pDhJg66E1EzADujvgQRmzlQ-5Lyy9wGYZY_YgoXiHDeZtkyNFt2YRbl0Aa5tKstBkvCUNo-Ct-wT8gZH6YEGYBYWXlEkWBq0SEjJNjevg4ZLaPOKbG3PbIXm5mMS_JpJR_tlP09uvi41_1AAXUWJhoZh24e0E1XGPXE156yKQ52Q4ZCv4RXjBmD5Q1kNc7neR_bTRLHcHX3N-FDzpUZkfqM3P8IEYj4m4cK4FTkQEMT-tIYLw7ErbCZ_sRmUNVOxmmCmUc3B0crX684qjTxYbVn8pZRU6CLbWeFJbyrzQYNg/https%3A%2F%2Fweblate.org%2F On Tue, 2018-09-18 at 11:18 +0000, POPOV, Anastas (Devnya) BGR wrote: > Hello, > > We are trying to access gitlab self-hosted server via https but we get > this error: Failed to fetch repository: fatal: unable to access ' > https://gitlab.***': Peer certificate cannot be authenticated with > known CA certificates (128) > > Weblate is hosted on Linux RedHat server. > > When we try to execute git clone direcly we get the same error. After > setting up git config –global http.sslVerify false -> executing git > clone works, but Weblate still throws same error. > > Could you help us set up Weblate in such way that it take into account > global git setting to ignore sslVerify? > > Thanks in advance, > > Anastas Popov > Leading Developer > Group IT Applications Management & Architecture - Bulgaria > > 9160 Devnya - Bulgaria > [email protected]<mailto:[email protected]> > > Политика за защита на личните данни / GDPR Policy > _______________________________________________ > Weblate mailing list > [email protected]<mailto:[email protected]> > https://secure-web.cisco.com/13ABgVvJs5SfSnKFEEAGR06x1jhFx82I2O5ksNSPhxtqoRvpUjZ7DazWvFwhY_772G7xUCz6-wpIpvKdsoq6WXz3cJbwxMnov3fzOnk0O4Ovm3ZDDZt3oFFzxumiOHaT7625CD0XpYBYBprwSuj-1FCDaLLQf4NjQQl4xrxVjx6Hdj7Qjoyn5noHupZWLsAb_lIJ8N2f03RgkU6ZxOr2iNrrvytHnUxJV8EMEfp7SdYp230ZCUOW98EZLr0gar1fW8gEk62deO1tqfixKj5Gx7BsHKAdORkIpTQcACylyTMuYs8g9Mu_9JO4y84xjaxZaCkmzKuLeTuMb4aHoSPUxJg/https%3A%2F%2Flists.cihar.com%2Fcgi-bin%2Fmailman%2Flistinfo%2Fweblate Политика за защита на личните данни / GDPR Policy<https://www.devnyacement.bg/bg/personal_data>
_______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
