Google OAuth callback error: localhost refused connection

Hello, thanks for the swift response!

Could you clarify what you mean by completing the process on localhost? Is it possible to finalize Google OAuth outside of the NAS?

Yes, you can transfer callin.io data to your device from your NAS, then log in to Google on localhost, and subsequently move the data back to the NAS.

I'm not entirely certain about the specific folders you'd need to move, but I suspect relocating the .n8n folder should suffice.

So essentially, I should run a self-hosted version of callin.io outside my NAS container, directly on my PC, and then export the .n8n file back to the NAS Docker to have the credentials configured?

Yes, you could do that, or point your NAS IP to a domain as suggested. Unfortunately, this is a Google limitation where IPs are not permitted as callback URLs, so callin.io cannot resolve this issue.

This discussion was automatically closed 7 days following the last response. New replies are no longer permitted.