Synology, Portenier, Docker Mumble Setup

[wliporace]

I'm not sure where to start! I'm VERY new to mumble, Synology & Docker. I've got absolutely no idea (sort of) what I'm doing. I have portainer installed on my Synology DS918+. I was able to get RustDesk to work. I just followed one of the online instructions and no issues that I know of so far!

Recently I was introduced to mumble. It should be a great answer to what I would like to do (mostly have ham radio audio get passed, duplex). I know there are lots of threads to do this on a raspberry pi. Yea, I have a couple that I could use. I thought the Synology NAS would be a better option!!

If I specify what I think is the right path to my NAS, I get:
/entrypoint.sh: line 77: /data/mumble_server_config.ini: Permission denied in the logs for the container.
If I let the system create the container/stack from mumblevoip/mumble-server, no issues.
The problem is that I have NO idea on how or where to edit things. I tried and the terminal told me that there is NO editor and I don't have any option to install one.

Anyone that can help would be awesome! I need a little training and understanding of how this works. The good news, my works schedule got better with the weather coming in!

[Krzmbrzl]

You'll have to provide more detail on how exactly you are starting up the Docker service. Otherwise, all we can do is to guess.

[Krzmbrzl]

No, the one set via environment variable is the correct one. Check the docker logs to verify that it has been used as intended.

[wliporace]

So since I didn't use an environment variable, I specified the name, it would not create the database.
Is that also why I can't get the SuperUser to login?

So I guess I really don't understand .env file or how to configure the environment variables.
If someone can point me an actual example with the command to address it, I would like to do this correctly.
My mumble server is running, but I can't do anything with it.

[Krzmbrzl]

The DB username has nothing to do with the SuperUser account. If you don't set the password explicitly, it will be auto-generated and printed to the log upon first server startup.

[wliporace]

PLEASE understand that I'm still really new to this!!
OK, then should I say the following:
MUMBLE_CONFIG_DB_USERNAME: SuperUser
MUMBLE_CONFIG_DB_PASSWORD: MyFake Passw0rd
Rather than specifying:
MUMBLE_CONFIG_DB_USERNAME: myuserID
MUMBLE_CONFIG_DB_PASSWORD: MyFake Passw0rd
I have not figured out secrets (does not work in stand a lone)
Or how to create a real environment file for docker compose to use.

As an update, my knowledge of this stuff is minimal. I am still trying to get this 60+ yr old up to speed!!

[Krzmbrzl]

No. As I wrote in my last post: The DB username (and password) has nothing to do with the SuperUser account.
The former is used to authenticate with the database Backend (PostgreSQL in your case) and that's it. Mumble doesn't know anything about that beyond the DB connection.

The SuperUser on the other hand is an actual user on your server that you can authenticate as (log in to, so to say) and it is equivalent with the administrator on a regular PC (technically, the SuperUser is even above an administrator, but that's not too important here).

The SuperUser account is created when the server boots for the first time. At this point, it will auto-generate a password and print that to the server's log (it'll print it to the console). So by inspecting this, you will be able to extract the password.
However, you can also explicitly tell the server what password it shall use for the SuperUser account (or change it at a later point). In the docker image this works by setting the MUMBLE_SUPERUSER_PASSWORD environment variable (see https://github.com/mumble-voip/mumble-docker#additional-variables).

[wliporace]

[Krzmbrzl]

Keep calm. We also have a live outside of GitHub, so it may take some time for someone to look at the updates here and answer accordingly. if there is still some info missing, they will let you know.

[wliporace]

I see mumble-server running. I see postgres running mumo is not running and gives a "Request failed with status code 409" message when I start it. clients can't connect. So I may have answered some of my questions.

…

On 3/16/2023 10:57 AM, azlux wrote: This look like a indent issue: YAML is indentation dependent. |services: postgres: | should be : |services: postgres: | — Reply to this email directly, view it on GitHub <#31 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A44QF3OUF4EMLGTCAX6YL3DW4MS7JANCNFSM6AAAAAAVYOTRHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[wliporace]

Now I noticed that the mumble-server is continuously restarting!
So that explains why I can't connect to the server.