Hi there, looks like this might be an application level issue to comply with Google's OAuth 2.0 policy so wouldn't be something we're able to fix on our end. Could you please recheck your application and it's configuration on Railway to see what the issue might be? A quick search yields: https://stackoverflow.com/questions/70638732/error-message-you-cant-sign-in-to-this-app-because-it-doesnt-comply-with-goog that could be helpful

Hey, so there are 3 parties

1. N8N Fork

2. Railway App Hosting

3. Google

On app level, there are 2: N8N Fork + Railway App Hosting.

The main N8N website - there's no issue, so I don't think it's anything wrong with N8N.

This means only can be configuration on Railway backend etc. ?

Yup, it could have to do with some redirection uri configuration — found this thread https://community.n8n.io/t/oauth-redirect-url-without-https-fail-access-blocked-authorization-error/44424/7 and it was resolved by adding a https:// to the N8N_EDITOR_BASE_URL , could you please try to manually add that and see if it helps?

Yes, https:// was already presence.

As I said, nothing wrong with N8N. If I were to subscribe to N8N and use their cloud service, it works perfectly fine.

But when I self-host with railway, I face an issue. So, something with the settings of Railway doesn't comply with Google's OAuth policy. I'm trying to figure that out.

Okay, managed to fixed it by changing some settings under Railway.

Under railway primary hosting settings - I found the editor_base_url, which I changed from the default to include https://

After which, it works. Thanks.

Amazing, glad to help and happy building !