You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for the delay. I tried multiple different configuration but never achieved the usage of the ingress. The frontend is not loaded properly through the proxy and I don't clearly understand why.
If you want to do some tries, you can clone the repo in the /config/addons folder of home assistant (through the ssh term for ex) and try some modifications. (in the config.json for example).
The addon will appear as a local addon within the addon menu of hass
The n8n webapp is not aware of the ingress path. Once you enable ingress, our browsers try to fetch the n8n webapp assets (like javascript and stylesheets) from /assets but because of the ingress it should be something like /api/hassio_ingress/3JKDFklsjf83-S0M3randomStuff7238sdjfSDf823/assets.
I've very little experience with Homeassistant addons and Homeassistant ingress. Anyway, it looks like other addon developers include an nginx reverse proxy in their container image to make it work (see e.g. Grafana addon or node-red addon). But this adds some complexity to the project.
Seems like just adjusting the base path of n8n is currently not an option unless you build n8n on your own.
Hello,
are there any plans to implement ingress to access web interface?
Best,
Viv
The text was updated successfully, but these errors were encountered: