I see traefik is back in the catalog. i remember it from back in the k3s days where i would port forward port 80 + 443 to it and when deploying other apps in the catalog i could check a box to use traefik to proxy that app’s traffic.
while i see the new app has a webui port, i dont see the default of 80 + 443 going to it. nor do i see an option on other apps to use traefik as the proxy.
does anyone know how the newly released traefik is supposed to function as a rev proxy now that it has been re-released?
so im guessing this one will just use the tags. but how is iX expecting this to work for truenas apps from the catalog? also why would this not expose 80 and 443 by default knowing its a reverse proxy?
truenas apps support labels for a long time, so you can simply add the required labels from the edit gui.
As for port 80 and 443 i dont know, my traefik app runs inside an lxc… i don’t trust truenas apps anymore
I looked up this traefik app and I think you must enter the required info for endpoints. For example you must add two endpoints, one for http traffic and one for https traffic. If you add an endpoint, you must provide the port information too, on which the endpoint will listen to the traffic and will route it to the app where its labels are configured.
I did not tried that yet, but will when I have time for that.
Basically those who know what this is would either setup alias interfaces and/or changing the default GUI ports first beforehand and then changing the ports there, similar to the experience using Nginx-Proxy-Manager.
Otherwise you’d have tons of users who install it and lock themselves out of the GUI and/or can’t install it at all because of the port conflict