#Custom Domain and HTTPS

1 messages · Page 1 of 1 (latest)

still fossil
#

Latest version of HAOS installed. I followed the DuckDNS configuration, but when I go on

myhaos.duckdns.org <--- not the real url, but for this context

It gives a 400 error...

I checked the nginx log, and it booted correctly as well as the duckdns

Although, this is really the first few steps, I want to use my

custom.domain.com

Eventually, I have a custom domain and the subdomain is point to my IP. I want the Duckdns to work first.

I have Port forwarded: 80, 443 and 8123

stark basalt
still fossil
#

Good idea let me check

#

Yes, if I go to

myip:8123

stark basalt
#

from a system outside the network?

#

i ask because a lot of people find themselves behind CGNAT without realising

still fossil
#

Yes my iphone using LTE

stark basalt
#

ok, well that's that ruled out anyway. maybe someone with more knowledge of duckdns/nginx config can jump in

still fossil
#

I understand well nginx though the addon makes it complicated

dawn dock
#

assuming you have 80 and 443 pointed to NGINX, there's no need to also forward 8123

#

did you add the docker subnet to trusted_proxies in the http: config?

still fossil
#

Where are the actual nginx settings?

dawn dock
still fossil
#

I did not add it

still fossil
#

that did it lol!

#

Thank you,
Do you know or anyone knows how to generate automatically cert for custom domain wihtout using the duckdns?

dawn dock
#

let's encrypt is one option

#

personally, I use Caddy which handles that

still fossil
#

lets try caddy

#

thank you by the way a lot