Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to reach via unifi.domain #3

Open
bigverm23 opened this issue May 1, 2020 · 3 comments
Open

Unable to reach via unifi.domain #3

bigverm23 opened this issue May 1, 2020 · 3 comments

Comments

@bigverm23
Copy link

Hey, thanks for all of these great containers. I am unable to reach this one via unifi.domainname.

The only I can reach the container is via https://10.0.0.216:8443, which isnt really making sense to me.

Would you be able to help?

@bigverm23
Copy link
Author

bigverm23 commented May 1, 2020

I tried to use the alt method as well, but get a "unifi.domainname has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. "

[tcp.routers]
  [tcp.routers.unifi-rtr]
      entryPoints = ["https"]
      rule = "HostSNI(`unifi.domainname`)"
      service = "unifi-svc"
      [tcp.routers.unifi-rtr.tls]
        certresolver = "dns-cloudflare"
        passthrough = true

[tcp.services]
  [tcp.services.unifi-svc]
    [tcp.services.unifi-svc.loadBalancer]
      passHostHeader = true
      [[tcp.services.unifi-svc.loadBalancer.servers]]
        address = "10.0.0.216:8443"

`

@CVJoint
Copy link
Owner

CVJoint commented May 8, 2020

My Unifi controller is running off of a raspberry pi (separate from my Traefik host), so I'm using the alt method you mention above. If they were on the same host I would try to use labels similar to how the Nextcloud container is set up.

I also have my internet traffic proxied through Cloudflare (orange cloud) and I know that when I've messed with the HSTS settings in Cloudflare I've seen those type of errors.

@mikejac
Copy link

mikejac commented May 28, 2020

@bigverm23 The Unifi Controller creates it's own, self-signed certificate at installation time. Firefox does not accept that kind of certificates anymore. In my setup, I have created my own certificate authority using EasyRSA and then issued a certificate for the Unifi URL. My root certficate is imported into Firefox (Firefox uses it's own certficate store, not the operating systems certfificate store).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants