René's URL Explorer Experiment


Title: bug: v4.4.6 self-hosted webapp fails to start due to ClickHouse URL `secure` param mismatch (goose entrypoint + Runs Replication client) · Issue #3674 · triggerdotdev/trigger.dev · GitHub

Open Graph Title: bug: v4.4.6 self-hosted webapp fails to start due to ClickHouse URL `secure` param mismatch (goose entrypoint + Runs Replication client) · Issue #3674 · triggerdotdev/trigger.dev

X Title: bug: v4.4.6 self-hosted webapp fails to start due to ClickHouse URL `secure` param mismatch (goose entrypoint + Runs Replication client) · Issue #3674 · triggerdotdev/trigger.dev

Description: Provide environment information Provide environment information Trigger.dev version: v4.4.6 (self-hosted Docker, ghcr.io/triggerdotdev/trigger.dev:v4.4.6) Setup: standard hosting/docker compose, multi-file (webapp/docker-compose.yml + wo...

Open Graph Description: Provide environment information Provide environment information Trigger.dev version: v4.4.6 (self-hosted Docker, ghcr.io/triggerdotdev/trigger.dev:v4.4.6) Setup: standard hosting/docker compose, mu...

X Description: Provide environment information Provide environment information Trigger.dev version: v4.4.6 (self-hosted Docker, ghcr.io/triggerdotdev/trigger.dev:v4.4.6) Setup: standard hosting/docker compose, mu...

Opengraph URL: https://github.com/triggerdotdev/trigger.dev/issues/3674

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"bug:  v4.4.6 self-hosted webapp fails to start due to ClickHouse URL `secure` param mismatch (goose entrypoint + Runs Replication client)","articleBody":"### Provide environment information\n\n### Provide environment information\n\n- **Trigger.dev version:** `v4.4.6` (self-hosted Docker, `ghcr.io/triggerdotdev/trigger.dev:v4.4.6`)\n- **Setup:** standard `hosting/docker` compose, multi-file (`webapp/docker-compose.yml` + `worker/docker-compose.yml`)\n- **ClickHouse:** `bitnamilegacy/clickhouse:latest`, HTTP only (no TLS), port 8123, local container\n- **Host:** Linux amd64\n- **Previous working version:** `v4.4.5` (same `.env`, started healthy)\n\n### Describe the bug\n\nAfter updating the image tag from `v4.4.5` to `v4.4.6` and running `docker compose pull && up -d`, the `webapp` container enters a restart loop. Two separate ClickHouse-URL handling issues block startup, related to but not fully covered by #3184 / #3204.\n\n**Issue 1 — `entrypoint.sh` appends `?secure=true` unconditionally, goose now rejects it**\n\n`docker/scripts/entrypoint.sh` constructs `GOOSE_DBSTRING` from `CLICKHOUSE_URL` and adds `?secure=true` if `secure=` isn't already in the URL — regardless of scheme. When the URL uses `http://` (no TLS), the goose ClickHouse driver in v4.4.6 fails DSN parsing:\n\n```\n+ export GOOSE_DBSTRING=http://default:***@clickhouse:8123?secure=true\n+ /usr/local/bin/goose up\n2026/05/20 10:13:56 goose run: clickhouse [dsn parse]: http with TLS specify; clickhouse [dsn parse]: http with TLS specify\n```\n\nThis appears to be a behavior change in the goose ClickHouse driver between v4.4.5 and v4.4.6 — the same DSN was tolerated by the older driver. `entrypoint.sh` exits non-zero, container restarts forever.\n\n**Issue 2 — `RUN_REPLICATION_CLICKHOUSE_URL` is NOT stripped before being passed to `@clickhouse/client`**\n\n#3204 added stripping of the `secure` query param for `QUERY_CLICKHOUSE_URL`, but `RUN_REPLICATION_CLICKHOUSE_URL` follows the same path through `@clickhouse/client@1.12.1` and doesn't get the same treatment. Workarounding Issue 1 by adding `?secure=false` to `RUN_REPLICATION_CLICKHOUSE_URL` (because the main `CLICKHOUSE_URL` workaround value is reused as the replication URL in some setups) triggers:\n\n```\n🗃️ Runs replication service enabled\n{\"url\":\"http://default:redacted@clickhouse:8123/?secure=false\", ...}\nError: Unknown URL parameters: secure\n    at loadConfigOptionsFromURL (.../config.js:267:19)\n    at prepareConfigWithURL (.../config.js:42:34)\n    at new ClickHouseClient (.../client.js:59:65)\n    at createClient (.../@clickhouse+client@1.12.1/.../client.js:15:12)\n    at new ClickhouseClient (.../webapp/build/index.js:49830:243)\n    at new ClickHouse (.../webapp/build/index.js:63805:21)\n    at initializeRunsReplicationInstance (.../webapp/build/index.js:190055:20)\n```\n\n### To reproduce\n\n1. Self-host `v4.4.5` with HTTP ClickHouse (no TLS), `CLICKHOUSE_URL=http://...@clickhouse:8123`, healthy.\n2. Bump `TRIGGER_IMAGE_TAG` to `v4.4.6`, `docker compose pull && up -d`.\n3. Observe `webapp` in restart loop, goose error in logs (Issue 1).\n4. Append `?secure=false` to `CLICKHOUSE_URL` and `RUN_REPLICATION_CLICKHOUSE_URL` — goose now passes, but webapp now crashes on Runs Replication init (Issue 2).\n\n### Workaround (currently running in production)\n\nAsymmetric values:\n\n```env\nCLICKHOUSE_URL=http://default:***@clickhouse:8123?secure=false\nRUN_REPLICATION_CLICKHOUSE_URL=http://default:***@clickhouse:8123\n```\n\n- `CLICKHOUSE_URL` ends with `?secure=false` so `entrypoint.sh`'s `grep -q secure=` matches and skips appending `?secure=true`. goose accepts `secure=false` + `http://` (no conflict). Webapp's own `CLICKHOUSE_URL` consumption already strips `secure` via #3204, so the param is harmless there.\n- `RUN_REPLICATION_CLICKHOUSE_URL` stays clean — it goes to `@clickhouse/client` without stripping.\n\nThis works but is fragile and undiscoverable.\n\n### Suggested fix\n\nTwo independent things to address:\n\n1. **`docker/scripts/entrypoint.sh`** — only append `?secure=true` when the URL scheme is `https://`. Or, simpler: strip the param entirely before calling `goose` and translate it to the scheme (`https://` → `secure=true`, `http://` → no flag). Conflating TLS choice with a query param when the scheme already encodes it is the root issue.\n\n2. **`initializeRunsReplicationInstance`** — apply the same `secure` strip that `QUERY_CLICKHOUSE_URL` got in #3204 to `RUN_REPLICATION_CLICKHOUSE_URL` (and any other URL passed to `@clickhouse/client`). Centralizing this in a helper used by all client constructors would prevent regressions.\n\n\n\n### Describe the bug\n\n### Provide environment information\n\n- **Trigger.dev version:** `v4.4.6` (self-hosted Docker, `ghcr.io/triggerdotdev/trigger.dev:v4.4.6`)\n- **Setup:** standard `hosting/docker` compose, multi-file (`webapp/docker-compose.yml` + `worker/docker-compose.yml`)\n- **ClickHouse:** `bitnamilegacy/clickhouse:latest`, HTTP only (no TLS), port 8123, local container\n- **Host:** Linux amd64\n- **Previous working version:** `v4.4.5` (same `.env`, started healthy)\n\n### Describe the bug\n\nAfter updating the image tag from `v4.4.5` to `v4.4.6` and running `docker compose pull && up -d`, the `webapp` container enters a restart loop. Two separate ClickHouse-URL handling issues block startup, related to but not fully covered by #3184 / #3204.\n\n**Issue 1 — `entrypoint.sh` appends `?secure=true` unconditionally, goose now rejects it**\n\n`docker/scripts/entrypoint.sh` constructs `GOOSE_DBSTRING` from `CLICKHOUSE_URL` and adds `?secure=true` if `secure=` isn't already in the URL — regardless of scheme. When the URL uses `http://` (no TLS), the goose ClickHouse driver in v4.4.6 fails DSN parsing:\n\n```\n+ export GOOSE_DBSTRING=http://default:***@clickhouse:8123?secure=true\n+ /usr/local/bin/goose up\n2026/05/20 10:13:56 goose run: clickhouse [dsn parse]: http with TLS specify; clickhouse [dsn parse]: http with TLS specify\n```\n\nThis appears to be a behavior change in the goose ClickHouse driver between v4.4.5 and v4.4.6 — the same DSN was tolerated by the older driver. `entrypoint.sh` exits non-zero, container restarts forever.\n\n**Issue 2 — `RUN_REPLICATION_CLICKHOUSE_URL` is NOT stripped before being passed to `@clickhouse/client`**\n\n#3204 added stripping of the `secure` query param for `QUERY_CLICKHOUSE_URL`, but `RUN_REPLICATION_CLICKHOUSE_URL` follows the same path through `@clickhouse/client@1.12.1` and doesn't get the same treatment. Workarounding Issue 1 by adding `?secure=false` to `RUN_REPLICATION_CLICKHOUSE_URL` (because the main `CLICKHOUSE_URL` workaround value is reused as the replication URL in some setups) triggers:\n\n```\n🗃️ Runs replication service enabled\n{\"url\":\"http://default:redacted@clickhouse:8123/?secure=false\", ...}\nError: Unknown URL parameters: secure\n    at loadConfigOptionsFromURL (.../config.js:267:19)\n    at prepareConfigWithURL (.../config.js:42:34)\n    at new ClickHouseClient (.../client.js:59:65)\n    at createClient (.../@clickhouse+client@1.12.1/.../client.js:15:12)\n    at new ClickhouseClient (.../webapp/build/index.js:49830:243)\n    at new ClickHouse (.../webapp/build/index.js:63805:21)\n    at initializeRunsReplicationInstance (.../webapp/build/index.js:190055:20)\n```\n\n### To reproduce\n\n1. Self-host `v4.4.5` with HTTP ClickHouse (no TLS), `CLICKHOUSE_URL=http://...@clickhouse:8123`, healthy.\n2. Bump `TRIGGER_IMAGE_TAG` to `v4.4.6`, `docker compose pull && up -d`.\n3. Observe `webapp` in restart loop, goose error in logs (Issue 1).\n4. Append `?secure=false` to `CLICKHOUSE_URL` and `RUN_REPLICATION_CLICKHOUSE_URL` — goose now passes, but webapp now crashes on Runs Replication init (Issue 2).\n\n### Workaround (currently running in production)\n\nAsymmetric values:\n\n```env\nCLICKHOUSE_URL=http://default:***@clickhouse:8123?secure=false\nRUN_REPLICATION_CLICKHOUSE_URL=http://default:***@clickhouse:8123\n```\n\n- `CLICKHOUSE_URL` ends with `?secure=false` so `entrypoint.sh`'s `grep -q secure=` matches and skips appending `?secure=true`. goose accepts `secure=false` + `http://` (no conflict). Webapp's own `CLICKHOUSE_URL` consumption already strips `secure` via #3204, so the param is harmless there.\n- `RUN_REPLICATION_CLICKHOUSE_URL` stays clean — it goes to `@clickhouse/client` without stripping.\n\nThis works but is fragile and undiscoverable.\n\n### Suggested fix\n\nTwo independent things to address:\n\n1. **`docker/scripts/entrypoint.sh`** — only append `?secure=true` when the URL scheme is `https://`. Or, simpler: strip the param entirely before calling `goose` and translate it to the scheme (`https://` → `secure=true`, `http://` → no flag). Conflating TLS choice with a query param when the scheme already encodes it is the root issue.\n\n2. **`initializeRunsReplicationInstance`** — apply the same `secure` strip that `QUERY_CLICKHOUSE_URL` got in #3204 to `RUN_REPLICATION_CLICKHOUSE_URL` (and any other URL passed to `@clickhouse/client`). Centralizing this in a helper used by all client constructors would prevent regressions.\n\n\n\n### Reproduction repo\n\n?\n\n### To reproduce\n\n### Provide environment information\n\n- **Trigger.dev version:** `v4.4.6` (self-hosted Docker, `ghcr.io/triggerdotdev/trigger.dev:v4.4.6`)\n- **Setup:** standard `hosting/docker` compose, multi-file (`webapp/docker-compose.yml` + `worker/docker-compose.yml`)\n- **ClickHouse:** `bitnamilegacy/clickhouse:latest`, HTTP only (no TLS), port 8123, local container\n- **Host:** Linux amd64\n- **Previous working version:** `v4.4.5` (same `.env`, started healthy)\n\n### Describe the bug\n\nAfter updating the image tag from `v4.4.5` to `v4.4.6` and running `docker compose pull && up -d`, the `webapp` container enters a restart loop. Two separate ClickHouse-URL handling issues block startup, related to but not fully covered by #3184 / #3204.\n\n**Issue 1 — `entrypoint.sh` appends `?secure=true` unconditionally, goose now rejects it**\n\n`docker/scripts/entrypoint.sh` constructs `GOOSE_DBSTRING` from `CLICKHOUSE_URL` and adds `?secure=true` if `secure=` isn't already in the URL — regardless of scheme. When the URL uses `http://` (no TLS), the goose ClickHouse driver in v4.4.6 fails DSN parsing:\n\n```\n+ export GOOSE_DBSTRING=http://default:***@clickhouse:8123?secure=true\n+ /usr/local/bin/goose up\n2026/05/20 10:13:56 goose run: clickhouse [dsn parse]: http with TLS specify; clickhouse [dsn parse]: http with TLS specify\n```\n\nThis appears to be a behavior change in the goose ClickHouse driver between v4.4.5 and v4.4.6 — the same DSN was tolerated by the older driver. `entrypoint.sh` exits non-zero, container restarts forever.\n\n**Issue 2 — `RUN_REPLICATION_CLICKHOUSE_URL` is NOT stripped before being passed to `@clickhouse/client`**\n\n#3204 added stripping of the `secure` query param for `QUERY_CLICKHOUSE_URL`, but `RUN_REPLICATION_CLICKHOUSE_URL` follows the same path through `@clickhouse/client@1.12.1` and doesn't get the same treatment. Workarounding Issue 1 by adding `?secure=false` to `RUN_REPLICATION_CLICKHOUSE_URL` (because the main `CLICKHOUSE_URL` workaround value is reused as the replication URL in some setups) triggers:\n\n```\n🗃️ Runs replication service enabled\n{\"url\":\"http://default:redacted@clickhouse:8123/?secure=false\", ...}\nError: Unknown URL parameters: secure\n    at loadConfigOptionsFromURL (.../config.js:267:19)\n    at prepareConfigWithURL (.../config.js:42:34)\n    at new ClickHouseClient (.../client.js:59:65)\n    at createClient (.../@clickhouse+client@1.12.1/.../client.js:15:12)\n    at new ClickhouseClient (.../webapp/build/index.js:49830:243)\n    at new ClickHouse (.../webapp/build/index.js:63805:21)\n    at initializeRunsReplicationInstance (.../webapp/build/index.js:190055:20)\n```\n\n### To reproduce\n\n1. Self-host `v4.4.5` with HTTP ClickHouse (no TLS), `CLICKHOUSE_URL=http://...@clickhouse:8123`, healthy.\n2. Bump `TRIGGER_IMAGE_TAG` to `v4.4.6`, `docker compose pull && up -d`.\n3. Observe `webapp` in restart loop, goose error in logs (Issue 1).\n4. Append `?secure=false` to `CLICKHOUSE_URL` and `RUN_REPLICATION_CLICKHOUSE_URL` — goose now passes, but webapp now crashes on Runs Replication init (Issue 2).\n\n### Workaround (currently running in production)\n\nAsymmetric values:\n\n```env\nCLICKHOUSE_URL=http://default:***@clickhouse:8123?secure=false\nRUN_REPLICATION_CLICKHOUSE_URL=http://default:***@clickhouse:8123\n```\n\n- `CLICKHOUSE_URL` ends with `?secure=false` so `entrypoint.sh`'s `grep -q secure=` matches and skips appending `?secure=true`. goose accepts `secure=false` + `http://` (no conflict). Webapp's own `CLICKHOUSE_URL` consumption already strips `secure` via #3204, so the param is harmless there.\n- `RUN_REPLICATION_CLICKHOUSE_URL` stays clean — it goes to `@clickhouse/client` without stripping.\n\nThis works but is fragile and undiscoverable.\n\n### Suggested fix\n\nTwo independent things to address:\n\n1. **`docker/scripts/entrypoint.sh`** — only append `?secure=true` when the URL scheme is `https://`. Or, simpler: strip the param entirely before calling `goose` and translate it to the scheme (`https://` → `secure=true`, `http://` → no flag). Conflating TLS choice with a query param when the scheme already encodes it is the root issue.\n\n2. **`initializeRunsReplicationInstance`** — apply the same `secure` strip that `QUERY_CLICKHOUSE_URL` got in #3204 to `RUN_REPLICATION_CLICKHOUSE_URL` (and any other URL passed to `@clickhouse/client`). Centralizing this in a helper used by all client constructors would prevent regressions.\n\n\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/Valentyn-Kubrak","@type":"Person","name":"Valentyn-Kubrak"},"datePublished":"2026-05-20T10:33:00Z","url":"https://github.com/triggerdotdev/trigger.dev/issues/3674"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:c346d51c-ecf8-b43c-f663-b03391316735
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-id8D6E:1FE80C:2FE6AF7:43F5243:6AFAE9E0
html-safe-noncee1a94fb1c52b8322e18d50f8de81a3efa089b8f29d8f942d95317cf80aa462bf
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4RDZFOjFGRTgwQzoyRkU2QUY3OjQzRjUyNDM6NkFGQUU5RTAiLCJ2aXNpdG9yX2lkIjoiODQ4NDE2MjE4MjM4NzU1NTIiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmac15e2fc5fffba170b1511c7864a6ef1ada0ea39e7ec762e7f92d62efc8c34e668
hovercard-subject-tagissue:4485523456
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/triggerdotdev/trigger.dev/3674/issue_layout
twitter:imagehttps://opengraph.githubassets.com/2f55497318810d2bcff08ab92a2834cc6da7d44f6aa65b29593d293ff837f9ae/triggerdotdev/trigger.dev/issues/3674
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/2f55497318810d2bcff08ab92a2834cc6da7d44f6aa65b29593d293ff837f9ae/triggerdotdev/trigger.dev/issues/3674
og:image:altProvide environment information Provide environment information Trigger.dev version: v4.4.6 (self-hosted Docker, ghcr.io/triggerdotdev/trigger.dev:v4.4.6) Setup: standard hosting/docker compose, mu...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameValentyn-Kubrak
hostnamegithub.com
expected-hostnamegithub.com
None0178036d8230524a18422872393ab7e708443ae4c2047f758560a2db870c1913
turbo-cache-controlno-preview
go-importgithub.com/triggerdotdev/trigger.dev git https://github.com/triggerdotdev/trigger.dev.git
octolytics-dimension-user_id95297378
octolytics-dimension-user_logintriggerdotdev
octolytics-dimension-repository_id572570113
octolytics-dimension-repository_nwotriggerdotdev/trigger.dev
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id572570113
octolytics-dimension-repository_network_root_nwotriggerdotdev/trigger.dev
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release12fff95459b24b0f882a66698ee6a36a5934d247
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/triggerdotdev/trigger.dev/issues/3674#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Ftriggerdotdev%2Ftrigger.dev%2Fissues%2F3674
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Ftriggerdotdev%2Ftrigger.dev%2Fissues%2F3674
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=triggerdotdev%2Ftrigger.dev
Reloadhttps://github.com/triggerdotdev/trigger.dev/issues/3674
Reloadhttps://github.com/triggerdotdev/trigger.dev/issues/3674
Reloadhttps://github.com/triggerdotdev/trigger.dev/issues/3674
triggerdotdevhttps://github.com/triggerdotdev
trigger.devhttps://github.com/triggerdotdev/trigger.dev
Codehttps://github.com/triggerdotdev/trigger.dev
Issues203 (203)https://github.com/triggerdotdev/trigger.dev/issues
Pull requests67 (67)https://github.com/triggerdotdev/trigger.dev/pulls
Discussionshttps://github.com/triggerdotdev/trigger.dev/discussions
Actionshttps://github.com/triggerdotdev/trigger.dev/actions
Projectshttps://github.com/triggerdotdev/trigger.dev/projects
Security and quality39 (39)https://github.com/triggerdotdev/trigger.dev/security
Insightshttps://github.com/triggerdotdev/trigger.dev/pulse
https://github.com/triggerdotdev/trigger.dev
New issuehttps://github.com/login?return_to=https://github.com/triggerdotdev/trigger.dev/issues/3674
New issuehttps://github.com/login?return_to=https://github.com/triggerdotdev/trigger.dev/issues/3674
bug: v4.4.6 self-hosted webapp fails to start due to ClickHouse URL secure param mismatch (goose entrypoint + Runs Replication client)https://github.com/triggerdotdev/trigger.dev/issues/3674#top
https://github.com/Valentyn-Kubrak
Valentyn-Kubrakhttps://github.com/Valentyn-Kubrak
on May 20, 2026https://github.com/triggerdotdev/trigger.dev/issues/3674#issue-4485523456
#3184https://github.com/triggerdotdev/trigger.dev/issues/3184
#3204https://github.com/triggerdotdev/trigger.dev/pull/3204
#3204https://github.com/triggerdotdev/trigger.dev/pull/3204
fix(webapp): strip secure param from query ClickHouse URL #3204https://github.com/triggerdotdev/trigger.dev/pull/3204
fix(webapp): strip secure param from query ClickHouse URL #3204https://github.com/triggerdotdev/trigger.dev/pull/3204
#3184https://github.com/triggerdotdev/trigger.dev/issues/3184
#3204https://github.com/triggerdotdev/trigger.dev/pull/3204
#3204https://github.com/triggerdotdev/trigger.dev/pull/3204
fix(webapp): strip secure param from query ClickHouse URL #3204https://github.com/triggerdotdev/trigger.dev/pull/3204
fix(webapp): strip secure param from query ClickHouse URL #3204https://github.com/triggerdotdev/trigger.dev/pull/3204
#3184https://github.com/triggerdotdev/trigger.dev/issues/3184
#3204https://github.com/triggerdotdev/trigger.dev/pull/3204
#3204https://github.com/triggerdotdev/trigger.dev/pull/3204
fix(webapp): strip secure param from query ClickHouse URL #3204https://github.com/triggerdotdev/trigger.dev/pull/3204
fix(webapp): strip secure param from query ClickHouse URL #3204https://github.com/triggerdotdev/trigger.dev/pull/3204
https://github.com/Suryansh1987
Suryansh1987https://github.com/Suryansh1987
on May 20, 2026https://github.com/triggerdotdev/trigger.dev/issues/3674#issuecomment-4500504524
https://github.com/samadrehman
samadrehmanhttps://github.com/samadrehman
on May 20, 2026https://github.com/triggerdotdev/trigger.dev/issues/3674#issuecomment-4502068297
https://github.com/samadrehman
samadrehmanhttps://github.com/samadrehman
on May 20, 2026https://github.com/triggerdotdev/trigger.dev/issues/3674#issuecomment-4502261477
PR #3681https://github.com/triggerdotdev/trigger.dev/pull/3681
darshitp091https://github.com/darshitp091
on May 23, 2026https://github.com/triggerdotdev/trigger.dev/issues/3674#event-25880885634
fix: clarify ClickHouse DSN normalizationhttps://github.com/darshitp091/trigger.dev-fixed/commit/476f08157c4166f6b34f47d1e4b7b756b18e6bd0
476f081https://github.com/darshitp091/trigger.dev-fixed/commit/476f08157c4166f6b34f47d1e4b7b756b18e6bd0
Sign up for freehttps://github.com/signup?return_to=https://github.com/triggerdotdev/trigger.dev/issues/3674
Sign in to commenthttps://github.com/login?return_to=https://github.com/triggerdotdev/trigger.dev/issues/3674
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.