I’m trying to start a workflow in my self hosted n8n instance and the form simply doesn’t load. Neither the test url or the production url. A popular comes up, but it stays empty or fails to load.
I have hosted it on a sub-domain of our website and I am accessing it through this subdomain. The ssl configuration is placed in my docker-compose.yml. Reverse Proxy is configured in our hardware firewall.
I can access the instance via https://n8n.oursite.de an I now can see, that the form urls in the node use http instead of https. Does that point to the problems root?
This is the beginning of my docker-compose.yml in the n8n service section. I have also tried port 443 and https protocol following Claude’s instructions, but i’m getting 502 proxy error in that case.
There’s a mismatch in your configuration. You’re accessing n8n via HTTPS but configuring it internally with HTTP. If changing to HTTPS/443 causes a 502 proxy error, this indicates your reverse proxy can’t reach n8n on that port. You need to ensure your reverse proxy is correctly forwarding requests to the container’s port 5678.
Does this also apply if I run self-hosting on my own network? There I do not access n8n via 443, but via 5678 if i understand it correctly from what my it support says.
Strangely enough, the form link works if I change it to https:// and remove the port from the link.
Okay, so this has worked. The form opens with the correct URL. Thank you for the hint with the wrong webhook configuration.
But my workflow is still having problems. I’m trying to send a GET-request to one of our servers. When i open the URL manually in my browser i can send the request for a job id for example and i will get the job id information. With n8n i want to send the job id via the form input as an expression in the request-url. The problem is, that the test doesn’t really respond. It’s still on “waiting for trigger event” even though i sent the form. When i look into the executions i can see, that the http-request cancels with the following message:
The connection cannot be established, this usually occurs due to an incorrect host (domain) value