Skip to content

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.

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.

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.

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.