Hello
I’m completely new here and looking forward to n8n. Unfortunately my first attempt failed. But I think I know why but still need your help.
I have running n8n as a docker container behind a SWAG proxy (SWAG setup - LinuxServer.io).
This works. So I have the possibility to access with httpS and do not need a specification port.
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name n8n_web.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
location / {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_app n8n_web;
set $upstream_port 5678;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;
}
}
Now the first workflow I tried was this example - https://n8n.io/workflows/782
Telegram bot is created - credentials entered but I get this error message
Telegram Trigger: Bad Request: bad webhook: HTTPS url must be provided for webhook
I also found this I the community Issue-with-telegram-webhook/1374 (since I’m a new user I’m not allowed to have more than two links).
I assume that the internal container name is sent as webhook URL to Telegram but this is only available internally and not httpS.
How can I adjust the workflow (or the server config) so that the external URL name is sent including https e.g. n8n_web.mydomain.com.
I don’t want to start n8n with the tunnel
Look like the answer is in the Issue-with-telegram-webhook/1374 - i just have not been seeing it the first three times i read it - sorry - i will try an d report back - have to adjust my docker-compose …
Do you have a proper URL (instead of IP address) with a valid SSL certificate set on the default HTTPs port (443, so that no port has to be set in the URL)?
If Telegram says the URL is invalid there has to be a reason. There must be something out of the ordinary.
HI jan - I will try a simpler example - at the moment I only play arround and only when I have time … will get back to you if this simpler example is NOT working … Webhook Creating Endpoints Part 1 - YouTube …
but i don’t exactly when i have time to try
Hello
I have played arround a bit When I create a webhook myself everything goes well. However when I create myself a Telegram trigger (similar to the imported one) it looks a bit weird.
Here is the web URL .
The Webhook in the Telegram Trigger node is expected to have /webhook at the end. The webhook is generated by n8n and has to be unique. You can’t change the webhook path of any trigger nodes, except the Webhook node itself.
Did you try executing a Webhook node? Did it return the expected output?
…