github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Migration failed: SSL Certificate problem: unable to get Local Issuer #2623

New Issue
Closed
opened 2025-11-02 04:42:29 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:42:29 -06:00
Owner
Copy Link

Originally created by @toni-moreno on GitHub (Dec 5, 2018).

  • Gitea version (or commit ref): fdec258
  • Git version: git inside gitea 2.18.1
  • Operating system: (working on docker oficial image gitea/gitea) alpine 3.8.1
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
2018/12/05 12:15:21 [.../api/v1/repo/repo.go:409 Migrate()] [E] MigrateRepository: Clone: exit status 128 - fatal: unable to access 'https://%3Ccredentials%3E@myserver/my-repo.git/': SSL certificate problem: unable to get local issuer certificate

2018/12/05 12:16:04 [.../api/v1/repo/repo.go:409 Migrate()] [E] MigrateRepository: Clone: exit status 128 - fatal: unable to access 'https://%3Ccredentials%3E@myserver/my-repo.git/': SSL certificate problem: unable to get local issuer certificate

Description

Can not clone from internal (self-signed ) gitlab servers and there is not option into the UI to configure the git client config like

git config http.sslVerify false

How can I allow the migration from "unsecured" SSL gitlab servers?
...

Originally created by @toni-moreno on GitHub (Dec 5, 2018). - Gitea version (or commit ref): fdec258 - Git version: git inside gitea 2.18.1 - Operating system: (working on docker oficial image gitea/gitea) alpine 3.8.1 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ````bash 2018/12/05 12:15:21 [.../api/v1/repo/repo.go:409 Migrate()] [E] MigrateRepository: Clone: exit status 128 - fatal: unable to access 'https://%3Ccredentials%3E@myserver/my-repo.git/': SSL certificate problem: unable to get local issuer certificate 2018/12/05 12:16:04 [.../api/v1/repo/repo.go:409 Migrate()] [E] MigrateRepository: Clone: exit status 128 - fatal: unable to access 'https://%3Ccredentials%3E@myserver/my-repo.git/': SSL certificate problem: unable to get local issuer certificate ```` ## Description Can not clone from internal (self-signed ) gitlab servers and there is not option into the UI to configure the git client config like ```` git config http.sslVerify false ```` How can I allow the migration from "unsecured" SSL gitlab servers? ...
GiteaMirror commented 2025-11-02 04:42:30 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Dec 5, 2018):

You can import ssl certificate in server certificate store and restart gitea as workaround

@lafriks commented on GitHub (Dec 5, 2018): You can import ssl certificate in server certificate store and restart gitea as workaround
GiteaMirror commented 2025-11-02 04:42:30 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 8, 2018):

@toni-moreno you could change git config --global http.sslVerify false on gitea server host.

@lunny commented on GitHub (Dec 8, 2018): @toni-moreno you could change `git config --global http.sslVerify false` on gitea server host.
GiteaMirror commented 2025-11-02 04:42:30 -06:00
Author
Owner
Copy Link

@toni-moreno commented on GitHub (Dec 12, 2018):

export GIT_SSL_NO_VERIFY=true on the docker image work for me Thank you!!

@toni-moreno commented on GitHub (Dec 12, 2018): export GIT_SSL_NO_VERIFY=true on the docker image work for me Thank you!!
GiteaMirror commented 2025-11-02 04:42:30 -06:00
Author
Owner
Copy Link

@giorgosn commented on GitHub (Jun 10, 2020):

git config --global http.sslVerify false

It did not worked for me. On a gitea server and a jankins server.

@giorgosn commented on GitHub (Jun 10, 2020): > git config --global http.sslVerify false It did not worked for me. On a gitea server and a jankins server.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2623
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?