this however does not work with the ingress.. if i...
# umh-support
d
this however does not work with the ingress.. if i use the hostname assigned in the router it sends me to 8080 and not 8443.. it works fine using the ip and port
ok, so i finnally cracked it.. needed to ingresses, one for redirect from http to https and the anotherone to skip the certificate verification.
# we need 2 ingresses. first to redirect from http to https and then another to skip verification of certificates # redirect from http to https apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: namespace: unifi name: unifi-controller spec: routes: - match: Host(
unifi.local
) kind: Rule services: - name: unifi-controller port: 8443 middlewares: - name: redirect-https --- # middleware to handle the redirection from http to https apiVersion: traefik.containo.us/v1alpha1 kind: Middleware metadata: name: redirect-https namespace: unifi spec: redirectScheme: scheme: https permanent: true --- # ingress for selfsigned certificate apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: namespace: unifi name: unifi-controller spec: routes: - match: Host(
unifi.local
) kind: Rule services: - name: unifi-controller port: 8443 scheme: https serversTransport: insecure-https --- # server transport to skip certificate checking apiVersion: traefik.containo.us/v1alpha1 kind: ServersTransport metadata: name: insecure-https namespace: unifi spec: insecureSkipVerify: true
j
wow crazy
but now we have it
thank you for posting!
d
Yes. The first approach worked fine when using the loadbalancer but then i had problems with port 8080 and 8443 since the unifi system is configured to use those, so an additional ip in the cluster host and node port made it. I have all the manifests at my computer. We could write a short article about how to deploy it on flatcar and in parallell with umh. I guess there are many out the using unifi controller since Ubiquiti is quite large in networks.
3 Views