Thomas Anderson

Any movement on this? I know it's a lot to implement... maybe a PR with a checklist to track the progress? :)

Working on implementing option 2 from above [here](https://github.com/tnyeanderson/unbound-docker/tree/fix-healthcheck-cache/1.16.3) It works for the first healthcheck after internet is cut off for the container, but then after that it serves an empty...

Sorry, I should've explicitly mentioned that the example above is [with remote-control enabled](https://github.com/tnyeanderson/unbound-docker/blob/119ab0d0cd5ccf8af48c9aca565673777a7267ea/1.16.3/data/unbound.sh#L354-L356), which is why it works the *first* time the cache needs to be cleared. In other words,...

Please look into this as well: https://github.com/bq/cervantes

Having this same issue. I am using Caddy to locally serve a web interface for my app (`web.heart.lan`) and a gotify server (`push.heart.lan`). If I go to `push.heart.lan` in my...

They are both accessed via 443. `web.heart.lan` is reverse proxied to `localhost:8081` (where the web interface is listening) `push.heart.lan` is reverse proxied to `localhost:8080` (where Gotify server is listening) Both...

I've actually tried both. Here was my original config before switching to regex: ```yaml server: cors: # Sets cors headers only when needed and provides support for multiple allowed origins....

@jmattheis With the configuration you provided, I still get a 403 error :(

``` heart-sms-push | [GIN] 2021/11/19 - 19:44:20 | 403 | 47.09µs | 127.0.0.1 | GET "/stream?token=[masked]" ```

The first (403) is running the console code above from `web.heart.lan`. The second (one that works) is running the same console code on `push.heart.lan` ``` heart-sms-push | Starting Gotify version...