# I'm using a Unix socket between Caddy and Discourse instead of TCP, but from time to time I get a 'unix:' error

**URL:** https://meta.discourse.org/t/im-using-a-unix-socket-between-caddy-and-discourse-instead-of-tcp-but-from-time-to-time-i-get-a-unix-error/409124
**Category:** Support
**Created:** [3 augustus 2026 om 06:00 UTC](https://meta.discourse.org/t/im-using-a-unix-socket-between-caddy-and-discourse-instead-of-tcp-but-from-time-to-time-i-get-a-unix-error/409124 "2026-08-03T06:00:08Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![Willy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/willy/32/499930_2.png) [@Willy](https://meta.discourse.org/u/Willy)
#### Post date: [3 augustus 2026 om 21:52 UTC](https://meta.discourse.org/t/im-using-a-unix-socket-between-caddy-and-discourse-instead-of-tcp-but-from-time-to-time-i-get-a-unix-error/409124/8 "2026-08-03T21:52:10Z")

</div>

I think I found the problem. If I perform a rebuild, I never restart Caddy. From now on, I’m going to do this:

`./launcher rebuild app && systemctl reload caddy`

I suspect that Caddy uses the socket cache or something similar after a rebuild. But it doesn’t usually happen immediately after a rebuild. We’ll see.

---

_[View the full topic](https://meta.discourse.org/t/im-using-a-unix-socket-between-caddy-and-discourse-instead-of-tcp-but-from-time-to-time-i-get-a-unix-error/409124)._