@darklt1side the tell is your Logs panel saying nothing to display, the workflow never actually ran, so its not Gemini or the agent, the chat message just isnt reaching n8ns backend. on a NAS behind a reverse proxy n8n doesnt know its own public url, so the chat widget posts to the wrong place and you get “Failed to receive response”. set WEBHOOK_URL and N8N_EDITOR_BASE_URL to your real public NAS url (not localhost), add N8N_PROXY_HOPS=1, make sure the proxy forwards the X-Forwarded headers, then restart the container. thats the documented cause for this exact error on self-hosted docker.
Hi @darklt1side Welcome!
It works fine, maybe try upgrading your n8n instance and then try again:
Make sure you have credentials settled up for the Gemini chat model.
Thank you so much for your response. Best regards.
Your welcome! Happy I was able to assist you!
Thank you for sharing.
