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

Allow insecure HTTPS for Elasticsearch indexer #6775

New Issue
Open
opened 2025-11-02 07:06:18 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 07:06:18 -06:00
Owner
Copy Link

Originally created by @PhenX on GitHub (Jan 27, 2021).

  • Gitea version (or commit ref):
  • Git version:1.13.0
  • Operating system: Uubuntu 20.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No

Description

It would be useful to have a "Allow insecure" for the Elastic search indexer, like for MySQL or PgSQL (SSL_MODE = skip-verify / require), the mailer (SKIP_VERIFY) or for webhooks (SKIP_TLS_VERIFY), when using self signed certificates.

Originally created by @PhenX on GitHub (Jan 27, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version:1.13.0 - Operating system: Uubuntu 20.04 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No ## Description It would be useful to have a "Allow insecure" for the Elastic search indexer, like for MySQL or PgSQL (SSL_MODE = skip-verify / require), the mailer (SKIP_VERIFY) or for webhooks (SKIP_TLS_VERIFY), when using self signed certificates.
GiteaMirror added the type/enhancementtype/proposalissue/workaround labels 2025-11-02 07:06:18 -06:00
GiteaMirror commented 2025-11-02 07:06:19 -06:00
Author
Owner
Copy Link

@davidgraymi commented on GitHub (Jan 21, 2025):

I'm running into this issue myself. How did you get around it in development phase? I downloaded the cert from elasticsearch server but am not able to use it.

@davidgraymi commented on GitHub (Jan 21, 2025): I'm running into this issue myself. How did you get around it in development phase? I downloaded the cert from elasticsearch server but am not able to use it.
GiteaMirror commented 2025-11-02 07:06:19 -06:00
Author
Owner
Copy Link

@djds commented on GitHub (Jan 21, 2025):

You can work around this by setting SSL_CERT_DIR to a directory containing your custom certificate(s) or SSL_CERT_FILE to a file.

https://go.dev/src/crypto/x509/root_unix.go

@djds commented on GitHub (Jan 21, 2025): You can work around this by setting `SSL_CERT_DIR` to a directory containing your custom certificate(s) or `SSL_CERT_FILE` to a file. https://go.dev/src/crypto/x509/root_unix.go
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 issue/workaround type/enhancement type/proposal
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#6775
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?