{"version":"2.1.290","anchor":"gateway-gives-a-clear-error-for-an-invalid-storepostgres-ur","canonical_anchor":"gateway-gives-a-clear-error-for-an-invalid-storepostgres-ur","heading":"Clear error for unsupported store.postgres_url values in the gateway","tier":"use","area":"Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/gateway-gives-a-clear-error-for-an-invalid-storepostgres-ur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clear error for unsupported `store.postgres_url` values in the gateway\n\nThe gateway now explains why a `store.postgres_url` with several hosts or a special-character password is rejected\n\n**What**\n\nA `store.postgres_url` setting for the gateway now fails with an explanatory error when it contains either of these:\n\n- a comma-separated list of hosts, which is not supported\n\n- a password with special characters\n\n**Why**\n\nPeople running the gateway get an error that says what to fix.\n\n- Area: Gateway\n- Names: `store.postgres_url`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}