OdinEidolon

Members
  • Posts

    27
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

OdinEidolon's Achievements

Newbie

Newbie (1/14)

4

Reputation

  1. Still doubtful on how I'd do that. There must be a simple way! Creating a custom `/etc/netdata/override/netdata.conf` does not work, and modifying the default file is overwritten on every container update. I guess one could add a path to the docker container template, but it does not seem like a proper solution to me.
  2. Hi and thanks for this docker template! I am trying to add settings to the `/override` folder, correctly mounted to `/etc/netdata/override` as per template default variables. I'd like to add simple settings that apply to `netdata.conf`, such as `hostname = hello-world`, without having to modify the `netdata.conf` file manually. Is that possible, or are `override` config only available for alarms and such? I can't find any documentation about that.
  3. Hi @ich777, I am testing out the PhotoPrism docker, thanks for that. I see you mention that one could use an external MariaDB docker as DB. Why should I? Would I have more stability/speed by doing so rather than using the SQlite that you built in?
  4. Same. I followed the suggestions from the last few pages: 1) loading a different docker image, and reloading :latest 2) Deleting MariaDB log files But my NC is still unable to start.
  5. Does anybody have any hint about what's going on here? I do not understand ifthis is an issue on duckDNS's side or some configuration mishap.
  6. SWAG stopped working for me, using duckdns. It worked OK for the last several months. I did not do any config change. Here's the docker log. Any idea? [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=Europe/Berlin URL=mydomain.duckdns.org SUBDOMAINS=wildcard EXTRA_DOMAINS= ONLY_SUBDOMAINS=true VALIDATION=duckdns CERTPROVIDER= DNSPLUGIN= EMAIL=mymail@mail.com STAGING=false grep: /config/nginx/resolver.conf: No such file or directory Setting resolver to 127.0.0.11 grep: /config/nginx/worker_processes.conf: No such file or directory Setting worker_processes to 4 Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing Wildcard cert for only the subdomains of mydomain.duckdns.org will be requested E-mail address entered: mymail@mail.com duckdns validation is selected the resulting certificate will only cover the subdomains due to a limitation of duckdns, so it is advised to set the root location to use www.subdomain.duckdns.org Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created Saving debug log to /var/log/letsencrypt/letsencrypt.log No match found for cert-path /config/etc/letsencrypt/live/mydomain.duckdns.org/fullchain.pem! Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Account registered. Requesting a certificate for *.mydomain.duckdns.org Hook '--manual-auth-hook' for mydomain.duckdns.org ran with output: OKsleeping 60 Hook '--manual-auth-hook' for mydomain.duckdns.org ran with error output: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 2 0 2 0 0 3 0 --:--:-- --:--:-- --:--:-- 3 Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems: Domain: mydomain.duckdns.org Type: dns Detail: DNS problem: SERVFAIL looking up TXT for _acme-challenge.mydomain.duckdns.org - the domain's nameservers may be malfunctioning Has anybody had any problem with duckdns recently? Of course I checked that all the settings, including the token, are correct.
  7. Was it just a matter of opening more ports?
  8. I personally have not tested yet... Here is a script to deploy the client and the server: https://github.com/GrimKriegor/TES3MP-deploy Here is a guide, it says it should be rather simple, but does not mention Linux: https://steamcommunity.com/groups/mwmulti/discussions/1/133258593388999187/ Here an older guide, but specific to Linux: https://steamcommunity.com/groups/mwmulti/discussions/1/133258092238983950/ Hope it helps a little bit. Once again, thank you very much.
  9. Hey @ich777, would you be able to provide a TES3MP server? Here's the github repo: https://github.com/TES3MP/openmw-tes3mp
  10. Just FYI The NWN server is broken if using the 'latest' NWN because the new 'latest' download is not https://github.com/nwnxee/unified/releases/download/buildlatest/NWNX-EE.zip but https://github.com/nwnxee/unified/releases/download/latest/NWNX-EE.zip
  11. Done! Thank you so much! Had to manually mount user.sh this way in the advanced docker options in Unraid: --mount type=bind,source=/my/path/to/user.sh,target=/opt/scripts/user.sh user.sh does: #!/bin/bash # Should be located in /opt/scripts/user.sh SSHD_CONFIG="Port 22\nPermitRootLogin no\nChallengeResponseAuthentication no\nUsePAM yes\nX11Forwarding no\nPrintMotd no\nAcceptEnv LANG LC_*\n" PASSWORD="myveryownpassword" # setting up keys is too much hassle ;) if [ ! -f /usr/sbin/sshd ]; then echo "### Installing missing pacakges ###" apt update && apt-get -y install ssh nano echo -e $SSHD_CONFIG > /etc/ssh/sshd_config echo "nwnee:$PASSWORD" | chpasswd fi echo "### Starting ssh ###" service ssh start
  12. Correct me if I am wrong. I would do this by: Configuring the container to open port 22 to the Unraid server (to port 22222 or something) entering the container by docker exec -it NWN /bin/bash apt update; apt install ssh edit ssh config in /etc/ssh/sshd_config service ssh start set ssh service to start on container boot (i do not know how to do this) set a new password for the nwnee user inside the container ssh nwnee@172.18.0.12 (or the exact container IP) screen -xS nwnee Am I missing anything? The only thing I think I have no idea how to do is step 6: I have tried both creating /etc/init/ssh.conf and using update-rc.d. Any suggestion?