October 18, 2025Oct 18 I just updated my Gotify Docker container in Unraid. Now it fails to start. The docker settings in Unraid don't seem to have a "revert update" options. The log messages are below. How can i fix this? panic: error while loading plugin gotify-smtp-emailer-linux-amd64-for-gotify-v2.6.3.so: plugin.Open("data/plugins/gotify-smtp-emailer-linux-amd64-for-gotify-v2.6.3"): plugin was built with a different version of package internal/goarchgoroutine 1 [running]:github.com/gotify/server/v2/router.Create(0xc000410230, 0xc000358090, 0xc0003501a0) /src/gotify/router/router.go:93 +0x2e16main.main() /src/gotify/app.go:48 +0x27apanic: error while loading plugin gotify-smtp-emailer-linux-amd64-for-gotify-v2.6.3.so: plugin.Open("data/plugins/gotify-smtp-emailer-linux-amd64-for-gotify-v2.6.3"): plugin was built with a different version of package internal/goarchgoroutine 1 [running]:github.com/gotify/server/v2/router.Create(0xc00007b410, 0xc000358090, 0xc0003501a0) /src/gotify/router/router.go:93 +0x2e16main.main() /src/gotify/app.go:48 +0x27aStarting Gotify version 2.7.3@2025-09-21-12:13:23Loading plugin data/plugins/gotify-smtp-emailer-linux-amd64-for-gotify-v2.6.3.soStarting Gotify version 2.7.3@2025-09-21-12:13:23Loading plugin data/plugins/gotify-smtp-emailer-linux-amd64-for-gotify-v2.6.3.so
October 18, 2025Oct 18 On 10/22/2023 at 4:37 AM, Draco said: Hi Team, I figured out a workaround to get the poller up and running within this docker container. I edited this file "/etc/cont-init.d/07-svc-cron.sh" and added the below under echo "Creating LibreNMS cron artisan schedule:run" echo "Creating LibreNMS poller scheduler"echo "*/5 * * * * /opt/librenms/cronic /opt/librenms/poller-wrapper.py 16" >>${CRONTAB_PATH}/librenms Hope this helps people getting this one up and running. This doesn't seem to stick around after a reboot of the container? Assuming you exec within the container and add this line in the first place?
October 18, 2025Oct 18 3 hours ago, timg11 said:How can i fix this?Select the tag for a previous version you were running, or run them backwards if you don't know...https://hub.docker.com/r/gotify/server/tags
October 18, 2025Oct 18 1 hour ago, Kilrah said:Select the tag for a previous version you were running, or run them backwards if you don't know...https://hub.docker.com/r/gotify/server/tags@Kilrah thanks for the tip. I'm very new to docker maintenance on Unraid.I installed the Docker container in early August. On the tags page, there are quite a few tags - sorted by Newest:TAG2Last pushed 27 days by gotifyciTAG2.7Last pushed 27 days by gotifyciTAG2.7.3Last pushed 27 days by gotifyciTAGlatestLast pushed 27 days by gotifyciTAG2.7.2Last pushed about 1 month by gotifyciTAG2.7.1Last pushed about 1 month by gotifyciTAG2.6Last pushed 6 months by gotifyciSo I assume I would use TAG 2.6 since all the others are one month old, which is after I installed, and this is the first time I've attempted an update.In the Container settings, I would change the Repository: setting from "gotify/server:latest" to "gotify/server:2.6" - correct?PS Now that I realize how important it is to keep track of Docker versions to be able to roll back to last known working, I looked at my other Docker containers. Some have clear indications in the Repository: field, like "11notes/unifi:7.5.187-unraid" or "postgres:17 ". But one is ambiguous "grafana/grafana". How would I know the current tag if I needed to roll back?Edit - I went ahead and tried 2.6. Here is the update report:Pulling image: gotify/server:2.6IMAGE ID [2.6]: Pulling from gotify/server. IMAGE ID [63ce8e957633]: Pulling fs layer. Downloading 100% of 28 MB. Download complete. Extracting. Pull complete. IMAGE ID [e7def9680541]: Pulling fs layer. Downloading 100% of 93 B. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [9a1821c438b4]: Pulling fs layer. Downloading 100% of 9 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [ad316556c9ff]: Pulling fs layer. Downloading 100% of 10 MB. Verifying Checksum. Download complete. Extracting. Pull complete. Status: Downloaded newer image for gotify/server:2.6TOTAL DATA PULLED: 47 MBRemoving container: gotifySuccessfully removed container 'gotify'Command executiondocker run -d --name='gotify' --net='bridge' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="T440" -e HOST_CONTAINERNAME="gotify" -e 'GOTIFY_DEFAULTUSER_PASS'='admin' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:80]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/A75G/docker-templates/master/templates/icons/gotify.png' -p '8070:80/tcp' -v '/mnt/user/appdata/gotify/':'/app/data':'rw' -v '/mnt/user/appdata/gotify/config/':'/etc/gotify':'rw' 'gotify/server:2.6' 3d73778914e7ceb914d36cbb52c28e3f2df4622a2b8545928a1a945ef9ebadd2The command finished successfully!The Gotify container started itself and is now running again. Oddly it says "Up To Date" - maybe it only checks periodically? Thanks again for the help! Edited October 18, 2025Oct 18 by timg11
October 19, 2025Oct 19 9 hours ago, timg11 said:Oddly it says "Up To Date" - maybe it only checks periodically?No, you now selected the 2.6 tag which currently points to the same image as 2.6.3, so it'll only show an update if that 2.6 tag was ever updated e.g. if a 2.6.4 was released, probably won't happen. I.e. you'll have to manually change it again if you want to change version.Should probably read the changelogs and docs of the app, maybe config changes are required going from 2.6 to 2.7.9 hours ago, timg11 said:But one is ambiguous "grafana/grafana" How would I know the current tag if I needed to roll back?That means it's the "latest" tag. You'd know by date basically, if you keep your containers up to date with daily/weekly updates it should be pretty quick to find from the list. Edited October 19, 2025Oct 19 by Kilrah
November 6, 2025Nov 6 I just installed this container and the web gui isn't working. I don't see any errors in the container log or the system log. On first run, the container log indicated that database setup went ok. I'm very confused.
November 12, 2025Nov 12 Nothing is updated and everything is outdated ! I do not recommend it.Get the latest official version, it's much better. Edited November 12, 2025Nov 12 by Logidroid
December 2, 2025Dec 2 Hello,I'm a little bit lost with Matrix template.I starte it one time, then I made the chown, but still not starting.Saying it cannot write to the folder.I'm missing something here for sure, but I can't get what.
December 7, 2025Dec 7 Would you please make a template for this? https://github.com/ChuckPa/DBRepairI'm honestly shocked that it isn't on the CA store yet. But I need it. Thanks!
December 7, 2025Dec 7 7 hours ago, eagle470 said:I'm honestly shocked that it isn't on the CA store yet. But I need it. Thanks!It's not a Docker container, so not something you can just put in CA.
December 29, 2025Dec 29 On 7/28/2025 at 7:51 PM, Hammy Havoc said:What's the recommended way to implement MAS (Matrix Authentication Service) on Unraid if you're running this Synapse container?https://element-hq.github.io/matrix-authentication-service/index.htmlHas anyone gotten any closer to figuring this out since July?Element X is now unable to make calls because there's no LiveKit/Element Call, but can't set that up without MAS being set up.Would happily buy someone some beers if they can help me figure this out so my dad can talk to my seventy-something year-old aunt again who lives a thousand miles away in the middle of nowhere. :- )
January 20Jan 20 On 10/1/2025 at 9:22 AM, bmartino1 said:yep wiht bitani licesne owner ship and boradcom doing what they did with license bitnami redis will not be getting any more updates.https://hub.docker.com/r/bitnamilegacy/redis/tagsAs I've been monitoring this.https://www.reddit.com/r/immich/comments/1k6mo49/regarding_valkeys_redisimage/I recommend moving off bitnami reddis and into valkey open-source redshttps://valkey.io/topics/migration/Yeah. I just tried to install, and there are no images to pull in! This repo is dead, then?
January 20Jan 20 1 hour ago, ILoveBigServerICannotLie said:Yeah. I just tried to install, and there are no images to pull in! This repo is dead, then?Nope it's official valkey.. my repo adds redis password options to the unraid template.If your referring to the bitnaminredis then YES when broadcon acquired butnaminrhey puked and removed ALL bitnami docker...That said, bitnami still maintained a bare minimum legacy for some database applications for future aspirations to help previous users using their dockers to transition and migrate off to the new systems...You must use Val key moving forward
February 11Feb 11 I keep getting the following error, not sure what to do about it:socket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedsocket: Protocol not supportedTraceback (most recent call last): File "<frozen runpy>", line 198, in runmodule_as_main File "<frozen runpy>", line 88, in runcode File "/matrix/venv/lib/python3.13/site-packages/synapse/app/homeserver.py", line 505, in <module> main() ~~~~^^ File "/matrix/venv/lib/python3.13/site-packages/synapse/app/homeserver.py", line 478, in main homeserver_config = load_or_generate_config(sys.argv[1:]) File "/matrix/venv/lib/python3.13/site-packages/synapse/app/homeserver.py", line 333, in load_or_generate_config config = HomeServerConfig.load_or_generate_config( "Synapse Homeserver", argv_options ) File "/matrix/venv/lib/python3.13/site-packages/synapse/config/_base.py", line 899, in load_or_generate_config return cls.load_config(description, argv_options) ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/matrix/venv/lib/python3.13/site-packages/synapse/config/_base.py", line 595, in load_config obj, = cls.loadconfig_with_parser(config_parser, argv_options) ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/matrix/venv/lib/python3.13/site-packages/synapse/config/_base.py", line 676, in load_config_with_parser obj.parse_config_dict( ~~~~~~~~~~~~~~~~~~~~~^ config_dict, ^^^^^^^^^^^^ ...<2 lines>... allow_secrets_in_config=config_args.secrets_in_config, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/matrix/venv/lib/python3.13/site-packages/synapse/config/_base.py", line 919, in parse_config_dict self.invoke_all( ~~~~~~~~~~~~~~~^ "read_config", ^^^^^^^^^^^^^^ ...<3 lines>... allow_secrets_in_config=allow_secrets_in_config, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/matrix/venv/lib/python3.13/site-packages/synapse/config/_base.py", line 438, in invoke_all res[config_class.section] = getattr(config, func_name)(*args, **kwargs) ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/matrix/venv/lib/python3.13/site-packages/synapse/config/repository.py", line 173, in read_config self.media_store_path = self.ensure_directory( ~~~~~~~~~~~~~~~~~~~~~^ config.get("media_store_path", "media_store") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/matrix/venv/lib/python3.13/site-packages/synapse/config/_base.py", line 287, in ensure_directory os.makedirs(dir_path, exist_ok=True) ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen os>", line 228, in makedirsPermissionError: [Errno 13] Permission denied: '/media_store'
February 14Feb 14 The matrix template is a mess, all A75G repos seem to be abandoned, the user A75G hasn't returned to this forum for almost a year.
March 11Mar 11 Trying to install Element and get it accessible via a Cloudflare tunnel.It installs fine, and I was able to set it up through the Ubuntu client, however when I try to load up the Web GUI through Unraid, it errors out.I've set it up through a Cloudflare tunnel, however it errors out with a "Bad Gateway Error 502" status.Looking into the logs, it's just a repeat of ::1 - - [DATE AND TIME] "GET /config.json HTTP/1.1" 200 1898 "-" "Wget" "-"
May 5May 5 If you're having issues with the CyberChef template, a recent update broke the webui because they switched the default port to 8080 instead of 80. You just need to update your port mapping on the template to map to port 8080 and update the webUI address in the advanced section of the template to [IP]:[8080] as well.
May 6May 6 Was still on the old mpepping repo which he apparently still maintains somewhat and uses 8000 so didn't see 😅 Switched to official now Edited May 6May 6 by Kilrah
May 15May 15 Hi everyone! Having issues with db-backup over here. I have DB01 which is a PostgreSQL container and I'm getting these error messages:2026-05-15.10:36:27 [INFO] ** [db-backup01] Starting Manual Backup for db-backup01 sudo: pg_isready: command not found 2026-05-15.10:36:33 [WARN] ** [01-postgresql14__ALL] Postgres Host 'postgresql14' is not accessible, retrying.. (5 seconds so far)I'm not sure if it means accessible as in network or credentials, but neither should be an issue since I can ping the DB from the db-backup container console and credentials are correct because I use them in adminer for that DB. Followed the suggestion from another post here that added "DB01_AUTHDB" (now just "DB01_AUTH") but still same issue. Also I was able to set it up correctly in Databasus with the same host, port and credentials.I also have DB03 as a CouchDB entry and I'm getting this message:2026-05-15.10:40:14 [ERROR] ** [03-Obsidian-LiveSync-CouchDB__ALL] DB Backup of 'couch_ALL_Obsidian-LiveSync-CouchDB_20260515-104014.txt.zst' reported errorsWish I knew what errors are reported lol.I have DB05 and DB06 which are different PG and Couch DBs and they fail in the same way as 01 and 03 respectively.
June 2Jun 2 On 5/6/2026 at 6:32 PM, Kilrah said:Was still on the old mpepping repo which he apparently still maintains somewhat and uses 8000 so didn't see 😅 Switched to official nowJust installed this and had this issue, so still mapping to 80 in the template so needed to manually change it over, Edited June 2Jun 2 by brent3000
June 2Jun 2 On 6/1/2026 at 4:40 AM, roman1 said:Docker image for BackuPC was removed.https://hub.docker.com/r/tiredofit/backuppc/Dev was moving from "tiredofit" namespace to https://github.com/nfrastack/container-db-backup as of this notice on the repo "This is being migrated to the nfrastack/container-db-backup namespace - A new nfrastack release will come in April 2026" but it does seem quite abandoned. Guess we'll see if he picks it up again or if it's dead.
June 2Jun 2 2 hours ago, manuxce said:Dev was moving from "tiredofit" namespace to https://github.com/nfrastack/container-db-backupThat's a different app/container.
June 3Jun 3 Woke up to a permissions bug with redis:latest in this template today. This fixed it for me. Note the change if you need to undo it later. Set:Extra Parameters:--user 0:0 --entrypoint /bin/bashSet Post Arguments to:-lc "/opt/bitnami/scripts/redis/setup.sh && chmod 644 /opt/bitnami/redis/etc/redis.conf && exec /opt/bitnami/scripts/redis/run.sh"
June 3Jun 3 Getting this error with the latest redis image,2 hours ago, Avsynthe said:Woke up to a permissions bug with redis:latest in this template today. This fixed it for me. Note the change if you need to undo it later.Set:Extra Parameters:--user 0:0 --entrypoint /bin/bashSet Post Arguments to:-lc "/opt/bitnami/scripts/redis/setup.sh && chmod 644 /opt/bitnami/redis/etc/redis.conf && exec /opt/bitnami/scripts/redis/run.sh"I tried this but still getting this error :2026-06-03T04:05:45.727845798Z 1:C 03 Jun 2026 04:05:45.727 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it 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.2026-06-03T04:05:45.727891375Z 1:C 03 Jun 2026 04:05:45.727 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo2026-06-03T04:05:45.727920650Z 1:C 03 Jun 2026 04:05:45.727 * Redis version=8.8.0, bits=64, commit=00000000, modified=1, pid=1, just started2026-06-03T04:05:45.727929467Z 1:C 03 Jun 2026 04:05:45.727 * Configuration loaded2026-06-03T04:05:45.728192459Z 1:M 03 Jun 2026 04:05:45.728 * monotonic clock: POSIX clock_gettime2026-06-03T04:05:45.729472332Z 1:M 03 Jun 2026 04:05:45.729 * Running mode=standalone, port=6379.2026-06-03T04:05:45.729892804Z 1:M 03 Jun 2026 04:05:45.729 * Server initialized2026-06-03T04:05:45.732357157Z 1:M 03 Jun 2026 04:05:45.732 * Reading RDB base file on AOF loading...2026-06-03T04:05:45.732381003Z 1:M 03 Jun 2026 04:05:45.732 * Loading RDB produced by version 8.6.32026-06-03T04:05:45.732396713Z 1:M 03 Jun 2026 04:05:45.732 * RDB age 303392 seconds2026-06-03T04:05:45.732403826Z 1:M 03 Jun 2026 04:05:45.732 * RDB memory usage when created 7.35 Mb2026-06-03T04:05:45.732410900Z 1:M 03 Jun 2026 04:05:45.732 * RDB is base AOF2026-06-03T04:05:45.751652220Z 1:M 03 Jun 2026 04:05:45.751 * Done loading RDB, keys loaded: 113, keys expired: 0.2026-06-03T04:05:45.751697777Z 1:M 03 Jun 2026 04:05:45.751 * DB loaded from base file appendonly.aof.192.base.rdb: 0.020 seconds2026-06-03T04:05:46.147937961Z 1:M 03 Jun 2026 04:05:46.147 * DB loaded from incr file appendonly.aof.192.incr.aof: 0.396 seconds2026-06-03T04:05:46.147970884Z 1:M 03 Jun 2026 04:05:46.147 * DB loaded from append only file: 0.417 seconds2026-06-03T04:05:46.148137402Z 1:M 03 Jun 2026 04:05:46.148 # Can't open the AOF manifest file temp-appendonly.aof.manifest: Permission denied2026-06-03T04:05:45.551782795Z redis 04:05:45.55 INFO ==> Initializing Redis2026-06-03T04:05:45.578101352Z redis 04:05:45.57 INFO ==> Setting Redis config file2026-06-03T04:05:45.667297907Z redis 04:05:45.66 INFO ==> Starting Redis Any ideas how to fix this?Thank you.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.