# Proper documentation for server

**URL:** <https://kopia.discourse.group/t/proper-documentation-for-server/2851>\
**Category:** Support\
**Created:** [April 26, 2024, 9:49pm UTC](https://kopia.discourse.group/t/proper-documentation-for-server/2851 "2024-04-26T21:49:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![p4tpr0](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/p4tpr0/32/1027_2.png) [@p4tpr0](https://kopia.discourse.group/u/p4tpr0)\
**Post date:** [April 26, 2024, 9:49pm UTC](https://kopia.discourse.group/t/proper-documentation-for-server/2851/1 "2024-04-26T21:49:59Z")

</div>

hello,

Is there a proper documentation for «kopia server» options?

Especially:

- usage example / use-case for `--server-control-password` and `--server-control-username`
- same for `--server-password` and `--server-username` and difference with above
- use-case for `--[no-]async-repo-connect`
- why does `--htpasswd-file` has no default? where are stored user credentials when you don’t specify this parameter?
- use-case for `--override-hostname` & `--override-username` server-side

thanks!

---

<div class="post-metadata">

**Author:** ![iBackup](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/ibackup/32/355_2.png) [@iBackup](https://kopia.discourse.group/u/iBackup)\
**Post date:** [April 27, 2024, 1:16pm UTC](https://kopia.discourse.group/t/proper-documentation-for-server/2851/2 "2024-04-27T13:16:36Z")

</div>

> [@p4tpr0](#):
>
> usage example / use-case for `--server-control-password` and `--server-control-username`

Check this thread: [KOPIA server: SERVER\_CONTROL\_USER](https://kopia.discourse.group/t/kopia-server-server-control-user/1033)

> [@p4tpr0](#):
>
> use-case for `--[no-]async-repo-connect`

As far as I understand: Connect to remote repository and while it connecting start doing other things preparing to more quick processing.

> [@p4tpr0](#):
>
> why does `--htpasswd-file` has no default?

Because there no defaults.

> [@p4tpr0](#):
>
> where are stored user credentials when you don’t specify this parameter?

Credentials stored inside of specified `htpasswd` file, in the same way as it is in Apache  
It was used prior to kopia v0.8

> Path to htpasswd file that contains allowed user@hostname entries

> [@p4tpr0](#):
>
> use-case for `--override-hostname` & `--override-username` server-side

I see it used extensively in test, as well you can override name of actual server’s hostname with your own, like “MySuperServer-0001” instead of “DESKTO-XYZ123”

---

<div class="post-metadata">

**Author:** ![p4tpr0](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/p4tpr0/32/1027_2.png) [@p4tpr0](https://kopia.discourse.group/u/p4tpr0)\
**Post date:** [April 29, 2024, 9:22am UTC](https://kopia.discourse.group/t/proper-documentation-for-server/2851/3 "2024-04-29T09:22:17Z")

</div>

thank you for those clarification attempts.

About the `--override-hostname`, server-side:

- say I have a server with many virtual hosts configured in my HTTPS proxy (foo, bar, baz…).
- if I make the kopia server init without `--override-hostname` it will pick the default server hostname (foo) when creating kopia’s TLS certs
- say I choose another vhost (bar) in my HTTPS proxy to publish the kopia service

I will end up having an error when the proxy connects to the kopia backend (TLS name does not match)

Will using `--override-hostname=bar` at init can prevent that hostname mismatch between front HTTPS proxy and TLS cert of kopia backend?