Caddy tutorial needed please

Configuration
22

Thanks for sharing the ip_bans file info, I’ve spent about an hour or two on this and to find out it was something so simple.

Thanks

23

@anon35356645

I finally got caddy (add-on, Bestlibre) working
this is my config:

{
  "homeassistant": "x.duckdns.org",
  "vhosts": [
    {
      "vhost": "y.duckdns.org",
      "port": "9000"
    }
  ],
  "raw_config": [],
  "email": "[email protected]"
}

28

In my router I have port 80 forwarded to 81 and 443 to 444 on my mac mini.
x.duckdns.org points to my HA
y.duckdns.org points to portainer

I also have the duckdns add-on
config:

{
  "lets_encrypt": {
    "accept_terms": false,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "xxxxxxxxxxxxxxxxxxx",
  "domains": [
    "x.duckdns.org",
    "y.duckdns.org"
  ],
  "seconds": 300
}
1 Like
24

The attached URL links to a tutorial I used to set up Caddy.
https://dew-itwebservices.com.au/setting-home-assistant-up-for-secure-access-over-the-internet/

25

@paul2nz i cant use my google assistant, i use the port 443 is there any specific configuration?
@DavidFW1960 i have this error , i use your tutorial

Screenshot_20190127-021515
Screenshot_20190127-021515325×578 36.9 KB

image
image538×600 48.3 KB

image

26

When you try and link the test app to home assistant, what is the URL it shows in the HA login screen?
What do you type in a browser to access your home assistant from outside your WLAN? Most likely, you have some mismatch in URL at Google - there’s a few places it is entered. Also, make sure your test app is enabled in the simulator on google dev console.

YOU DON’T NEED THE :443…

27

@DavidFW1960, answering the first question:

xxxxxx
xxxxxx1080×1920 113 KB

2 question:
outside i acess https://my_duckdns.org

3 ok i remove all 443
image
image

yes my test app is enabled in the simulator:

image
image719×321 32.5 KB

but the error is the same.

28

why are you still using the API auth instead of the new auth?
It’s not a caddy issue…

29

if i use the new auth, the error is the same… i dont understand why this happens.

30

all your posted urls look ok. I assume you’ve built an action?

31

the fact you’re seeing the HA login screen means caddy isn’t preventing you connecting… it’s a googe thing… I would just work through all the instructions for linking with google and make sure you didn’t miss anything. The google actions might show something in the logs?

32

when you write Logs, did you mean home-assistant.log? if yes no, i dont have any errors.

33

no I meant the log in google actions console

34

@DavidFW1960

image
image1443×628 62.6 KB

35

I can only suggest you go through the setup of the component from HA docs again to make sure you didn’t miss something.

36

I’ve done it all again, and it’s still the same. When i used duckdns without this addon everything worked fine.

I think I’ll give up, and use the dnsmasq addon, I just do not know if dnsmasq protects me as much as this.

37

what does your caddyfile look like?

38 
SECRET.duckdns.org {
    header / {
    Strict-Transport-Security "max-age=31536000; includeSubDomains"
    X-XSS-Protection "1; mode=block"
    X-Content-Type-Options "nosniff"
    X-Frame-Options "SAMEORIGIN"
    Referrer-Policy "same-origin"
    - Server
}
    proxy / localhost:8123 {
        websocket
        transparent
    }
}
nodered.SECRET.duckdns.org {
    proxy / localhost:1880 {
        websocket
        transparent
    }
}
grafana.SECRET.duckdns.org {
    proxy / localhost:1880 {
        websocket
        transparent
    }	
}
39

what about your http settings in config yaml?

40 
http:
  base_url: https://SECRET.duckdns.org
  api_password: !secret api_password_http
  ip_ban_enabled: True
  login_attempts_threshold: 3
41

All looks ok to me. Is there a reason you still have the old API-password enabled?