Trying to configure IFTTT, but HA says I'm not accessible from the internet

Configuration
21

What does your base url look like?
Mine is this: https://my-domain.duckdns.org:xxxxx
I’m using a reverse proxy so I need to have the port xxxxx configured in the base url and then when I set up IFTTT it accepts it.

22

which port is the xxxx ? the one from the proxy (443 for me) or the one from HA (8123 for me) ?

i can connect to HA from 2 url:

23

if you use 443 then you shouldn’t need to include the port. I have one open port - that is xxxxx and the reverse proxy proxies that to 8123 for HA, 3218 for configurator etc. You will need to use the HTTPS one I believe, in your case https://homeassistant.domain.tld should work.

24

same error :frowning:
really i dont get it

25

i’ve found my problem,
before:

  http:
    base_url: !secret base_url

after:

http:
  base_url: !secret base_url

yaml synthax was wrong…

Thanks for your time !!!

1 Like
26

Bloody Hell!!! spacing kills you every time huh?

27

Hi, can you point it out, I can’t find it …

28

Looking at that again now maybe it’s not as useful as I thought.

29

if I remember correctly you use caddy, right? I do too.

So in order to have it working your solution is as below?

http:
  api_password: !secret api_password
  base_url: https:xxx.duckdns.org:8123
  cors_allowed_origins: 
    - http://192.168.1.11:7080

and in caddy file

   https://xxx.duckdns.org {      
    tls  /ssl/fullchain.pem /ssl/privkey.pem   {                            
        alpn http/1.1                                                    
    }                                                                    
    proxy / 192.168.1.11:8123 {                                            
        transparent                                                      
        websocket                                                        
    }                                                                    
    log stdout                                                         
    errors stderr                                                      
}
30

mmhhh not working for you?

Caddy

On Caddy you add the following to the proxy section(s) of your configuration:

header_upstream Authorization “Bearer YOUR_LONG_LIVED_ACCESS_TOKEN”

Alternatively, you can do the same in the header section if you want it for every page:

Authorization “Bearer YOUR_LONG_LIVED_ACCESS_TOKEN”;

31

Yes I use Caddy.

No I don’t use any of those except the base_url

No I don’t use the TLS or my own certificates. I let Caddy get LetsEncrypt certificates.

You asked me for that article so I found it and posted it for you.
Caddy is working perfectly for me even on IPv6 only (no IPv4). I have not added or used the long_lived_access_token.
I use only the normal HA auth with 2FA.

32

I tried as in my post and, so far, all is working. For anyone else that’s a working solution (443 port forwarded to 443 of the host hosting hass /Caddy)