New Caddy add-on

There might be a duckdns as well… You are definitely running Hass.io and the caddy addon in hassio? You have ports forwarded as well? 80-80 and 443-443? WHat does caddy show in the logs?

Sorry if you’ve answered all these before… I’ve spent a week learning more than I ever wanted to know about docker and linux and my mind is going STOPPPPPPPPPP.

All I can say is in the last month I have configured hass.io in ResinOS, HassOS, Raspbian with docker, NUC with Debian and docker and the only trouble I had on any of them was I had to re-add the repo for Caddy and reinstalling it after restoring a snapshot and it went merrily on it’s way… Caddy works like mad and I just don’t understand why you are having issues.

apologies, yea definitely a strange one here, i myself have good experience with these, but this one is not getting through to me, i’m very sure of running Hassio with caddy addon in it. ports forwarded 80-80 and 443-443 , it intrigues me as well why the setup wont work, the PI or the add-on has nothing to do with this error as i had caddy on another system and got the same error, i had the ISP on call and checked my ports and confirmed all are good , so its either my $250 router causing this or some wrong config in it. well i think i might remove the duckdns addon and use the router’s dns service or call my ISP to change to a static ip.

this error

starting version 3.2.4
Running Caddy with arguments: -conf /share/caddy/Caddyfile -agree -email [email protected]
2018/08/25 13:59:29 [X.duckdns.org] failed to get certificate: acme: Error 400 - urn:acme:error:connection - Fetching http://X.duckdns.org/.well-known/acme-challenge/p17j_aVf8m30FC5ar5S0sVL3MW7Hs3IhDhfECrMvXeg: Timeout during connect (likely firewall problem)
Error Detail:
Validation for X.duckdns.org:80
Resolved to:
X.X.239.X
Used: X.X.239.X
Activating privacy features…

OR

Activating privacy features…2018/08/22 15:53:39
get directory at ‘https://acme-v01.api.letsencrypt.org/directory’: failed to get json “https://acme-v01.api.letsencrypt.org/directory”:
Get https://acme-v01.api.letsencrypt.org/directory: net/http: TLS handshake timeout

So it’s failing getting the certificates… are you certain your ISP doesn’t block port 80? (Mine does but unblock on request)

It could be a setting in your router… can you temporarily put the Pi in the DMZ on the router and see if it can get the certificate then?

1 Like

i was assured its not blocked, is there anyway i can check and confirm.

not working on DMZ too.

Try forwarding 80 to 8123 and go to http://external-ip-address and see if HA loads (make sure you’re on the public internet not internal network). Don’t leave it like that of course.

:open_mouth: its not working externally, i checked on two networks and its showing connection refused, these guys must be kidding me… i raised a complaint again, its working from the same broadband, but thats just nat loopback i guess… thank you @DavidFW1960 , i have a long call with ISP today.

1 Like

You don’t run Pihole or anything like that that might be blocking the port?

pihole is moved to another port, i never port forwarded pihole at all. i even removed that from the setup and checked, i also placed another router removed the existing one and still the same. so im convinced its port issue from ISP side.

i have error 403: forbidden when i connect outside my lan.
ports 80 and 443 are open. caddy running without errors and dns.
checked online with port checker and they are all open

Ip_bans.yaml delete if there after looking to see who tried to connect
that was my problem

thanks mines a completely different issue, its the ISP blocking port 80

Hello @DavidFW1960, after much calls with ISP, i got port 80 and 443 released and its all working now. i wanted to thank you for your help. :slight_smile:

1 Like

Great it’s now working!

Hello, all. I’m sorry for the radio silence. I’ve not had a lot of time to devote to my Hass.io add-ons.

I did want to let everyone know that I released version 1.4 of my Caddy add-on. The most useful new feature is the ability to use custom Caddy binaries (so that you can use plugins!)

Take a look at the README for more info if you want to do that.

Also, thanks to everyone who’s been able to help others out on this thread!

5 Likes

Saqys update available, click update, spins circle a few times and then back yo update available again… it’s not installing the update

Oh crap I just removed it and it won’t install now

Just found out the amd64 version didn’t upload. Is that what architecture you’re on?

It’s fixed now, but the hass.io builder keeps failing to upload to Docker Hub randomly. Sorry about that.

If it’s still not working, can you let me know what hardware you’re on?

Also, try to install the update again, then go to Hass.io -> System and refresh the log. Then copy and past the last few log entries here.

oh oh… it’s installed but this is all I get in the log when I start it

Running Caddy with arguments: -conf /share/caddy/Caddyfile -agree -email [email protected]
Using built-in Caddy: Caddy 0.10.14 (unofficial)
``

restarted it and it’s got a real log again now…

So does it seem to be functioning now?