Everything posted by pkoasne
-
[Plug-In] Community Applications
Is there a way to disable the `External Link` warning entirely?
-
After upgrade to Unraid 7 beta 2 SSH no longer works
Booting into safe mode fixed it. Thanks
-
After upgrade to Unraid 7 beta 2 SSH no longer works
Version 7.0.0-beta.2 2024-07-12 I realized I couldn't SSH in anymore after rebooting for the update.
-
After upgrade to Unraid 7 beta 2 SSH no longer works
Sep 27 14:47:49 Castle rc.sshd: Starting SSH server daemon... Sep 27 14:47:49 Castle rc.sshd: /usr/sbin/sshd Sep 27 14:47:49 Castle sshd[2463]: Server listening on 192.168.1.229 port 22. Sep 27 14:47:49 Castle rc.sshd: SSH server daemon... Started. Sep 27 14:47:53 Castle reload_services: sshd Sep 27 14:47:53 Castle sshd[2463]: Received signal 15; terminating. Sep 27 14:47:53 Castle sshd[2932]: Server listening on 10.253.0.1 port 22. Sep 27 14:47:53 Castle sshd[2932]: Server listening on 192.168.1.229 port 22.
-
Some containers using a custom br0 network show port mappings, and some do not
Bumping this thread. Thanks
-
Error 522 intermittently
It vanished as mysteriously as it had appeared.
-
[REQUEST] Financial-freedom (MINT replacement)
https://github.com/serversideup/financial-freedom thank you!
-
Error 522 intermittently
Hello, I'm experiencing a recurring problem where all of my services display a 522 error every few minutes, and then they resume normal operation. The service does not have an issue if the IP is used instead of domain name. The only information I can find in the ngnixproxymanager logs is: "An upstream response is buffered to a temporary file." This configuration has been functioning without issues for years prior to this. castle-diagnostics-20231120-0629.zip
-
Help reading diagnostic
Thank you for your time and help Jorge & itimpi. I ordered some new power cables to try.
-
Help reading diagnostic
seems like there are still issues disk 7 seems to have read errors now but is not being shown as emulated
-
Help reading diagnostic
Hopefully last question for awhile. Can you help me find the correct firmware for the other card? I'm having trouble: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0087] (rev 05)
-
Help reading diagnostic
@JorgeB issue came back. new logs attached. Thank you
-
Help reading diagnostic
I went through all the connections to everything. It appears to be stable now. I'll follow back up if needed. Thank you @JorgeB
-
Help reading diagnostic
Hi, do I have bad cables? I started getting issues with multiple drives all at once but SMART seems to think (from what I can tell) that the drives are fine. Thank you.
-
Docker Container order - removed?
Hi, Was the ability to reorder the docker containers removed? I don't seem to be able to drag and drop them anymore. Thanks
-
Run script when specific docker starts
Thanks, that is basically what I ended up doing. Running this on a cron every few minutes to check if the docker is running and if not it starts it up and executes the commands I need. Sharing the script in case anyone else ever needs this. #!/bin/bash # Replace CONTAINER_NAME with the actual name of your running Docker container CONTAINER_NAME="CHANGEME" # Specify the log file path LOG_FILE="docker_exec_log.txt" # Check if the container is already running if docker inspect -f '{{.State.Running}}' $CONTAINER_NAME > /dev/null 2>&1; then echo "Container $CONTAINER_NAME is already running." exit 0 fi # Start the container if it's not running docker start $CONTAINER_NAME # Wait for the container to start echo "Waiting for container $CONTAINER_NAME to start..." while ! docker inspect -f '{{.State.Running}}' $CONTAINER_NAME > /dev/null 2>&1; do sleep 1 done echo "Container $CONTAINER_NAME is now running." # Run commands inside the Docker container and log errors/output docker exec $CONTAINER_NAME bash -c ' REPLACE_THIS_WITH_THE_COMMANDS_YOU_WANT_TO_RUN ' 2>&1 > $LOG_FILE # Display the log file contents cat $LOG_FILE
-
Run script when specific docker starts
Hi, Is there a way that I can trigger a script to run whenever a specific docker starts? The options in the User Scripts plugin doesn't have this usecase. Thanks
-
[Support] d8sychain - Elasticsearch
https://github.com/jemalloc/jemalloc/issues/1328 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. where is sysctl.conf ? I couldn't find it in the container.
-
issue creating new cache pool
-
issue creating new cache pool
I've formatted both nvme drives to btrfs yet unraid only detects 1 fs and it thinks its xfs: parted /dev/nvme0n1 print Model: Samsung SSD 980 1TB (nvme) Disk /dev/nvme0n1: 1000GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End Size File system Flags 1 0.00B 1000GB 1000GB btrfs parted /dev/nvme1n1 print Model: SPCC M.2 PCIe SSD (nvme) Disk /dev/nvme1n1: 1024GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End Size File system Flags 1 0.00B 1024GB 1024GB btrfs
-
[REQUEST] Mastodon
Got around to updating the script: #!/bin/bash if docker exec mastodon grep -q 5000 /app/www/app/javascript/mastodon/features/compose/components/compose_form.js && docker exec mastodon grep -q 5000 /app/www/app/validators/status_length_validator.rb; then echo "No changes needed, 5000 already present in both files." else docker exec mastodon sed -i 's/500/5000/g' /app/www/app/javascript/mastodon/features/compose/components/compose_form.js docker exec mastodon sed -i 's/500/5000/g' /app/www/app/validators/status_length_validator.rb docker exec mastodon sed -i 's/:registrations/:registrations, :max_toot_chars /g' /app/www/app/serializers/rest/instance_serializer.rb docker exec mastodon sed -i 's/private/def max_toot_chars\n 5000\n end\n\n private/g' /app/www/app/serializers/rest/instance_serializer.rb docker exec -w /app/www/app mastodon bundle exec rails assets:precompile && echo "Assets precompiled successfully." || echo "Assets precompilation failed." docker container restart mastodon fi
-
[support] kilrah/libretranslate
i think an updated image has been made available. @Kilrah would you mind updating this? thank you.
-
[Support] Gitea
has anyone been able to get this working again? I'm stuck with this: Server listening on :: port 22. Server listening on 0.0.0.0 port 22. 2023/01/12 05:43:34 cmd/web.go:106:runWeb() [I] Starting Gitea on PID: 18 2023/01/12 05:43:34 ...s/setting/setting.go:613:deprecatedSetting() [E] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.19.0 2023/01/12 05:43:34 cmd/web.go:160:runWeb() [I] Global init 2023/01/12 05:43:34 ...s/setting/setting.go:613:deprecatedSetting() [E] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.19.0 2023/01/12 05:43:34 routers/init.go:116:GlobalInitInstalled() [I] Git Version: 2.36.3, Wire Protocol Version 2 Enabled (home: /data/gitea/home) 2023/01/12 05:43:34 routers/init.go:117:GlobalInitInstalled() [I] AppPath: /usr/local/bin/gitea 2023/01/12 05:43:34 routers/init.go:118:GlobalInitInstalled() [I] AppWorkPath: /app/gitea 2023/01/12 05:43:34 routers/init.go:119:GlobalInitInstalled() [I] Custom path: /data/gitea 2023/01/12 05:43:34 routers/init.go:120:GlobalInitInstalled() [I] Log path: /data/gitea/log 2023/01/12 05:43:34 routers/init.go:121:GlobalInitInstalled() [I] Configuration file: /data/gitea/conf/app.ini 2023/01/12 05:43:34 routers/init.go:122:GlobalInitInstalled() [I] Run Mode: Prod Received signal 15; terminating.
-
[REQUEST] snikket
Snikket is a self-hosted chat service. https://snikket.org/
-
[REQUEST] Mastodon
Max_toot_length is not configurable with official mastodon. Changing max_toot_length manually isn't great because every time the docker updates, your configuration will be wiped. To get around this I created a userscript which I manually run after I update the docker. replace 5000 with whatever length you want to use. #!/bin/bash docker exec mastodon sed -i 's/500/5000/g' /app/www/app/javascript/mastodon/features/compose/components/compose_form.js docker exec mastodon sed -i 's/500/5000/g' /app/www/app/validators/status_length_validator.rb docker exec mastodon sed -i 's/:registrations/:registrations, :max_toot_chars /g' /app/www/app/serializers/rest/instance_serializer.rb docker exec mastodon sed -i 's/private/def max_toot_chars\n 5000\n end\n\n private/g' /app/www/app/serializers/rest/instance_serializer.rb docker exec -w /app/www/app mastodon bundle exec rails assets:precompile && echo "pass" || echo "fail" docker container restart mastodon At some point I'll get tired of manually running the script and will add a precheck to determine if the script should be run or not.