a year ago
When adding credentials to n8n application I found that the prepopulated oauth callback url was referring to what must have been a previous public network URI, and Google oauth was failing. So, I made a slight change to the public url in railway, and now everything is running so very slowly. So, I also upgraded my plan thinking that it might be having RAM limitations, but still running very slowly or not at all.
7 Replies
Status changed to Awaiting User Response Railway • about 1 year ago
brody
Hello,Have you tried to redeploy your services since upgrading?
a year ago
no, I did it just before upgrading, but i'll do again.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
redeployed everything, and n8n gui comes up, but saving credentials, creating new workflows goes slowly then fail.
a year ago
Then you would need to get in contact with N8N's community for support for N8N as we cannot provide support for 3rd party software.
mapachekurt
redeployed everything, and n8n gui comes up, but saving credentials, creating new workflows goes slowly then fail.
a year ago
when it finally does work, i'm getting this error, which seems that the oauth redirect is not working properly for some reason.
Attachments
brody
Then you would need to get in contact with N8N's community for support for N8N as we cannot provide support for 3rd party software.
a year ago
yeah, I understand that.
Status changed to Closed brody • about 1 year ago