How to expose and connect to Home Assistant

[Dr4gon]

Error Message and Logs

Using the given docker-compose.yaml to install Home Assistant results in no apparent error message and no access to the application because the port is not made available on a Raspberry PI 4 with Debian GNU/Linux 13 (trixie).

root@Egghead:~# curl localhost:8123
curl: (7) Failed to connect to localhost port 8123 after 0 ms: Could not connect to server

Steps to Reproduce

1. Install Coolify via the quick installation instructions
2. Create your admin account and login
3. Create a new Resource in one of your projects by choosing Home Assistant

4. Replace the domains name to http://localhost:8123

5. Open a browser and enter http://localhost:8123
6. Use curl on the server to verify that even on the machine itself, it's not reachable

root@Egghead:~# curl localhost:8123
curl: (7) Failed to connect to localhost port 8123 after 0 ms: Could not connect to server

Example Repository URL

https://github.com/Dr4gon/coolify/tree/next

Coolify Version

v4.0.0-beta.462

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 13 (trixie)

Additional Information

Hey Coolify-Team,

I found and fixed the issue already and will provide PR shortly after creating this.

Sunny regards,
De Long

[djsisson]

there is no error here, the container is being proxied via traefik, however you can't use localhost as the domain name, as your own host uses the name localhost, so this defaults to the main host not via the proxy.

setting network mode host via your pr, would then make this port public, which is a security risk
instead just use a domain name like sslip.io this would then route the traffic via the proxy

[Dr4gon]

@djsisson Thanks for the quick response. Fair point and I understand the explanation.

I tried to replace the domain with http://homeassistant.sslip.io:8123 and restarted the app and the Coolify proxy.

root@Egghead:~# curl http://homeassistant.sslip.io:8123
curl: (6) Could not resolve host: homeassistant.sslip.io

Then I tried to re-create the orginal URL (which I didn't save anywhere) by creating a new Home Assistant and just replaced the app name http://homeassistant-sws8cw8kwsskk4ss8k0okoo8.82.135.80.110.sslip.io:8123. Restart app and proxy, again.

root@Egghead:/# curl http://homeassistant-sws8cw8kwsskk4ss8k0okoo8.82.135.80.110.sslip.io:8123
curl: (28) Failed to connect to homeassistant-sws8cw8kwsskk4ss8k0okoo8.82.135.80.110.sslip.io port 8123 after 133301 ms: Could not connect to server

It seems the port isn't open. The below command shows nothing.

root@Egghead:/#  ss -tulpen | grep 8123

I also looked directly on the local server on my RaspberryPI 4 in which file Coolify itself with port 8000 is exposed via Traefik.

root@Egghead:/# find . -name "*.yml" -exec grep "traefik.http" {} +
./data/coolify/services/sws8cw8kwsskk4ss8k0okoo8/docker-compose.yml:      - traefik.http.middlewares.gzip.compress=true
./data/coolify/services/sws8cw8kwsskk4ss8k0okoo8/docker-compose.yml:      - traefik.http.middlewares.redirect-to-https.redirectscheme.scheme=https
./data/coolify/services/sws8cw8kwsskk4ss8k0okoo8/docker-compose.yml:      - traefik.http.routers.http-0-sws8cw8kwsskk4ss8k0okoo8-homeassistant.entryPoints=http
./data/coolify/services/sws8cw8kwsskk4ss8k0okoo8/docker-compose.yml:      - traefik.http.routers.http-0-sws8cw8kwsskk4ss8k0okoo8-homeassistant.middlewares=gzip
./data/coolify/services/sws8cw8kwsskk4ss8k0okoo8/docker-compose.yml:      - 'traefik.http.routers.http-0-sws8cw8kwsskk4ss8k0okoo8-homeassistant.rule=Host(`homeassistant-sws8cw8kwsskk4ss8k0okoo8.82.135.80.110.sslip.io`) && PathPrefix(`/`)'
./data/coolify/services/sws8cw8kwsskk4ss8k0okoo8/docker-compose.yml:      - traefik.http.routers.http-0-sws8cw8kwsskk4ss8k0okoo8-homeassistant.service=http-0-sws8cw8kwsskk4ss8k0okoo8-homeassistant
./data/coolify/services/sws8cw8kwsskk4ss8k0okoo8/docker-compose.yml:      - traefik.http.services.http-0-sws8cw8kwsskk4ss8k0okoo8-homeassistant.loadbalancer.server.port=8123
./data/coolify/proxy/docker-compose.yml:      - traefik.http.routers.traefik.entrypoints=http
./data/coolify/proxy/docker-compose.yml:      - traefik.http.routers.traefik.service=api@internal
./data/coolify/proxy/docker-compose.yml:      - traefik.http.services.traefik.loadbalancer.server.port=8080

I checked your docu and only found the dynamic config , but no mention where the normal routing is configured.

I have Coolify also running on a Hetzner server, where I provide the DNS configuration. There I can replace domains in Coolify appname.mydomain.io and Traefik takes the routing configuration. I.e. I can access the apps via the given domain.

• How can sslip.io be exposed locally in my home network on my RaspberryPI 4 without a proper DNS configuration?
• How can I configure the routing in Coolify?

[djsisson]

the port is only used for the proxy to connect to the container, the port is not opened on your host

you browse to a normal url domain.ip.sslip.io do not use a port when browsing
the proxy then forwards this request to the registed port (8123) inside the container for that service.

lastly you can use sslip with any ip, even 127.0.0.1 so you can still use it locally but its not exposed via a public ip.
alternatively, you can create a local domain and use that in your hosts file, traefik only matches the domain that it receives, so as long as your local domain points to the ip where you are running even 127.0.0.1 is fine, localhost is an example of that, but you need to create a different one for each service you need, but you would browse to port 80 (traefik) as that is what's being used on your host

[Dr4gon]

the port is only used for the proxy to connect to the container, the port is not opened on your host

Alright, got it.

you browse to a normal url domain.ip.sslip.io do not use a port when browsing the proxy then forwards this request to the registed port (8123) inside the container for that service.

Set the above domain, restarted app and proxy. This should do the trick, but it unfortunately doesn't :/

root@Egghead:/# hostname -I
192.168.178.102 10.0.1.1 10.0.2.1 10.0.3.1 10.0.4.1 10.0.0.1 10.0.5.1 fd10:e410:126a::1
root@Egghead:/# curl http://homeassistant.192.168.178.102.sslip.io/
curl: (6) Could not resolve host: homeassistant.192.168.178.102.sslip.io

What am I missing here?

[djsisson]

it resolves to 192.168.178.102 for me, only thing i can think of is how your local dns is setup, i.e your system resolver is not forwarding external requests??

[Dr4gon]

it resolves to 192.168.178.102 for me, only thing i can think of is how your local dns is setup, i.e your system resolver is not forwarding external requests??

Ah I see. This needs some clarification. The home assistant should only be available in my home network. From what I understand the moment I put in a valid url in domains Coolify exposes that app via Traefik in the internet.

Can I somehow replace the default slip generation with a custom DNS?

How can I configure in Coolify that an app only is available within a certain network?

[djsisson]

the url is only publically available if you are using a registered domain, using a sslip.io domain with a private ip does not expose anything to the public, since that url only resolves to the users own local private ip, in this case 192.168.178.102.

typing http://192.168.178.102/ and typing http://xxx.192.168.178.102.sslip.io/ is equivalent, however the latter is a url the former is just a direct ip address, using a url allows you to use a proxy to serve more than one service from the same ip without needing to use ports, but just using host names