Has anyone been able to get rancher running on a non-standard port? It gives a network error on the login page, and looking at the javascript logs, it gives the error: "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://rancher.nicholasbernstein.local/v3-public/localProviders/local?action=login. (Reason: CORS request did not succeed). Status code: (null)." I've tried changing the hostname in the helm chart to include :444, I added a snippets to the nginx ingress:

nginx.org/location-snippets: |
      add_header Access-Control-Allow-Origin: "*"

as well as a number of variants that included the actual urls. If there are reasonable alternatives I'm not thinking of that would give the same functionality - we want it on a separate port so we can lock it down with firewall rules, but we are using standard 80/443 for another ingress with different firewall rules on the same public ip.