self-host-csmm-support

Your compose file would be helpful just for me to double cross check things.

idk your level of diagnose, check your docker networks and make sure they are not conflicting.... each of the servers talk via the container names, give me a few, ill get you my compose file, i added networks so only the containers that needed to talk to anything else would, then everything else stayed within an isolated network...

also a "cache" container

am going through the Compose and it does start a db container. The problem I am having is that the other containers are throwing errors that they can't connect to it

in the compose file
https://github.com/CatalysmsServerManager/7-days-to-die-server-manager/blob/master/docker-compose.yml
there is a cache (redis) and db (MariaDB) containers specified, as long as you have the ENV info correct, it will add the users/DB and configs for you

TLDR are you attempting the Host install? or Compose?
Host install walks you through adding both a DB and Redis server, the Compose file does it for you, both require info to be added to the ENV file

the documentation doesn't seem to indicate anything under the docker section in terms of creating mysql or redis usernames and passwords; only to pass a string with them

I was also busy at work.

that Idr and why I said check the documenation earlier

You also might need to create the database in MariaDB

Not in Cata's container. There was a container that was made for use on Unraid that has all dependencies with in the container.

I will install MariaDB and phpMyAdmin on my synology and make sure there are the correct csmm user and pass i set in the .env and see if that works

Thanks so much for this info SF. I will try that. I just wasn't sure if the mysql database and mariaDB etc came with the CSMM container or it uses the host resources for that

iirc you need to setup mysql separately in its own container then in the env you put the address and user/pass in there so it can connect

So, is the .env file leading to creation or is the .env just the info to connect to the database that already has that user and pass created?

Ok possibly silly question but I don't know enough about how the containers work with mysql. In the .env file, it sets a mysql user and password. Does this create the user and password, OR do I need to have mysql running on my synology outside of the container and set up the username and password there and the .env file just has the info?

I have scoured the docs for hours and have done a plethora of Google and discord searches and still stuck. I will continue to investigate and let people here know if I find a solution.

check the docs

catalysm/csmm

I thought you might have to setup the db and then connect to it. who's container are you using?

Ok thank you. I’ll try changing it to not only make it more secure but to also see if it fixes authentication issues of say the web container not being able to authenticate with the mariadb container. Not sure what is causing that.

well thats in there as default pw and is not secure at all

Because none of the containers can apparently connect to the mariadb container

Or am I just less secure?

Thanks SF. Would I get authentication issues if I don’t change it?

yes

Hi all, I’m a semi noob that is attempting to set up CSMM in docker on my Synology system and I feel like I am 90% there. I think the web container may be having a connection issue to the mariadb container. Noob question incoming! During .env modification, I didn’t change any of the database values or strings. When it lists things like “mysecretpasswordissosecure”, was I meant to change that as well as the MYSQL_PASSWORD default?

okay ill take a look to ngix thx

i use NoIP dns for my network

i run a couple of containers as use a domain. I use duck dns & nginx proxy manager

okay, any suggestions about?

already did, with allocs if i dont remember bad

at least a 10 character pw

you need to create a webtoken on the 7d server

yes reverse proxy if you want to access outside your home

should I Reverse proxy, or its nod really needed? i never did before and i dont really know what does it means

but now i dont know whats the next step on the operation

on the 7days server side i installed the required mods (allocs server fixes ans CPM)

here the screen i got when running the app

Okay, im a little bit stuck. I already susceed at self hosting implementation of csmm app on debian shell server. I have meet all the requeriments, made the database setup, configured .env file, and run the aplication suscesfully I guess

im a disaster

i realized haha, sorry so much

In the future please use pastebin

here is the fix, by chatgpt:

The error you're experiencing seems related to the Node.js version you're using. According to the logs, you're currently running Node.js v12.22.12, but the Unexpected token '?' error indicates that the code is using a JavaScript feature called nullish coalescing assignment (??=), which is not available in Node.js v12.

To resolve this, you need to update your Node.js version to a more recent one that supports these modern JavaScript features. The recommended version is at least Node.js v16 or higher.

Steps to Fix the Issue:
Check Compatible Versions for CSMM: Refer to the official CSMM documentation to verify the recommended Node.js version. As of now, Node.js v16 or v18 should work well.

Update Node.js Using NVM (Node Version Manager): Since you already have NVM installed, you can use it to install a newer Node.js version:

bash
Copiar código
nvm install 18
nvm use 18
nvm alias default 18
This will install Node.js v18 (or the latest compatible version) and set it as the default version.

Clean and Reinstall Dependencies: After updating Node.js, remove the existing dependencies and reinstall them:

bash
Copiar código
cd ~/7-days-to-die-server-manager
rm -rf node_modules package-lock.json
npm install
Run the Application Again: Now, try starting CSMM:

bash
Copiar código
NODE_ENV=production npm run start
Validate Configuration: Ensure the .env file is properly configured and that all external dependencies (e.g., databases, open ports, etc.) are set up as required.

Verify Node.js Version:
After updating Node.js, confirm you're using the correct version:

bash
Copiar código
node -v
This should show the updated version (e.g., v18.x.x).

okay i solved it

well i found out that its about my Node.js version installed

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/home/csmm/.nvm/versions/node/v12.22.12/bin/node',
1 verbose cli '/home/csmm/.nvm/versions/node/v12.22.12/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm@6.14.16
3 info using node@v12.22.12
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle csmm@2.3.0prestart: csmm@2.3.0
6 info lifecycle csmm@2.3.0start: csmm@2.3.0
7 verbose lifecycle csmm@2.3.0start: unsafe-perm in lifecycle true
8 verbose lifecycle csmm@2.3.0start: PATH: /home/csmm/.nvm/versions/node/v12.22.12/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/csmm/7-days-to-die-server-manager/node_modules/.bin:/home/csmm/.nvm/versions/node/v12.22.12/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/csmm/.dotnet/tools
9 verbose lifecycle csmm@2.3.0start: CWD: /home/csmm/7-days-to-die-server-manager
10 silly lifecycle csmm@2.3.0start: Args: [
10 silly lifecycle '-c',
10 silly lifecycle "cross-env NODE_ENV=production concurrently --kill-others -n 'app,worker' 'npm run start:app' 'npm run start:worker'"
10 silly lifecycle ]
11 silly lifecycle csmm@2.3.0start: Returned: code: 1 signal: null
12 info lifecycle csmm@2.3.0start: Failed to exec start script
13 verbose stack Error: csmm@2.3.0 start:

cross-env NODE_ENV=production concurrently --kill-others -n 'app,worker' 'npm run start:app' 'npm run start:worker'

13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/home/csmm/.nvm/versions/node/v12.22.12/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess. (/home/csmm/.nvm/versions/node/v12.22.12/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1022:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid csmm@2.3.0
15 verbose cwd /home/csmm/7-days-to-die-server-manager
16 verbose Linux 6.1.0-23-amd64
17 verbose argv "/home/csmm/.nvm/versions/node/v12.22.12/bin/node" "/home/csmm/.nvm/versions/node/v12.22.12/bin/npm" "run" "start"
18 verbose node v12.22.12
19 verbose npm v6.14.16
20 error code ELIFECYCLE
21 error errno 1
22 error csmm@2.3.0 start:

cross-env NODE_ENV=production concurrently --kill-others -n 'app,worker' 'npm run start:app' 'npm run start:worker'

22 error Exit status 1
23 error Failed at the csmm@2.3.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]