I'm trying to connect Google's oauth2-credential to the n8n but I just realized that if in this version of the N8n with Webhook processor it doesn't work and when I connect to the normal n8n it works perfectly
#N8n (w/ Webhook Processes) Does not connect with Google Sheets OAuth2 API
tranquil valley
brave windBOT
tranquil valley
this is my google setup.
URI 01 - is disabled
URI 02 - is the N8n with Webhooks Processor
URI 03 - This is the default n8n
this is the normal n8n that worked
this is the n8n with the webhooks processor that didn't work
uncut glade
Conseguiu?
tranquil valley
ainda não
tranquil valley
Conseguiu?
você sabe como resolver isso amigo?
tranquil valley
@marsh osprey Can you help me with this here?
marsh osprey
I have never used n8n ever
I also don't know what "normal" in "normal n8n" is referring to here
tranquil valley
I have never used n8n ever
okay thank you
tranquil valley
I also don't know what "normal" in "normal n8n" is referring to here
normal n8n = n8n standart
it is the version without workers and without webhooks processors
marsh osprey
won't it need webhook processors to be able to setup oAuth with Google?
tranquil valley
yes but the version with webhook processors does not work with google but the old version without webhook processors works.
I believe Jack can help me because he created this template
marsh osprey
you'd need to find out what the differences between the two are
tranquil valley
@verbal lintel can you help me?
marsh osprey
please don't ping #🛂｜readme #5
marsh osprey
I'd appreciate if you could use English, very few people speak Portuguese
tranquil valley
and how do I get support? I already created this call 4 days ago and I have not received a response
marsh osprey
this is community support, please be patient
marsh osprey
have you tried solving this yourself, by looking at the differences in the setups and trying to eliminate any differences? this is just a configuration issue after all
tranquil valley
I tried to see everything I could see differently but I couldn't find it.
I just installed this version created by jack and it doesn't work.
I installed the old version and it works perfectly.
From what I've seen, the only difference is the issue of workers, but I'll investigate further here.
thanks
verbal lintel
Just because it has webhook processors wouldn’t change anything besides coming to production node execution of webhooks.
Do you also have a picture of the error in the webhook processor version as opposed to the regular display?
It’s also not the “old version”, it’s simply the latest version of n8n with workers, the only addition in the webhook processor template is the addition and incorporation of a webhook processor service.
tranquil valley
I believe it is an error in the webhook module because when I try to create a workflow with a webhook and call this webhook via the http request node in another workspace it gives an error and shows me this here:
ERROR: The resource you are requesting could not be found
webhook link for an n8n project without Worker and without Webhook processor:
https://primary-production-aee1.up.railway.app/webhook-test/7e339fed-8929-4085-b366-eedda8828848
webhook link of an n8n project with Webhook processsor:
verbal lintel
webhook link for an n8n project without Worker and without Webhook processor:
h...
I can’t access those webhooks they’re not listening. In addition, read this remark to understand why that happens. I’ll make sure I add it to the template description to mitigate confusion. #1203039311272878174 message
visual meadow
same here, I'm experince the same issue.
heady hamlet
The Webhook processor took me an hour or so to get right, there are some settings that need tweaking/ There have been updates to n8n since the railway template's release. It's 100% worth reading this an getting familar with the variables and you can get everything to work nicely https://docs.n8n.io/hosting/scaling/queue-mode/
marsh osprey
The Webhook processor took me an hour or so to get right, there are some setting...
would you mind stating what you needed to change exactly so that the template creator can update his template?
heady hamlet
would you mind stating what you needed to change exactly so that the template cr...
Yeah, the template by default uses public urls for redis, which increases latency by about 200ms per request in my testing. However there was a recent n8n update that allows connecting to redis via ipv6 so the this flag can be added QUEUE_BULL_REDIS_DUALSTACK=true to all of the n8n instances. All of the redis vars can be updated as well to use the interal redis url and ports. Just doing that greatly improves performance!
marsh osprey
I knew about that, but from your message it seems like you eluded to changes that fixes something broken with the template? this just speeds redis access up is all
heady hamlet
Ah, nothing was broken, just performance improvements
marsh osprey
gotcha, thank you, I've passed that information on to the creator