# Go-pluginserver terminated when using custom Go plugin

**URL:** <https://discuss.konghq.com/t/go-pluginserver-terminated-when-using-custom-go-plugin/5969>\
**Category:** Questions\
**Created:** [April 7, 2020, 8:29pm UTC](https://discuss.konghq.com/t/go-pluginserver-terminated-when-using-custom-go-plugin/5969 "2020-04-07T20:29:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![alex](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@alex](https://discuss.konghq.com/u/alex)\
**Post date:** [November 12, 2020, 3:34pm UTC](https://discuss.konghq.com/t/go-pluginserver-terminated-when-using-custom-go-plugin/5969/2 "2020-11-12T15:34:14Z")

</div>

Try this:

> [@Kong:2.0.5 infinite loop go-pluginserver terminated](https://discuss.konghq.com/t/kong-2-0-5-infinite-loop-go-pluginserver-terminated/6715/2):
>
> Hi @taotao. When the go-pluginserver starts, it attempts to create a Unix domain socket in the Kong prefix; as such, you need to ensure that the Kong prefix is writeable by the user that is starting the go-pluginserver.

---

_[View the full topic](https://discuss.konghq.com/t/go-pluginserver-terminated-when-using-custom-go-plugin/5969)._