Hi @jhhbe,
The token within the duckdns addon is for duckdns only. The letsencrypt part needs your email only.
The caddy tokens are stored in a dedicated folder within the SSL folder, therefore no interference.
BTW, you can have the best from both with following setup (which I use):
Duckdns Addon: Set accept_terms to false. That way no certificates will be created.
Caddy Addon: Here I have configured all URLs. Since Caddy takes care of the whole SSL management, no further worries. 
Thanks @berichta. They describe problems with vhost settings. However I do not have set those. My config is simply:
{
“homeassistant”: “mydomain.com”,
“vhosts”: [],
“raw_config”: [],
“email”: “[email protected]”
}
my configuration file looks like this:
http:
# Secrets are defined in the file secrets.yaml
api_password: !secret http_password
login_attempts_threshold: 5
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
base_url: XXXXXX.com
# ssl_certificate: /ssl/fullchain.pem
# ssl_key: /ssl/privkey.pem
And I set port forward 443>443 and 80>80 to the IP of hassio.
I’m just starting with this, so not sure if this is correct. I could not find anywhere how the other settings should be set:
Strange, your config looks good to me. Do you have any other addon running on port 80 or 443?
Yes thanks. thought I deleted nginx, but appearently it was still installed. It is working now!
Thanks for explaining @berichta - found the caddy subfolder in /ssl. Nice that things can work without knowing why/how.
I’ll check if my router supports duckdns, if not I’ll switch to using your setup. If it does, I’ll have one addon less.
Jhh
Hi all,
I got the Caddy proxy addon working with this config:
{
"homeassistant": "home.redacted.tld",
"vhosts": [
{
"vhost": "nas.redacted.tld",
"port": "5000",
"paths": []
}
],
"raw_config": [],
"email": "[email protected]"
}
But what i am interested in is having a sub-path with the default sub-domain like: ‘home.redacted.tld/nas’ instead of having an other subdomain (nas.redacted.ytld) to my synology nas.
Can someone please be so kind to help me out with this?
Regards
You should be able to do that with the paths option.
You can try this config (based on your example) :
{
"vhosts": [
{
"vhost": "home.redacted.tld",
"port": "8123",
"paths": ["/nas 152.17.0.1:5000"]
}
],
"raw_config": [],
"email": "[email protected]"
}
Thanks for your reply @bestlibre. i had to add "homeassistant": "", above "vhosts" otherwise it will re-add "homeassistant": "homeassistant.domain.tld",.
However, this works for may main site “https://home.redacted.tld” but going to “https://home.redacted.tld/nas” with the subpath included, i get an error:
I have also tried to proxify HA-Configurator on port 3218, but then i get"
no auth header received
This is my config atm:
{
"homeassistant": "",
"vhosts": [
{
"vhost": "home.redacted.tld",
"port": "8123",
"paths": [
"/haconfig 192.168.1.115:3218",
"/nas 192.168.1.1:5000"
]
}
],
"raw_config": [],
"email": "[email protected]"
}
So i’m kinda clueless now