4 months ago
Hi, I’m not sure if this is related to the general issues, but when trying to publish an n8n workflow, I’m now getting an error.
Attachments
Pinned Solution
4 months ago
I've fixed it.
Basically each node that carries credentials was reset, you have to reconfigure the credentials for each node that requires it.
8 Replies
4 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 4 months ago
4 months ago
Hi! I’m experiencing the same behavior on my side.
In Railway everything looks healthy and the service appears to be running correctly, but the self-hosted n8n instance returns a 502 error when trying to publish workflows.
Let me know if you need any logs or additional details to help debug this.
Attachments
4 months ago
Restart all services in the flow and it will go back to state before outage.
4 months ago
I try restarting all the services and doing redeploy and it doesn't work for me.
What you don’t know how to contact the support
4 months ago
same for me
norbertosk
I try restarting all the services and doing redeploy and it doesn't work for me. What you don’t know how to contact the support
4 months ago
Do you have persistent data enabled in Docker? If you don't, when something goes down, it changes the encryption key, so unless you have that encription key saved anywhere, you'll have to start again
4 months ago
check if you have the ~/.n8n/ ~/.n8n/config folders, if not it means it didn't persist and you lost everything...
4 months ago
the solution is to delete those credentials and create new ones
4 months ago
I've fixed it.
Basically each node that carries credentials was reset, you have to reconfigure the credentials for each node that requires it.
Status changed to Solved chandrika • 4 months ago