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

Conseguiu?

ainda não

você sabe como resolver isso amigo?

@Brody Can you help me with this here?

I have never used n8n ever

I also don't know what "normal" in "normal n8n" is referring to here

okay thank you

normal n8n = n8n standart

it is the version without workers and without webhooks processors

won't it need webhook processors to be able to setup oAuth with Google?

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

you'd need to find out what the differences between the two are

@Jack can you help me?

please don't ping <#727685388893945877> #5

ok

sorry

I'd appreciate if you could use English, very few people speak Portuguese

and how do I get support? I already created this call 4 days ago and I have not received a response

this is community support, please be patient

ok

thanks

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

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

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.

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:

https://webhook-processor-production-f0fe.up.railway.app/webhook-test/96059e09-9bf7-436d-8e11-ba1b8c9ee077fafadsfdasfdas

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. https://discord.com/channels/713503345364697088/1203039311272878174/1203702558733107241

thanks

I don't understand why I can't connect the Google credential

same here, I'm experince the same issue.

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/

would you mind stating what you needed to change exactly so that the template creator can update his template?

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!

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

Ah, nothing was broken, just performance improvements

gotcha, thank you, I've passed that information on to the creator

the creator has informed me that they have updated it, thank you!

!s