TekDRu

Members
  • Posts

    89
  • Joined

  • Last visited

Everything posted by TekDRu

  1. Getting log errors and not sure how to fix. rename(/ext_logs/nextcloud_logs/nextcloud.log,/ext_logs/nextcloud_logs/nextcloud.log.1): Permission denied at /app/www/public/lib/public/Log/RotationTrait.php#51 This is the setting in my config: 'loglevel' => 2, 'logfile' => '/ext_logs/nextcloud_logs/nextcloud.log', 'logfile_audit' => '/ext_logs/nextcloud_logs/audit.log', Any help is greatly appreciated. Thanks
  2. Hey @TekWarren, the setup and screenshot shared on this post still works well for me. You can use it as a guide for the paths.
  3. Discovered a solution to updating the container without issue. Adding variables for "DB_PREFIX" and "APP_INSTALLED=true" did the trick for me. Got some help from these posts: https://github.com/akaunting/docker/issues/61#issuecomment-1143664641 https://github.com/akaunting/docker/issues/107 For the DB_PREFIX variable, you will need to use the first 4 characters seen in your specific existing database tables names. I would advice backing up your database and appdata before making these edits.
  4. Hey @marlouiegene18 can you share screenshot of settings, docker run or config?
  5. hey @K1LLA_KING_KING, can you share a screenshot of your container or the docker run command to see If I notice any issues with the settings.
  6. Did you already run the "php artisan install" script?
  7. Thanks @xanatos. After changing my password to just alpha numeric and tried again, I was successful in getting the new unifi controller up and running. Thanks for the tip. Hope it helps others who may have this issue.
  8. Thanks @xanatos. I double checked my password but there are no "@" symbols. There are some other characters that may be an issue so I will try recreating the container and try again later this evening/week.
  9. hi @wgstarks, I tried following your steps but could not get it to work. Unifi Network Controller: This is what I get if I go to web URL for UNA: HTTP Status 404 – Not Found Logs for UNA: [custom-init] No custom files found, skipping... Docker Run: docker run -d --name='unifi-network-application' --net='mongonet' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="unifi-network-application" -e 'MONGO_USER'='unifi' -e 'MONGO_PASS'='********************' -e 'MONGO_HOST'='mongodb' -e 'MONGO_PORT'='27017' -e 'MONGO_DBNAME'='unifi' -e 'MEM_LIMIT'='4024' -e 'MEM_STARTUP'='1024' -e 'MONGO_TLS'='' -e 'MONGO_AUTHSOURCE'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/unifi-network-application-icon.png' -p '8446:8443/tcp' -p '3478:3478/udp' -p '10001:10001/udp' -p '8082:8080/tcp' -p '1900:1900/udp' -p '8843:8843/tcp' -p '8880:8880/tcp' -p '6789:6789/tcp' -p '5514:5514/udp' -v '/mnt/user/appdata/unifi-network-application':'/config':'rw' 'lscr.io/linuxserver/unifi-network-application' Mongo DB: This is what I get when I go to the web URL for mongodb: It looks like you are trying to access MongoDB over HTTP on the native driver port. Docker Run: docker run -d --name='MongoDB' --net='mongonet' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="MongoDB" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/jason-bean/docker-templates/master/jasonbean-repo/mongo.sh-600x600.png' -p '27017:27017/tcp' -v '/mnt/user/appdata/mongodb/db-data/':'/data/db':'rw' -v '/mnt/user/appdata/mongodb/mongo-init/init-mongo.js':'/docker-entrypoint-initdb.d/init-mongo.js':'ro' 'mongo:7.0-rc' Can you help figure out what I'm missing or doing wrong? Thanks
  10. I can't get VM to start. Seeing this error in libvert log: 2023-10-09 04:00:26.944+0000: 20881: error : virNetDevSendEthtoolIoctl:3039 : ethtool ioctl error on vethed387a7: No such device Diagnostics attached. Thanks tower-diagnostics-20231108-1826.zip
  11. solved this by changing port number.
  12. Thanks @gremlica. Did you get the execution error when you first updated to 6.12.3? If so, what did you do to resolve the error? I'm trying to find a solution for the execution error I have been getting. I may try again tonight or next weekend.
  13. Hi @gremlica, Are you using invoice ninja with Unraid 6.12.4? I am using the container from @Mihai and it was working fine on Unraid 6.11.5, but after updating to 6.12.3 or 6.12.4, I get an execution error.
  14. Hello @Mihai, After I updated Unraid to version 6.12.3 I realized the invoiceninja is not starting. I get an "execution error" "server error" whenever I try to start the container. If I try to pull the container again, I get the following error: docker: Error response from daemon: driver failed programming external connectivity on endpoint invoiceninja-v5 (e23929c8306f014445db778e1d5f00d6064fad93a957c18c6d6b0f2bf4e86424): Error starting userland proxy: listen tcp4 0.0.0.0:8443: bind: address already in use. Please help
  15. Hey @taifleh, @b0m541 and @knex666, I'm interested in trying mopidy3. but from going through these posts, I'm not sure if its working properly. Can you let me know if any of you have mopidy3 working well with these extensions: Mopidy-Iris Mopidy-Muse Mopidy-SomaFM Mopidy-SoundCloud Mopidy-Tunein Mopidy-Jellyfin Mopidy-Youtube Thanks
  16. The container Setup Account should be set to false. Make that change and run the php artisan install command again and see if that gets you to the setup wizard. Is the screenshot from portainer? I haven't used portainer before so I can't help there. I've only used the docker with mariadb and use adminer to access my databases.
  17. What errors or problems are you running into? I am using the app. I do not apply any updates to the container to avoid breaking it. I was able to update to 3.0.12 from within the app itself. If and when I decide to update the container, there is a process I go through to restore my existing database and avoid loosing everything. Below is a quick list of steps from memory. I can give more detail if needed. Backup the current database before making container updates Apply container updates and go through install process from scratch (with php artisan install commands etc.) until I have a running app Open the backed-up sql file in a text editor, and change the first three initials of all tables in to match the first three letters in new table names from new database Delete all tables from new database Import sql file from existing database (with new table names) to replace the new database
  18. Hey @Domotics, just wanted to come back and say thanks for this. It solved my problem after an update to nextcloud 25. I don't know what happened but it seems like my config file got overwritten after the update and the log file was saved to the array again. I think this fix should work for future updates. Thanks!
  19. @blue8lucian Does the email and the password that you used in the php command match what you have in your container settings?
  20. Yeah. It's best to turn off auto updates, and don't apply any updates for now. I realize that it breaks after each update.
  21. @blue8lucian you can find some help here:
  22. @dredgeon Can you take a look at my screenshot and let me know what I have wrong.
  23. @dredgeon did you have to run the setup wizard after your changes? I tried adding the new variables for DB_PORT and DB_NAME but now I can't log in anymore.
  24. That makes sense. I see that the php artisan install code defines the host ip and port separately. I'll give that a try and then run a pending update to see if it breaks after the update. Thanks!