PostgresSQL issue with MD5 hash

Hi there :wave:

Describe the problem/error/question

I have a problem when using postgres database. I successfully setup the owner user, yet when I try to create additional users I have a problem. From what I understand it’s because my postgres instance (hosted on Azure) doesn’t support to encode using MD5 “could not compute MD5 hash: disabled for FIPS”.

P.S.: the exact same setup with sqlite works fine.

What is the error message (if any)?

I see in the logs:

2025-03-04T14:21:58.916977688Z ResponseError: An error occurred during user creation
2025-03-04T14:21:58.916981788Z     at UserService.inviteUsers (/usr/local/lib/node_modules/n8n/dist/services/user.service.js:163:19)
2025-03-04T14:21:58.916984888Z     at processTicksAndRejections (node:internal/process/task_queues:95:5)
2025-03-04T14:21:58.916987788Z     at InvitationController.inviteUser (/usr/local/lib/node_modules/n8n/dist/controllers/invitation.controller.js:69:48)
2025-03-04T14:21:58.916990688Z     at handler (/usr/local/lib/node_modules/n8n/dist/decorators/controller.registry.js:93:24)
2025-03-04T14:21:58.916993388Z     at /usr/local/lib/node_modules/n8n/dist/response-helper.js:110:26
2025-03-04T14:21:58.916996088Z
2025-03-04T14:21:58.916998488Z could not compute MD5 hash: disabled for FIPS/home/LogFiles/2025_03_04_lw1mdlwk0002XW_default_scm_docker.log  (https://blockloads-sectionslab-auto-qa.scm.azurewebsites.net/api/vfs/LogFiles/2025_03_04_lw1mdlwk0002XW_default_scm_docker.log)

Information on your n8n setup

  • n8n version: 1.81.4
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: Azure

hello @Xmaster6y

That’s because of the FIPS requirements. So the only options is to avoid using the Azure postgres.

1 Like

I went back to the sqlite default. But do you know why is it necessary? I never had issue for other apps.

I may assume that it’s the n8n’s implementation which has been created a long time ago, when the md5 was still good solution

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.