> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/knowledge-base/LmMmmLqSszWn8sdGe7gH/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/knowledge-base/LmMmmLqSszWn8sdGe7gH/self-managed-articles/ihc-related/special-characters-in-passwords-breaks-prisma-migrations.md).

# Special characters in passwords breaks Prisma migrations

If using a password that contains special characters it might break Primsa migrations and cause the web pods to fail. This can be resolved with special formatting and SQL.

For every non alpha-numeric character we replaced it with the value outlined in: <https://stackoverflow.com/questions/63684133/prisma-cant-connect-to-postgresql>

1. Change the password in your database, and secret if used in your deployment.
   1. Select a new password to use.
   2. Exec into db container, log into psql as postgres
      1. `kubectl exec -n <NAMESPACE> -it <DATABASE-POD-NAME> -- bash`
      2. `psql -u postgres`
      3. `ALTER USER postgres WITH PASSWORD 'newpassword';`
   3. Exit the Postgres container and pod
2. If a kubernetes secret is being used you must edit the secret to reflect the password changed in the steps above:
   1. Change the `databaseSuperuserPassword` in the `immuta-secrets` kubernetes Secret to reflect the new password
      1. Postgres passwords must be base64 encrpyted prior to saving or altering outside of SQL:
         1. `echo "newpassword" | base64`
      2. Save the secret


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.immuta.com/knowledge-base/LmMmmLqSszWn8sdGe7gH/self-managed-articles/ihc-related/special-characters-in-passwords-breaks-prisma-migrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.