Skip to content
GeoJibe

Connection problems

PostGIS connection failed

What you see: Test or Run fails with authentication, connection, permission, SSL, or “PostGIS” errors.

What to check:

  • Host, port, database, username, password
  • SSL mode (try prefer first)
  • The database exists and has the PostGIS extension
  • Schema/table names are valid identifiers
  • Create vs Replace vs Append matches whether the table already exists

GeoJibe does not create the database for you.

SQL Server connection failed

What you see: Test or Run fails with login failed, connection timeout, TLS, permission, or “SQL Server” errors.

What to check:

  • Host, port (usually 1433), database, username, password
  • The database exists and the login can see the schema and table
  • Schema/table names are valid identifiers (dbo.Parcels is typical)
  • Create vs Replace vs Append matches whether the table already exists
  • Encryption is Required by default. A TLS certificate error is different from a login, host/port, or missing-database error
  • For a self-signed server certificate, keep encryption required and enable Trust server certificate. Do not turn encryption off to work around certificate errors

GeoJibe does not create the database for you. Windows Integrated Authentication is not used.

MySQL / MariaDB connection failed

What you see: Test or Run fails with authentication, connection, permission, or “MySQL” errors.

What to check:

  • Host, port (usually 3306), database, username, password
  • The database exists and the login can see the table
  • Table names are valid identifiers
  • Create vs Replace vs Append matches whether the table already exists
  • The GDAL runtime includes the MySQL driver

GeoJibe does not create the database for you. This is a table import/export, not a full database migration.

Oracle Spatial connection failed

What you see: Test or Run fails with authentication, connection, TNS, permission, or “Oracle” / “OCI” errors.

What to check:

  • Host, port (usually 1521), service name, username, password
  • The service name matches the listener
  • The login can see the schema and table
  • Schema/table names are valid identifiers
  • Create vs Replace vs Append matches whether the table already exists
  • The GDAL runtime includes the OCI driver

GeoJibe does not create the database for you. Passwords must not contain / or @. This is vector table import/export only — GeoRaster is not supported.

Google BigQuery connection failed

What you see: Test or Run fails with authentication, permission, not found, or “BigQuery” errors.

What to check:

  • The project ID matches the Google Cloud project
  • The uploaded file is a service-account JSON key (type is service_account)
  • The service account has bigquery.jobUser plus bigquery.dataViewer (import) or bigquery.dataEditor (write)
  • Dataset and table names are valid identifiers (letters, digits, underscore)
  • Create vs Replace vs Append matches whether the table already exists
  • Writes use EPSG:4326. Other CRSs must be reprojected in Transform first
  • Nested RECORD/REPEATED fields are not imported in this version

GeoJibe does not create the dataset for you. Interactive Google OAuth is not used. Private keys never appear in Job JSON, API views, or logs.

S3 Test or Import failed

What you see: Bucket not found, auth failed, permission denied, or unreachable endpoint.

What to check: Access key and secret, bucket, region, and endpoint. Leave Endpoint empty for AWS. Keep Use path-style addressing for MinIO. Custom private endpoints can be blocked.

SFTP failed

What you see: Auth failed, unreachable host, directory not found, or permission denied.

What to check: Password vs private key mode. The remote parent directory must already exist. GeoJibe does not verify SSH host keys — confirm you trust the host.

My URL won't import

See Common problems. Only public http/https is accepted. Local and private hosts are blocked.

My HTTP/API request won't import

See Common problems. HTTP/API uses the same network policy as URL. Tokens are never shown after save.

FeatureServer access denied

What you see: Connect or Import fails with access denied.

What to check: The service must be public. GeoJibe does not collect an ArcGIS token in the form. Try the layer URL in a browser without signing in.

GeoServer rejected the publication

What you see:

  • Workspace missing from the list
  • Store "…" already exists in workspace "…"
  • Layer "…" already exists
  • Not vector / no geometry / missing CRS

What to check: Create the workspace in GeoServer first. Use a new store and layer name. Publish one vector layer. Test should return Connected to GeoServer.

GeoNode upload failed

What you see: Unsupported GeoNode, auth failed, A GeoNode resource named "…" already exists, or processing timeout.

What to check: GeoNode 5.x or 4.2+ with API v2 upload. Token vs username/password matches how you saved the Destination. Pick a new resource name. Wait for GeoNode processing; it is not instant.

Webhook Destination failed

What you see: DNS, connection refused, TLS, timeout, HTTP 401/403/404/429/5xx, or the webhook rejected the request.

What to check: Endpoint URL (no query string), POST vs PUT, Basic/Bearer/headers, and whether the remote expects multipart or a raw body. Send test request posts a small GeoJibe JSON payload, not your dataset. Cloud metadata and link-local addresses are always blocked.

Job outcome JSON uses a notification webhook, not this Destination. See Job Notifications.

Saved connection Test vs Run

Test only checks that GeoJibe can sign in and reach the service. It does not create tables or publish layers. A green Test can still fail on Run if the table name, key, or layer is wrong.