MongoDB - AuthenticationFailed #1171

New Issue

Closed

opened 2026-03-22 17:13:13 -05:00 by GiteaMirror · 11 comments

GiteaMirror commented 2026-03-22 17:13:13 -05:00

Owner

Copy Link

Copy Source

Originally created by @wardwygaerts on GitHub (May 14, 2025).

I wanted to test komodo and tried with MongoDB, but failes

komodo-core        | Error: task 9 panicked with message "called `Result::unwrap()` on an `Err` value: failed to initialize database client\n\nCaused by:\n    failed to create index | index: enabled | error: Error { kind: Authentication { message: \"SCRAM failure: Authentication failed.\" }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: \"AuthenticationFailed\", message: \"Authentication failed.\", topology_version: None }), labels: {}, wire_version: None, source: None }) }"

No error in mongodb

When using postgres, everything is working fine, but I prefer not to have the additional ferret layer.

services:
  mongo:
    image: mongo
    labels:
      komodo.skip: null # Prevent Komodo from stopping with StopAllContainers
    command: --quiet --wiredTigerCacheSizeGB 0.25
    restart: unless-stopped
    logging:
      driver: ${COMPOSE_LOGGING_DRIVER:-local}
    # ports:
    #   - 27017:27017
    volumes:
      - mongo-data:/data/db
      - mongo-config:/data/configdb
    environment:
      - MONGO_INITDB_ROOT_USERNAME=${KOMODO_DB_USERNAME}
      - MONGO_INITDB_ROOT_PASSWORD=${KOMODO_DB_PASSWORD}
  core:
    image: ghcr.io/moghtech/komodo-core:latest
    container_name: komodo-core
    labels:
      komodo.skip: null
    restart: unless-stopped
    depends_on:
      #- ferretdb
      - mongo
    logging:
      driver: local
    ports:
      - 9120:9120
    env_file: .env
    environment:
      KOMODO_DATABASE_ADDRESS: mongo:27017
      KOMODO_DATABASE_USERNAME: ${KOMODO_DB_USERNAME}
      KOMODO_DATABASE_PASSWORD: ${KOMODO_DB_PASSWORD}
    volumes:
      ## Core cache for repos for latest commit hash / contents
      - repo-cache:/repo-cache
      ## Store sync files on server
      # - /path/to/syncs:/syncs

Originally created by @wardwygaerts on GitHub (May 14, 2025). I wanted to test komodo and tried with MongoDB, but failes ``` komodo-core | Error: task 9 panicked with message "called `Result::unwrap()` on an `Err` value: failed to initialize database client\n\nCaused by:\n failed to create index | index: enabled | error: Error { kind: Authentication { message: \"SCRAM failure: Authentication failed.\" }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: \"AuthenticationFailed\", message: \"Authentication failed.\", topology_version: None }), labels: {}, wire_version: None, source: None }) }" ``` No error in mongodb When using postgres, everything is working fine, but I prefer not to have the additional ferret layer. ``` services: mongo: image: mongo labels: komodo.skip: null # Prevent Komodo from stopping with StopAllContainers command: --quiet --wiredTigerCacheSizeGB 0.25 restart: unless-stopped logging: driver: ${COMPOSE_LOGGING_DRIVER:-local} # ports: # - 27017:27017 volumes: - mongo-data:/data/db - mongo-config:/data/configdb environment: - MONGO_INITDB_ROOT_USERNAME=${KOMODO_DB_USERNAME} - MONGO_INITDB_ROOT_PASSWORD=${KOMODO_DB_PASSWORD} core: image: ghcr.io/moghtech/komodo-core:latest container_name: komodo-core labels: komodo.skip: null restart: unless-stopped depends_on: #- ferretdb - mongo logging: driver: local ports: - 9120:9120 env_file: .env environment: KOMODO_DATABASE_ADDRESS: mongo:27017 KOMODO_DATABASE_USERNAME: ${KOMODO_DB_USERNAME} KOMODO_DATABASE_PASSWORD: ${KOMODO_DB_PASSWORD} volumes: ## Core cache for repos for latest commit hash / contents - repo-cache:/repo-cache ## Store sync files on server # - /path/to/syncs:/syncs ```

GiteaMirror closed this issue 2026-03-22 17:13:14 -05:00

GiteaMirror commented 2026-03-22 17:13:15 -05:00

Author

Owner

Copy Link

Copy Source

@yunus-acar commented on GitHub (May 14, 2025):

I had a similar problem. Did you solve it? @wardwygaerts

@yunus-acar commented on GitHub (May 14, 2025): I had a similar problem. Did you solve it? @wardwygaerts

GiteaMirror commented 2026-03-22 17:13:15 -05:00

Author

Owner

Copy Link

Copy Source

@cehenriques commented on GitHub (May 18, 2025):

I had 2 issues with the Mongo setup that I solved:

• First, the Mongo compose didn't have the "env_file" property to pass the environment variables from the compose.env file.
• Second, I had issues running Mongo on my Proxmox VM - "MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!". Solved it by changing the CPU typo to "Host" on the VM settings.

@cehenriques commented on GitHub (May 18, 2025): I had 2 issues with the Mongo setup that I solved: - First, the Mongo compose didn't have the "env_file" property to pass the environment variables from the compose.env file. - Second, I had issues running Mongo on my Proxmox VM - "MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!". Solved it by changing the CPU typo to "Host" on the VM settings.

GiteaMirror commented 2026-03-22 17:13:16 -05:00

Author

Owner

Copy Link

Copy Source

@EliasMasche commented on GitHub (Jun 11, 2025):

I am having the same issue, too

called `Result::unwrap()` on an `Err` value: failed to initialize database client

Caused by:

    failed to create index | index: enabled | error: Error { kind: Authentication { message: "SCRAM failure: Authentication failed." }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: "AuthenticationFailed", message: "Authentication failed.", topology_version: None }), labels: {}, wire_version: None, source: None }) }

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Error: task 5 panicked with message "called `Result::unwrap()` on an `Err` value: failed to initialize database client\n\nCaused by:\n    failed to create index | index: enabled | error: Error { kind: Authentication { message: \"SCRAM failure: Authentication failed.\" }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: \"AuthenticationFailed\", message: \"Authentication failed.\", topology_version: None }), labels: {}, wire_version: None, source: None }) }"

Running on bare metal, my CPU supports AVX, and adding env_file: ./compose.env didn't help either

@EliasMasche commented on GitHub (Jun 11, 2025): I am having the same issue, too ```rust called `Result::unwrap()` on an `Err` value: failed to initialize database client Caused by: failed to create index | index: enabled | error: Error { kind: Authentication { message: "SCRAM failure: Authentication failed." }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: "AuthenticationFailed", message: "Authentication failed.", topology_version: None }), labels: {}, wire_version: None, source: None }) } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Error: task 5 panicked with message "called `Result::unwrap()` on an `Err` value: failed to initialize database client\n\nCaused by:\n failed to create index | index: enabled | error: Error { kind: Authentication { message: \"SCRAM failure: Authentication failed.\" }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: \"AuthenticationFailed\", message: \"Authentication failed.\", topology_version: None }), labels: {}, wire_version: None, source: None }) }" ``` Running on bare metal, my CPU supports AVX, and adding `env_file: ./compose.env` didn't help either

GiteaMirror commented 2026-03-22 17:13:17 -05:00

Author

Owner

Copy Link

Copy Source

@wardwygaerts commented on GitHub (Jun 17, 2025):

I had a similar problem. Did you solve it? @wardwygaerts

I removed everything, added a network and redeployed. Everything's working fine now

@wardwygaerts commented on GitHub (Jun 17, 2025): > I had a similar problem. Did you solve it? [@wardwygaerts](https://github.com/wardwygaerts) I removed everything, added a network and redeployed. Everything's working fine now

GiteaMirror commented 2026-03-22 17:13:17 -05:00

Author

Owner

Copy Link

Copy Source

@EliasMasche commented on GitHub (Jun 17, 2025):

Can you share your changes to verify if it will work on my side, too?

@EliasMasche commented on GitHub (Jun 17, 2025): Can you share your changes to verify if it will work on my side, too?

GiteaMirror commented 2026-03-22 17:13:18 -05:00

Author

Owner

Copy Link

Copy Source

@wardwygaerts commented on GitHub (Jun 18, 2025):

@EliasMasche :

docker-compose:

services:
  mongo:
    image: mongo
    container_name: komodo-mongo
    labels:
      komodo.skip: null
    command: --quiet --wiredTigerCacheSizeGB 0.25
    restart: unless-stopped
    networks:
      - local
    # ports:
    #   - 27017:27017
    env_file: .env
    volumes:
      - mongo-data:/data/db
      - mongo-config:/data/configdb
    environment:
      MONGO_INITDB_ROOT_USERNAME: ${KOMODO_DB_USERNAME}
      MONGO_INITDB_ROOT_PASSWORD: ${KOMODO_DB_PASSWORD}
  core:
    image: ghcr.io/moghtech/komodo-core:latest
    container_name: komodo-core
    labels:
      komodo.skip: null
    restart: unless-stopped
    depends_on:
      - mongo
    logging:
      driver: local
    networks:
      - local
    ports:
      - 9121:9120
    env_file: .env
    environment:
      KOMODO_DATABASE_ADDRESS: mongo:27017
      KOMODO_DATABASE_USERNAME: ${KOMODO_DB_USERNAME}
      KOMODO_DATABASE_PASSWORD: ${KOMODO_DB_PASSWORD}
      #KOMODO_DATABASE_URI: mongodb://${KOMODO_DB_USERNAME}:${KOMODO_DB_PASSWORD}@ferretdb:27017/${KOMODO_DATABASE_DB_NAME:-komodo}?authMechanism=PLAIN
    volumes:
      - repo-cache:/repo-cache
volumes:
  # Mongo
  mongo-data: null
  mongo-config: null
  repo-cache: null
networks:
  local:
    external: true

env:

# DB credentials
KOMODO_DB_USERNAME=admin
KOMODO_DB_PASSWORD=*************************

# Configure a secure passkey to authenticate between Core / Periphery.
KOMODO_PASSKEY=*******************************

# General
KOMODO_HOST=http://192.x.x.x:9121
KOMODO_TITLE=Komodo
KOMODO_DISABLE_CONFIRM_DIALOG=false

KOMODO_MONITORING_INTERVAL="15-sec"
KOMODO_RESOURCE_POLL_INTERVAL="5-min"

# Secrets
KOMODO_WEBHOOK_SECRET=a_random_secret
KOMODO_JWT_SECRET=a_random_jwt_secret

# Auth
KOMODO_LOCAL_AUTH=true
KOMODO_DISABLE_USER_REGISTRATION=false
KOMODO_ENABLE_NEW_USERS=true
KOMODO_DISABLE_NON_ADMIN_CREATE=false
KOMODO_TRANSPARENT_MODE=false

KOMODO_JWT_TTL="1-day"

@wardwygaerts commented on GitHub (Jun 18, 2025): @EliasMasche : docker-compose: ``` services: mongo: image: mongo container_name: komodo-mongo labels: komodo.skip: null command: --quiet --wiredTigerCacheSizeGB 0.25 restart: unless-stopped networks: - local # ports: # - 27017:27017 env_file: .env volumes: - mongo-data:/data/db - mongo-config:/data/configdb environment: MONGO_INITDB_ROOT_USERNAME: ${KOMODO_DB_USERNAME} MONGO_INITDB_ROOT_PASSWORD: ${KOMODO_DB_PASSWORD} core: image: ghcr.io/moghtech/komodo-core:latest container_name: komodo-core labels: komodo.skip: null restart: unless-stopped depends_on: - mongo logging: driver: local networks: - local ports: - 9121:9120 env_file: .env environment: KOMODO_DATABASE_ADDRESS: mongo:27017 KOMODO_DATABASE_USERNAME: ${KOMODO_DB_USERNAME} KOMODO_DATABASE_PASSWORD: ${KOMODO_DB_PASSWORD} #KOMODO_DATABASE_URI: mongodb://${KOMODO_DB_USERNAME}:${KOMODO_DB_PASSWORD}@ferretdb:27017/${KOMODO_DATABASE_DB_NAME:-komodo}?authMechanism=PLAIN volumes: - repo-cache:/repo-cache volumes: # Mongo mongo-data: null mongo-config: null repo-cache: null networks: local: external: true ``` env: ``` # DB credentials KOMODO_DB_USERNAME=admin KOMODO_DB_PASSWORD=************************* # Configure a secure passkey to authenticate between Core / Periphery. KOMODO_PASSKEY=******************************* # General KOMODO_HOST=http://192.x.x.x:9121 KOMODO_TITLE=Komodo KOMODO_DISABLE_CONFIRM_DIALOG=false KOMODO_MONITORING_INTERVAL="15-sec" KOMODO_RESOURCE_POLL_INTERVAL="5-min" # Secrets KOMODO_WEBHOOK_SECRET=a_random_secret KOMODO_JWT_SECRET=a_random_jwt_secret # Auth KOMODO_LOCAL_AUTH=true KOMODO_DISABLE_USER_REGISTRATION=false KOMODO_ENABLE_NEW_USERS=true KOMODO_DISABLE_NON_ADMIN_CREATE=false KOMODO_TRANSPARENT_MODE=false KOMODO_JWT_TTL="1-day" ```

GiteaMirror commented 2026-03-22 17:13:19 -05:00

Author

Owner

Copy Link

Copy Source

@EliasMasche commented on GitHub (Jun 19, 2025):

Thanks with this was enough for the trick, now it works fine.

networks:
  local:
    external: true

@EliasMasche commented on GitHub (Jun 19, 2025): Thanks with this was enough for the trick, now it works fine. ```yaml networks: local: external: true ```

GiteaMirror commented 2026-03-22 17:13:19 -05:00

Author

Owner

Copy Link

Copy Source

@victornavorskie commented on GitHub (Jun 25, 2025):

I have the same issue and nothing works after the Komodo v1.18.0 version (https://github.com/moghtech/komodo/releases/tag/v1.18.0). Neither FerretDB nor MongoDB work, and I have even removed everything and set up from scratch. I have added labels for Traefik, which was working before and still is, but the Komodo core is full of MongoDB errors, such as 'Authentication Failed'.
Starting on http://[::]:9120
core-1 | 2025-06-25T11:54:55.429023Z ERROR core::schedule: failed to get actions for schedule update | failed to get all actions from db: Kind: SCRAM failure: password authentication failed for user 'admin', labels: {": Kind: Command failed: Error code 1 (InternalError): Password authentication failed for user 'admin', labels: {}.
Still not fixed.

@victornavorskie commented on GitHub (Jun 25, 2025): I have the same issue and nothing works after the Komodo v1.18.0 version (https://github.com/moghtech/komodo/releases/tag/v1.18.0). Neither FerretDB nor MongoDB work, and I have even removed everything and set up from scratch. I have added labels for Traefik, which was working before and still is, but the Komodo core is full of MongoDB errors, such as 'Authentication Failed'. Starting on http://[::]:9120 `core-1 | 2025-06-25T11:54:55.429023Z ERROR core::schedule: failed to get actions for schedule update | failed to get all actions from db: Kind: SCRAM failure: password authentication failed for user 'admin', labels: {": Kind: Command failed: Error code 1 (InternalError): Password authentication failed for user 'admin', labels: {}. ` Still not fixed.

GiteaMirror commented 2026-03-22 17:13:20 -05:00

Author

Owner

Copy Link

Copy Source

@terroreek commented on GitHub (Aug 14, 2025):

I can confirm I am getting the same error with the docker compose file, the komodo-core-1 container is just stuck in a continuous reboot cycle.

2025-08-14T15:39:49.612256748Z thread 'tokio-runtime-worker' panicked at bin/core/src/state.rs:47:6:
2025-08-14T15:39:49.612261238Z called `Result::unwrap()` on an `Err` value: failed to initialize database client
2025-08-14T15:39:49.612273677Z 
2025-08-14T15:39:49.612276027Z Caused by:
2025-08-14T15:39:49.612278357Z     failed to create index | index: enabled | error: Error { kind: Authentication { message: "SCRAM failure: Authentication failed." }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: "AuthenticationFailed", message: "Authentication failed.", topology_version: None }), labels: {}, wire_version: None, source: None }) }
2025-08-14T15:39:49.612281547Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-08-14T15:39:49.613656382Z Error: task 49 panicked with message "called `Result::unwrap()` on an `Err` value: failed to initialize database client\n\nCaused by:\n    failed to create index | index: enabled | error: Error { kind: Authentication { message: \"SCRAM failure: Authentication failed.\" }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: \"AuthenticationFailed\", message: \"Authentication failed.\", topology_version: None }), labels: {}, wire_version: None, source: None }) }"

@terroreek commented on GitHub (Aug 14, 2025): I can confirm I am getting the same error with the docker compose file, the komodo-core-1 container is just stuck in a continuous reboot cycle. ```2025-08-14T15:39:49.612239398Z 2025-08-14T15:39:49.612256748Z thread 'tokio-runtime-worker' panicked at bin/core/src/state.rs:47:6: 2025-08-14T15:39:49.612261238Z called `Result::unwrap()` on an `Err` value: failed to initialize database client 2025-08-14T15:39:49.612273677Z 2025-08-14T15:39:49.612276027Z Caused by: 2025-08-14T15:39:49.612278357Z failed to create index | index: enabled | error: Error { kind: Authentication { message: "SCRAM failure: Authentication failed." }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: "AuthenticationFailed", message: "Authentication failed.", topology_version: None }), labels: {}, wire_version: None, source: None }) } 2025-08-14T15:39:49.612281547Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 2025-08-14T15:39:49.613656382Z Error: task 49 panicked with message "called `Result::unwrap()` on an `Err` value: failed to initialize database client\n\nCaused by:\n failed to create index | index: enabled | error: Error { kind: Authentication { message: \"SCRAM failure: Authentication failed.\" }, labels: {}, wire_version: None, source: Some(Error { kind: Command(CommandError { code: 18, code_name: \"AuthenticationFailed\", message: \"Authentication failed.\", topology_version: None }), labels: {}, wire_version: None, source: None }) }" ```

GiteaMirror commented 2026-03-22 17:13:21 -05:00

Author

Owner

Copy Link

Copy Source

@martyp187 commented on GitHub (Aug 25, 2025):

I have the same issue and nothing works after the Komodo v1.18.0 version (https://github.com/moghtech/komodo/releases/tag/v1.18.0). Neither FerretDB nor MongoDB work, and I have even removed everything and set up from scratch. I have added labels for Traefik, which was working before and still is, but the Komodo core is full of MongoDB errors, such as 'Authentication Failed'. Starting on http://[::]:9120 core-1 | 2025-06-25T11:54:55.429023Z ERROR core::schedule: failed to get actions for schedule update | failed to get all actions from db: Kind: SCRAM failure: password authentication failed for user 'admin', labels: {": Kind: Command failed: Error code 1 (InternalError): Password authentication failed for user 'admin', labels: {}. Still not fixed.

I have the exact same after trying both DB backend options. Running on a Proxmox VM of Ubuntu using 'host' as CPU type.

@martyp187 commented on GitHub (Aug 25, 2025): > I have the same issue and nothing works after the Komodo v1.18.0 version (https://github.com/moghtech/komodo/releases/tag/v1.18.0). Neither FerretDB nor MongoDB work, and I have even removed everything and set up from scratch. I have added labels for Traefik, which was working before and still is, but the Komodo core is full of MongoDB errors, such as 'Authentication Failed'. Starting on http://[::]:9120 `core-1 | 2025-06-25T11:54:55.429023Z ERROR core::schedule: failed to get actions for schedule update | failed to get all actions from db: Kind: SCRAM failure: password authentication failed for user 'admin', labels: {": Kind: Command failed: Error code 1 (InternalError): Password authentication failed for user 'admin', labels: {}. ` Still not fixed. I have the exact same after trying both DB backend options. Running on a Proxmox VM of Ubuntu using 'host' as CPU type.

GiteaMirror commented 2026-03-22 17:13:21 -05:00

Author

Owner

Copy Link

Copy Source

@mbecker20 commented on GitHub (Aug 26, 2025):

If you deploy the default compose and compose.env on the host, without changing anything, does it work? If so, my guess is your password contains some invalid characters for URL. Try choosing a password only containing letters / numbers. Note that after you start up database for the first time, you can't change the init credentials. You have to drop the data.

I think there actually is an improvement Komodo can make, and this would be url-encoding the credentials for you. I believe the issue is password contains URL invalid character that needs to be url-encoded in order to work. But the simple fix right now is to choose username / password only containing simple characters.

@mbecker20 commented on GitHub (Aug 26, 2025): If you deploy the default compose and compose.env on the host, without changing anything, does it work? If so, my guess is your password contains some invalid characters for URL. Try choosing a password only containing letters / numbers. Note that after you start up database for the first time, you can't change the init credentials. You have to drop the data. I think there actually is an improvement Komodo can make, and this would be url-encoding the credentials for you. I believe the issue is password contains URL invalid character that needs to be url-encoded in order to work. But the simple fix right now is to choose username / password only containing simple characters.

GiteaMirror referenced this issue 2026-03-22 17:46:35 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #1850

GiteaMirror referenced this issue 2026-04-11 10:42:18 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #2976

GiteaMirror referenced this issue 2026-04-13 15:20:14 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #4124

GiteaMirror referenced this issue 2026-04-19 14:11:27 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #4546

GiteaMirror referenced this issue 2026-04-22 00:49:36 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #5716

GiteaMirror referenced this issue 2026-04-24 19:53:35 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #6894

GiteaMirror referenced this issue 2026-04-27 22:11:54 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #8079

GiteaMirror referenced this issue 2026-05-03 05:27:44 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #9273

GiteaMirror referenced this issue 2026-05-08 16:06:45 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #10472

GiteaMirror referenced this issue 2026-05-12 21:51:53 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #11678

GiteaMirror referenced this issue 2026-05-15 06:33:15 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #12885

GiteaMirror referenced this issue 2026-05-17 19:46:42 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #13158

GiteaMirror referenced this issue 2026-05-20 16:03:12 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #14334

GiteaMirror referenced this issue 2026-05-24 16:47:28 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #15564

GiteaMirror referenced this issue 2026-05-29 01:15:43 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #16796

GiteaMirror referenced this issue 2026-06-02 01:58:15 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #18034

GiteaMirror referenced this issue 2026-06-05 03:38:57 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #19281

GiteaMirror referenced this issue 2026-06-07 18:10:26 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #20535

GiteaMirror referenced this issue 2026-06-08 18:23:59 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #21789

GiteaMirror referenced this issue 2026-06-10 20:44:37 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #23047

GiteaMirror referenced this issue 2026-06-13 07:53:55 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #23324

GiteaMirror referenced this issue 2026-06-15 07:13:16 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #24533

GiteaMirror referenced this issue 2026-06-20 14:34:34 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #24810

GiteaMirror referenced this issue 2026-06-21 23:16:42 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #26027

GiteaMirror referenced this issue 2026-07-12 11:11:34 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #27317

GiteaMirror referenced this issue 2026-07-13 14:29:09 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #28613

GiteaMirror referenced this issue 2026-07-14 20:47:23 -05:00

[PR #1171] [CLOSED] fix: improve error message when git is not installed on periphery #28902

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

gh-pages-docs

legacy-v1-frontend

copilot/secure-local-authentication

v0

legacy

v2.3.3

v2.2.0

v2.1.2

v2.1.1

v2.1.0

v2.0.0

v2.0.0-dev-124

v2.0.0-dev-123

v2.0.0-dev-120

v2.0.0-dev-118

v2.0.0-dev-114

v2.0.0-dev-112

v2.0.0-dev-111

v2.0.0-dev-102

v2.0.0-dev-98

v2.0.0-dev-90

v2.0.0-dev-86

v2.0.0-dev-72

v2.0.0-dev-59

v2.0.0-dev-53

v2.0.0-dev-50

v2.0.0-dev-36

v1.19.5

v2.0.0-dev-35

v1.19.4

v1.19.3

v1.19.2

v1.19.1

v1.19.1-dev-14

v1.19.0

v1.19.0-dev-9

v1.18.4

1.18.5-dev-5

v1.18.3

v1.18.2

v1.18.1

v1.18.0

v1.17.5

v1.17.4

v1.17.3

v1.17.4-dev-1

v1.17.2

v1.17.2-dev-1

v1.17.1

v1.17.0

v1.17.0-dev-7

v1.17.0-dev-4

v1.17.0-dev-3

v1.17.0-dev-5

v1.17.0-dev-6

v1.17.0-dev-2

v1.17.0-dev-1

v1.16.12

v1.16.11

v1.16.10

v1.16.9

v1.16.8

v1.16.7

v1.16.6

v1.16.5

v1.16.4

v1.16.3

v1.16.2

v1.16.1

v1.16.0

v1.15.12

v1.15.11

v1.15.10

v1.15.9

v1.15.8

v1.15.7

v1.15.6

v1.15.5

v1.15.4

v1.15.3

v1.15.2

v1.15.1

v1.15.0

v1.14.2

v1.14.1

v1.14.0

v1.14.0-rc1

v1.13.4

v1.13.3

v1.13.2

v1.13.1

v1.13.0

v1.12.0

v1.11.0

v1.10.0

v1.9.0

v1.8.0

v1.7.3

v1.7.0

v1.6.0

v1.5.0

v1.4.0

v1.2.0

v1.1.0

v1.0.0

v0.3.4

v0.3.3

v0.3.2

v0.3.0

v0.2.14

v0.2.13

v0.2.12

v0.2.11

v0.2.10

v0.2.9

v0.2.7

v0.2.6

v0.2.5

v0.2.4

v0.2.1

v0.2.0

v0.1.17

v0.1.16

v0.1.15

v0.1.11

v0.1.10

v0.1.9

v2.3.2

v2.3.1

v2.3.0

Labels

Clear labels

1.19.0

1.19.1

1.19.2

1.19.3

1.19.4

2.0.0

bug

documentation

done

enhancement

help wanted

info

pull-request

Mirrored from GitHub Pull Request

question

security

seen 👀

setup

thinking 🤔

ui

v2

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

GiteaMirror ninjasurge (Kaehlen Rog)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#1171