January 6, 20251 yr On 10/22/2023 at 10: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. Hi, the fix works great, thanks for sharing - I had a problem tho, where the file im editing seems to get overwritten. This evening ive had to add the line back into the file. Did you just go into the cli and using vi or similar, edit the file?
January 16, 20251 yr I started getting an error on my Redis container "bad file format reading the append only file appendonly.aof.209.incr.aof: make a backup of your AOF file, then use ./redis-check-aof --fix <filename.manifest>". This container immediately fails so I can't start it and then run the command to fix it. I need to run "./redis-check-aof --fix appendonly.aof.209.incr.aof" but I need the container to start up first to do so. Any advice?
January 20, 20251 yr On 1/4/2025 at 6:20 PM, Fiala06 said: I'm having trouble with LibreNMS. Anyone find a fix for the scheduler? The command doesn't work inside the container. you need to goto the cli of the docker container, and edit this file with vi or similar "/etc/cont-init.d/07-svc-cron.sh" add the below under existing section called 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 Once you've added this, you need to stop/start the docker container, and then wait about 10/15 mins, then run validate again, and you should be running
January 31, 20251 yr On 9/1/2020 at 8:04 PM, mkono87 said: I myself seem to connect to the flarum db but I get a basic webpage that states Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error. Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error. Howdy! Did you ever find a solution to this? I can't seem to find a solution to this, so here I am. I've searched all over and the error I'm getting right after install is "Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error." Apparently that's a pretty common issue, but I can't find any that are experiencing that issue specifically in regard to the Unraid docker container. This container is the only one on the Unraid Community Apps, so I can't really test it against another, but I can't seem to get past the whole "Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error." error. Here's what I've tried so far: 1. php flarum cache:clear 2. php flare migrate 3. No errors in /var/log/nginx/error.log 4. /storage/logs_ is empty 5. The container is talking to MariaDB Yet, I'm still stuck at Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error." Any ideas? Thanks! edit: Scratch all this. After messing around with it for an hour more last night, I gave up. I started fiddling around again with it today and got everything working! Edited February 1, 20251 yr by eightysixed Issue Resolved.
February 4, 20251 yr Hey! I think this is the correct topic for the kiwix-serve, right? I'm confused – Where are the files for kiwix actually at? I see one path in the container when setting it up, 'Appdata', which sits in '/mnt/user/appdata/kiwix-serve/'. There's also the Download variable, which has the URL for a vim file. I thought that the appdata folder would contain all the files that kiwix needed to run the webserver, etc., but when I start the container the only thing in there is the zim file which has been downloaded. I had actually added another path to the container, where I had intended to keep the zim files, separate from the appdata folder.
February 4, 20251 yr 1 hour ago, emsixteen said: I had actually added another path to the container, where I had intended to keep the zim files, separate from the appdata folder. The appdata folder is for the zim files, there's nothing else it needs to store persistently.
February 4, 20251 yr Where are the files for and which run the kiwix itself, the web server n' that? Where is that running from? It feels wrong to me to keep the zim files in the appdata folder, 100GB+ files shouldn't be in there imo and I believe there should be a separation of concerns. I do have it working as-is and appreciate that it was very easy to get set-up, but my questions are still there.
February 4, 20251 yr 3 minutes ago, emsixteen said: Where are the files for and which run the kiwix itself, the web server n' that? Where is that running from? It feels wrong to me to keep the zim files in the appdata folder, 100GB+ files shouldn't be in there imo and I believe there should be a separation of concerns. I do have it working as-is and appreciate that it was very easy to get set-up, but my questions are still there. you can change the path from "/mnt/user/appdata/kiwix-serve/" to where you want to store the files For example /mnt/user/SHARE/data/kiwix/ or something The container itself is stored under "/mnt/user/system/docker", probably, most likely. As all docker images are.
February 9, 20251 yr On 2/4/2025 at 4:02 AM, Mainfrezzer said: you can change the path from "/mnt/user/appdata/kiwix-serve/" to where you want to store the files For example /mnt/user/SHARE/data/kiwix/ or something The container itself is stored under "/mnt/user/system/docker", probably, most likely. As all docker images are. Wouldn't that also put the docker's appdata in the /mnt/user data share as well? If possible would like to see it behaves the same as the *arr apps where appdata and data are separate folders.
February 10, 20251 yr i thought it just contained just "zim files" as it was stated above. if there are any non zim files and they are in the same folder, its a bit tricky. But if the settings are in some subfolder, you can map the container path /data/THEFOLDER to /mnt/user/appdata/kiwix-serve, while having the whole /data mapped to the array Edit: Or the other way around, if the zim files are in a subfolder in data. /data/ZIMFOLDER to /mnt/user/SHARE/ while having /data mapped to /mnt/user/appdata/kiwix-serve Edit Edit: yes, as suspected. there is no other data. This is a "dumb" program that scans the folder for zim files, theres nothing that needs to be saved seperately. its just the zim files. Edited February 10, 20251 yr by Mainfrezzer
February 15, 20251 yr Hey I hope you can help with Mattermost container please. It's out of date to the point the mobile client won't connect anymore, says the server is too old and insecure. Can you please update the Mattermost container to the latest? Thanks Daniel
February 15, 20251 yr On 8/6/2024 at 2:07 AM, TwistedDrum5 said: For the mattermost container, there needs to be an update to the template: First off, they are moving away from mysql and pushing their users to use postgres, so it would be wise to mention this, and have the default first setup be postgres. Second the template for DATASOURCE is formatted for mysql: MM_USERNAME:MM_PASSWORD@tcp(DB_HOST:DB_PORT_NUMBER)/MM_DBNAME?charset=utf8mb4,utf8&readTimeout=30s&writeTimeout=30s and there is one hidden field under "show more settings" where you select the driver, which is defaulted to mysql. It would be helpful to default to postgres driver and postgres format for the DATASOURCE postgres://MM_USERNAME:MM_PASSWORD@DB_HOST:DB_PORT_NUMBER/MM_DBNAME?sslmode=disable&connect_timeout=10 Let me know if you need anything from me, but troubleshooting this took a long time and there wasn't a lot of info out there, so I think this would be helpful. I managed to get around the database issue using chatgpt for help. I now connecto to Postgres databse and everything works. Published through NGINX all good. Now when using mobile client I get warnings about how old and insecure / out of date the server is. Is it possible to just change repos or something and pull down a new version? I'm not a huge docker expert. I suspect there is a template that makes the docker more compatible with Unraid so I fear this is not the case and we are reliant on the publisher to update. I hope they do it soon.
February 24, 20251 yr Hi. I have installed leantime with the CA template. Everything seems to be ok but can't get to installation page and here is how the log for the container looks: I don't think I'm doing anything wrong in the template: any suggestions on what could be wrong?
March 4, 20251 yr Matrix Server. What is the best way to go about being able to edit the config files? I know it is a permissions issue since 991 is applied, but I'm unable to edit the files unless I'm signed into console as root and nano into the file. I can't edit them or copy them to my local pc or view them in something like codeserver. Thank you for any tips on this.
March 10, 20251 yr Does anyone else have problems with the librenms container not shutting down? I've gotten everything working correctly and I'm even using the librenms dispatch. Polling, validation, everything is green and working, except when I try to stop the container. Logs show the container seeing the shutdown requests but it just doesn't shut down. This is only an issue with librenms/librenms:latest. All other docker containers are good. 2025/03/10 09:44:17 [notice] 626#626: signal 15 (SIGTERM) received from 617, exiting [10-Mar-2025 09:44:17] NOTICE: Terminating ... 2025/03/10 09:44:17 [notice] 657#657: exiting 2025/03/10 09:44:17 [notice] 658#658: exiting 2025/03/10 09:44:17 [notice] 659#659: exiting 2025/03/10 09:44:17 [notice] 725#725: exiting 2025/03/10 09:44:17 [notice] 676#676: exiting 2025/03/10 09:44:17 [notice] 662#662: exiting 2025/03/10 09:44:17 [notice] 814#814: exiting 2025/03/10 09:44:17 [notice] 664#664: exiting 2025/03/10 09:44:17 [notice] 700#700: exiting 2025/03/10 09:44:17 [notice] 757#757: exiting 2025/03/10 09:44:17 [notice] 787#787: exiting 2025/03/10 09:44:17 [notice] 844#844: exiting 2025/03/10 09:44:17 [notice] 890#890: exiting 2025/03/10 09:44:17 [notice] 919#919: exiting 2025/03/10 09:44:17 [notice] 953#953: exiting 2025/03/10 09:44:17 [notice] 987#987: exiting 2025/03/10 09:44:17 [notice] 657#657: exit 2025/03/10 09:44:17 [notice] 658#658: exit [10-Mar-2025 09:44:17] NOTICE: exiting, bye-bye! 2025/03/10 09:44:17 [notice] 814#814: exit 2025/03/10 09:44:17 [notice] 787#787: exit 2025/03/10 09:44:17 [notice] 659#659: exit 2025/03/10 09:44:17 [notice] 725#725: exit 2025/03/10 09:44:17 [notice] 676#676: exit 2025/03/10 09:44:17 [notice] 953#953: exit 2025/03/10 09:44:17 [notice] 664#664: exit 2025/03/10 09:44:17 [notice] 700#700: exit 2025/03/10 09:44:17 [notice] 919#919: exit 2025/03/10 09:44:17 [notice] 844#844: exit 2025/03/10 09:44:17 [notice] 757#757: exit 2025/03/10 09:44:17 [notice] 662#662: exit 2025/03/10 09:44:17 [notice] 890#890: exit 2025/03/10 09:44:17 [notice] 987#987: exit 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 664 2025/03/10 09:44:17 [notice] 626#626: worker process 664 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 757 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 787 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 919 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 919 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 814 2025/03/10 09:44:17 [notice] 626#626: worker process 814 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 657 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 657 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 658 2025/03/10 09:44:17 [notice] 626#626: worker process 658 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 725 2025/03/10 09:44:17 [notice] 626#626: worker process 725 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 953 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 953 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 700 2025/03/10 09:44:17 [notice] 626#626: worker process 700 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: worker process 662 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 662 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 844 2025/03/10 09:44:17 [notice] 626#626: worker process 844 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 890 2025/03/10 09:44:17 [notice] 626#626: worker process 890 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 987 2025/03/10 09:44:17 [notice] 626#626: worker process 987 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 676 2025/03/10 09:44:17 [notice] 626#626: worker process 676 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: signal 29 (SIGIO) received 2025/03/10 09:44:17 [notice] 626#626: signal 17 (SIGCHLD) received from 659 2025/03/10 09:44:17 [notice] 626#626: worker process 659 exited with code 0 2025/03/10 09:44:17 [notice] 626#626: exit crond: USER librenms pid 1314 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1317 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1320 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1323 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1326 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1329 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1332 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1335 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1338 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1341 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1344 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1347 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1350 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1353 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1 crond: USER librenms pid 1356 cmd php /opt/librenms/artisan schedule:run --no-ansi --no-interaction > /dev/null 2>&1
March 11, 20251 yr On 2/15/2025 at 6:41 AM, dmarti3 said: I managed to get around the database issue using chatgpt for help. I now connecto to Postgres databse and everything works. Published through NGINX all good. Now when using mobile client I get warnings about how old and insecure / out of date the server is. Is it possible to just change repos or something and pull down a new version? I'm not a huge docker expert. I suspect there is a template that makes the docker more compatible with Unraid so I fear this is not the case and we are reliant on the publisher to update. I hope they do it soon. To get the latest version I changed the repository to mattermost/mattermost-team-edition:latest
March 13, 20251 yr The Keycloak template is outdated ever since keycloak rolled out their hostname v2. Here are the correct variables to get it working correctly: Port KEYCLOAK_ADMIN_USER (temporary first username to login and do first time setup) KEYCLOAK_ADMIN_PASSWORD (temporary first password to login and do first time setup) KEYCLOAK_DATABASE_HOST (Postgres Hostname if on same docker network, or IP if not) KEYCLOAK_DATABASE_PORT (Postgres container port 5432 if on same docker network, or public port if not) KEYCLOAK_DATABASE_USER (Postgres username) KEYCLOAK_DATABASE_PASSWORD (Postgres password) KEYCLOAK_DATABASE_NAME (Postgres DB name - i.e. "keycloak") KEYCLOAK_EXTRA_ARGS (leave blank) KEYCLOAK_PROXY_HEADERS (set to "xforwarded" if using a reverse proxy like Nginx) KEYCLOAK_HOSTNAME_ADMIN (URL for admin access, you can have this be the same as hostname if you want to have web access to Keycloak admin portal, or you can set to something else if you want to keep it local) KEYCLOAK_HOSTNAME (i.e. "auth.example.com") KEYCLOAK_PRODUCTION (Set to "true" if you want to run in production mode, which you do, or "false" for development mode) The old template fields of "HTTPS Strict" and "HTTP Enabled", and "KC_Proxy" have been deprecated.
March 19, 20251 yr Trying to run db-backup. My MSSQL Server is in another docker container in Unraid. I get this: 2025-03-19.19:07:13 [NOTICE] ** [01-192.168.100.100__master] Dumping MSSQL database: 'master' cat: /tmp/backups/01_dbbackup.UqyLvH/mssql_master_192.168.100.100_20250319-190713.bak: No such file or directory 2025-03-19.19:07:17 [INFO] ** [01-192.168.100.100__master] DB Backup of 'mssql_master_192.168.100.100_20250319-190713.bak' completed successfully stat: cannot statx '/tmp/backups/01_dbbackup.UqyLvH/mssql_master_192.168.100.100_20250319-190713.bak': No such file or directory date: /tmp/backups/01_dbbackup.UqyLvH/mssql_master_192.168.100.100_20250319-190713.bak: No such file or directory stat: cannot statx '/tmp/backups/01_dbbackup.UqyLvH/mssql_master_192.168.100.100_20250319-190713.bak': No such file or directory 2025-03-19.19:07:17 [NOTICE] ** [01-192.168.100.100__master] Backup of 'mssql_master_192.168.100.100_20250319-190713.bak' created with the size of bytes chmod: cannot access '/tmp/backups/01_dbbackup.UqyLvH/mssql_master_192.168.100.100_20250319-190713.bak': No such file or directory mv: cannot stat '/tmp/backups/01_dbbackup.UqyLvH/mssql_master_192.168.100.100_20250319-190713.bak': No such file or directory 2025-03-19.19:07:17 [ERROR] ** [01-192.168.100.100__master] Moving of backup 'mssql_master_192.168.100.100_20250319-190713.bak' reported errors 2025-03-19.19:07:17 [NOTICE] ** [01-192.168.100.100__master] DB Backup for 'master' time taken: Hours: 0 Minutes: 00 Seconds: 04 2025-03-19.19:07:17 [ERROR] ** [01-192.168.100.100__master] Skipping Cleaning up old backups because there were errors in backing up 2025-03-19.19:07:17 [INFO] ** [01-192.168.100.100__master] Backup 01 routines finish time: 2025-03-19 19:07:17 CET with exit code 0 2025-03-19.19:07:17 [NOTICE] ** [01-192.168.100.100__master] Backup 01 routines time taken: Hours: 0 Minutes: 00 Seconds: 04 2025-03-19.19:07:17 [NOTICE] ** [01-192.168.100.100__master] Sleeping for another 3596 seconds. Waking up at 2025-03-19 20:07:13 CET 2025-03-19.20:07:13 [NOTICE] ** [01-192.168.100.100__master] Dumping MSSQL database: 'master' 2025-03-19.20:07:16 [INFO] ** [01-192.168.100.100__master] DB Backup of 'mssql_master_192.168.100.100_20250319-200713.bak' completed successfully 2025-03-19.20:07:16 [NOTICE] ** [01-192.168.100.100__master] Backup of 'mssql_master_192.168.100.100_20250319-200713.bak' created with the size of bytes 2025-03-19.20:07:16 [ERROR] ** [01-192.168.100.100__master] Moving of backup 'mssql_master_192.168.100.100_20250319-200713.bak' reported errors 2025-03-19.20:07:16 [NOTICE] ** [01-192.168.100.100__master] DB Backup for 'master' time taken: Hours: 0 Minutes: 00 Seconds: 03 2025-03-19.20:07:16 [ERROR] ** [01-192.168.100.100__master] Skipping Cleaning up old backups because there were errors in backing up 2025-03-19.20:07:16 [INFO] ** [01-192.168.100.100__master] Backup 01 routines finish time: 2025-03-19 20:07:16 CET with exit code 0 2025-03-19.20:07:16 [NOTICE] ** [01-192.168.100.100__master] Backup 01 routines time taken: Hours: 0 Minutes: 00 Seconds: 03 2025-03-19.20:07:16 [NOTICE] ** [01-192.168.100.100__master] Sleeping for another 3597 seconds. Waking up at 2025-03-19 21:07:13 CET When I check the tmp folder in the mssql docker it works, the backup is created but the db-backup can't access this it seems. Any ideas? Edited March 19, 20251 yr by Wojciech
April 1, 20251 yr On 2/24/2025 at 8:41 PM, rodmendoza said: Hi. I have installed leantime with the CA template. Everything seems to be ok but can't get to installation page and here is how the log for the container looks: I don't think I'm doing anything wrong in the template: any suggestions on what could be wrong? I am having the same issue. The configuration is not being written as the sample.env does not contain the database configuration. Checking the logs, on my install I see failed to connect to DB and the host IP is the IP of the container not the maria db IP that I put in. So this container is broken. Hopefully @A75G can fix it, otherwise it should be pulled out of the app store in my opinion.
April 3, 20251 yr Author On 4/1/2025 at 10:30 PM, nerbonne said: I am having the same issue. The configuration is not being written as the sample.env does not contain the database configuration. Checking the logs, on my install I see failed to connect to DB and the host IP is the IP of the container not the maria db IP that I put in. So this container is broken. Hopefully @A75G can fix it, otherwise it should be pulled out of the app store in my opinion. Updated https://github.com/A75G/docker-templates/commit/d10779ac63b21bf18f1b295249d9d04566c08915
April 3, 20251 yr Author On 3/13/2025 at 8:19 PM, DebrodeD said: The Keycloak template is outdated ever since keycloak rolled out their hostname v2. Here are the correct variables to get it working correctly: Port KEYCLOAK_ADMIN_USER (temporary first username to login and do first time setup) KEYCLOAK_ADMIN_PASSWORD (temporary first password to login and do first time setup) KEYCLOAK_DATABASE_HOST (Postgres Hostname if on same docker network, or IP if not) KEYCLOAK_DATABASE_PORT (Postgres container port 5432 if on same docker network, or public port if not) KEYCLOAK_DATABASE_USER (Postgres username) KEYCLOAK_DATABASE_PASSWORD (Postgres password) KEYCLOAK_DATABASE_NAME (Postgres DB name - i.e. "keycloak") KEYCLOAK_EXTRA_ARGS (leave blank) KEYCLOAK_PROXY_HEADERS (set to "xforwarded" if using a reverse proxy like Nginx) KEYCLOAK_HOSTNAME_ADMIN (URL for admin access, you can have this be the same as hostname if you want to have web access to Keycloak admin portal, or you can set to something else if you want to keep it local) KEYCLOAK_HOSTNAME (i.e. "auth.example.com") KEYCLOAK_PRODUCTION (Set to "true" if you want to run in production mode, which you do, or "false" for development mode) The old template fields of "HTTPS Strict" and "HTTP Enabled", and "KC_Proxy" have been deprecated. updated https://github.com/A75G/docker-templates/commit/856549a905699e0569581a95d905f29b074b982d
April 3, 20251 yr Author On 2/15/2025 at 3:35 PM, dmarti3 said: Hey I hope you can help with Mattermost container please. It's out of date to the point the mobile client won't connect anymore, says the server is too old and insecure. Can you please update the Mattermost container to the latest? Thanks Daniel Updated https://github.com/A75G/docker-templates/commit/4ea2db17bad754092c73cd9d0459b801382d3d1e
April 3, 20251 yr 3 hours ago, A75G said: Updated https://github.com/A75G/docker-templates/commit/d10779ac63b21bf18f1b295249d9d04566c08915 I updated but still having the same issue. The error log shows the container trying to connect to the container IP for the DB. Container error log: PDOException: SQLSTATE[HY000] [1045] Access denied for user 'leantime'@'10. 10.11.71' (using password: YES) in /var/www/html/vendor/laravel/framework/s rc/Illuminate/Database/Connectors/Connector.php:66 Docker run command: docker run -d --name='gda-leantime-container-nas0' --net='br0' --ip='10.10.11.71' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="ISOT0" -e HOST_CONTAINERNAME="gda-leantime-container-nas0" -e 'TCP_PORT_80'='8000' -e 'LEAN_DB_HOST'='10.10.11.76' -e 'LEAN_DB_USER'='leantime' -e 'LEAN_DB_PASSWORD'='leantimepass' -e 'LEAN_DB_DATABASE'='leantimedb' -e 'LEAN_APP_URL'='http://10.10.11.71:8000' -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/leantime.png' 'leantime/leantime:latest' 8d02a7103a388ec2e48e81a1b40d272e29906fec1eeb8a01e6389190c5759ba5 The command finished successfully!
April 3, 20251 yr Author 3 hours ago, nerbonne said: I updated but still having the same issue. The error log shows the container trying to connect to the container IP for the DB. Container error log: PDOException: SQLSTATE[HY000] [1045] Access denied for user 'leantime'@'10. 10.11.71' (using password: YES) in /var/www/html/vendor/laravel/framework/s rc/Illuminate/Database/Connectors/Connector.php:66 Docker run command: docker run -d --name='gda-leantime-container-nas0' --net='br0' --ip='10.10.11.71' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="ISOT0" -e HOST_CONTAINERNAME="gda-leantime-container-nas0" -e 'TCP_PORT_80'='8000' -e 'LEAN_DB_HOST'='10.10.11.76' -e 'LEAN_DB_USER'='leantime' -e 'LEAN_DB_PASSWORD'='leantimepass' -e 'LEAN_DB_DATABASE'='leantimedb' -e 'LEAN_APP_URL'='http://10.10.11.71:8000' -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/leantime.png' 'leantime/leantime:latest' 8d02a7103a388ec2e48e81a1b40d272e29906fec1eeb8a01e6389190c5759ba5 The command finished successfully! I just double checked everything from the start it directly got working. This appear to be database issue please create new user with full access to a new database.
April 4, 20251 yr Can someone help with weechat? I installe it, ran the mnt commands, attached the docker to the terminal and... then? Trying to connect to a server gets me the error "you cannot write text in this buffer" so I'm not sure where to go from here...
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.