Skip to content
cccskills
FreePublished on GitHub

gorse-clickhouse-cloud-incompatible

Fix Gorse recommendation engine failing to connect to ClickHouse Cloud with EOF errors. Use when: (1) Gorse pods crash with "failed to connect data database" and "EOF" error, (2) Using ClickHouse Cloud (*.clickhouse.cloud) as Gorse data store, (3) TLS connection works (verified with openssl) but Gorse still fails, (4) Tried secure=true, different ports (8443, 9440), timeout params without success. The Gorse ClickHouse driver is incompatible with ClickHouse Cloud's native protocol.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile
Works withPostgreSQLMySQL
See how to install

Files included (1)

  • SKILL.md3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Gorse + ClickHouse Cloud Incompatibility

Problem

Gorse recommendation engine fails to connect to ClickHouse Cloud with EOF errors during protocol negotiation, even though TLS handshake succeeds.

Context / Trigger Conditions

  • Gorse master/server pods show CrashLoopBackOff
  • Logs show: failed to connect data database: EOF or transport failed to send a request to ClickHouse: EOF
  • Using ClickHouse Cloud (*.clickhouse.cloud) as the GORSE_DATA_STORE
  • TLS connection works when tested with openssl s_client
  • Tried various connection parameters without success

Root Cause

Despite the clickhouse:// URL scheme suggesting native protocol, Gorse actually uses the HTTP interface on port 8123 (not the native protocol on port 9000/9440). ClickHouse Cloud's HTTP interface on port 8443 has compatibility issues with Gorse's driver.

Key facts:

  • Gorse uses ClickHouse HTTP interface (port 8123), NOT native protocol (port 9000)
  • ClickHouse Cloud port 8443: HTTP/HTTPS protocol
  • ClickHouse Cloud port 9440: Native protocol with TLS
  • Gorse only accepts: clickhouse://, mysql://, postgres://, mongodb://
  • Gorse does NOT support https:// scheme (returns "unsupported data storage backend")
  • Redis is only for cache store, NOT data store
  • If you use port 9000 with in-cluster ClickHouse, you'll get: "Port 9000 is for clickhouse-client program. You must use port 8123 for HTTP."

Solution Options

Option 1: Use In-Cluster ClickHouse (Recommended)

Deploy ClickHouse Operator with an in-cluster instance for Gorse:

# Standard in-cluster connection works
GORSE_DATA_STORE: "clickhouse://user:password@clickhouse-host:8123/gorse"

Option 2: Use Different Database

Gorse supports MySQL and PostgreSQL as data stores:

GORSE_DATA_STORE: "mysql://user:password@host:3306/gorse"
# or
GORSE_DATA_STORE: "postgres://user:password@host:5432/gorse"

Option 3: Deploy ClickHouse Proxy

Set up a proxy (like chproxy) that translates between protocols.

Option 4: Fallback to Popular Videos

Keep Gorse disabled and let the API fallback to popularity-based recommendations:

{"videos": [...], "source": "popular"}

Verification

After choosing a solution, check Gorse master logs:

kubectl logs -l app=gorse-master -n gorse --tail=20

Should show successful connection instead of EOF errors.

Notes

  • The TLS layer works fine - the issue is at the ClickHouse protocol level
  • This may be fixed in future versions of the clickhouse-go driver
  • In-cluster ClickHouse doesn't have this issue because it uses plain connection on port 8123

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

argocd-externalsecret-namespace-permission

Free

Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

art-direct

Free

Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

async-await-null-race-condition

Free

Fix "Null check operator used on a null value" errors when an object is set to null during an async await. Use when: (1) Object reference is nullified while awaiting, (2) Code accesses object with ! after await returns, (3) Cancel/dispose operations run concurrently with async operations on same object. Solution: capture local reference before await.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

aws-v4-signing-custom-headers-gcs

Free

Add custom metadata headers (x-amz-meta-*) to AWS v4 signed requests for GCS S3-compatible API. Use when: (1) Adding custom metadata to GCS uploads via S3 API, (2) Getting signature mismatch errors after adding new headers, (3) x-amz-meta-* headers being ignored or causing 403 errors. Custom headers MUST be included in canonical headers and signed headers list.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

bash-herestring-newline-secrets

Free

Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings. Use when: (1) Password authentication fails with correct password, (2) Secret created with `<<< "value"` syntax, (3) Error like "password authentication failed" or "invalid token" despite correct value. Bash here-strings (`<<<`) add a trailing newline that corrupts secrets.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

blossom-content-addressed-url-filtering

Free

Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp). Use when: (1) Media moderation, transcoding, or analysis silently skips files from Blossom or content-addressed storage servers, (2) URL extraction from Nostr event tags (imeta, r tags) drops URLs without recognized extensions, (3) CDN fallback URLs append .mp4 but the actual server uses extensionless content-addressed paths like /{sha256}. Common in Nostr video events (kind 34236) where different clients use different URL formats.

The English summary is being prepared. Showing the original description.

divinevideo/divine-mobile265Updated Oct 22, 2026

See all skills by divinevideo

Report a problem with this skill