Issue to get nttps access to my n8n instance

[Christianb23]

Hello

Describe the problem/error/question

My intention is to used a Asana Trigger node to inform my Home Assistant that there is a new event.
For that I have understood that a https webhook was necessary.
But unfortunately, I haven’t succeeded to link one of my duckdns domain : xxxx.duckdns.org to my n8n instance

What is the error message (if any)?

When I click on https://xxxx.duckdns.org , the website of my Freebox router opens (instead of my local n8n instance)

Please share your workflow

Share the output returned by the last node

When tested, obviously, the error is :

Bad request - please check your parameters

Show Details
Asana Trigger: Asana was unable to connect to your webhook because of SSL misconfiguration.

Information on your n8n setup

• n8n version: 1.56.2
• Database (default: SQLite): SQLite
• n8n EXECUTIONS_PROCESS setting (default: own, main): main
• Running n8n via (Docker, npm, n8n cloud, desktop app): npm
• Operating system: Windows 11

n8n has been installed on Windows 11 with npm
I have tried to change the variables such like this :

----                           -----
N8N_PROXY                      true
N8N_EDITOR_BASE_URL            https://xxxx.duckdns.org:5678
N8N_HOST                       localhost
N8N_WEBHOOK_TEST_URL           https://xxxx.duckdns.org:5678
N8N_WEBHOOK_URL                https://xxxx.duckdns.org:5678
N8N_PROTOCOL                   http
N8N_PATH                       /
N8N_PORT                       5678
N8N_SECURE_COOKIE              false
N8N_CUSTOM_HEADER_SIZE         32768

I use the Nginx Proxy Manager Add-on installed (with Maria DB) on the Home Assistant Vitrual Machine 192.168.1.34 (I think a kind of container), which is bridged to the same networks of my mini PC 192.168.1.27 where n8n is installed.

I can easily access to http://localhost:5678 and http://xxxx.duckdns.org:5678 ,but I am not able to reach https://xxxx.duckdns.org:5678 which opens my freebox router webpage (probably because the IPv4 adress in duckdns of xxxx is the IP adresse of my router).

On my router Freebox, I have redirected the ports

• 80, 443 and 81 to my Home Assistant Virtual Machine
• 5678 to mini PC where n8n is installed

Here are the set-up on Nginx Proxy Manager and status of my proxy host is “green - on line” and the duckdns certificate is created :

I thank you in advance for your help

[Jon]

Hey @Christianb23,

I suspect you have your router configured to respond to https traffic instead of directing the traffic to nginx proxy manager. The IP being that of your router is fine but as long as you have configured the internal network routing correctly it should work.

The downside is I don’t have a Freebox router so I am nto sure which setting you need to change but I would imagine there is a freebox community somewhere that knows how to do it.

You could also look at using Cloudflare or NGROK instead to use a tunnel so that you don’t need to expose your home network to the internet.

[Christianb23]

Thank you @Jon for your answer.
What is strange is that there is a duckdns add-on in home assistant which enables me to have a https://yyyy.duckdns.org:8123 access, making the link between another duckdns domain and my home assistant instance with the help of let’s encrypt, so that should mean that it is possible to make the same thing between xxx.duckdns.org and nginx proxy manager add-on, no ?

[Jon]

Hey @Christianb23,

That could be possible however I don’t use DuckDNS or know how the home assistant add-on works. In theory you should be able to make it work without using add-ons it is normally a case of opening port 80 / 443 on a firewall and pointing it to the reverse proxy on your internal network that will handle the connections and all is good.

In your set up you will need to find out what that route is and configure it.