Vaseer

Members
  • Content Count

    102
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Vaseer

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. I had the same problem. My solution was manual upgrade to version 18.0.13 (from 17.0.x). I did as described in first post of this thread, option 3. Manual upgrade using occ. All commands are the same, except docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest.tar.bz2 -P /config must be replaced with docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest-18.tar.bz2 -P /config Reason for this is that you can't skip major versions (i.e. if your Nextcloud instance is on version 17.x, you must first
  2. I didn't get any information (searched unRAID forum and Googled it) to answer this question so I am asking again and adding some new test results. Uploading ~5GB test file to Nextcloud over local network: Before upload: Couple seconds after finished upload: Is this normal/correct way of uploading files to Nextcloud? NC container mappings: /data <--> /mnt/disks/nextcloud/nextcloud-data/ /config <--> /mnt/cache/docker/appdata/nextcloud unRAID version: 6.6.6 Edit: Found it! This only h
  3. I have mappings for all containers configured and this happens when I upload ~5 GB file to Nextcloud: Before upload: Seconds after finished upload: After 10-20 seconds values return to same state as before upload. Is this container specific (if so, I will ask in NC thread) or could be something wrong with my docker configuration? My unRAID version is 6.6.6
  4. To clarify question: I am using Transmission container, which is using mapped volume /downloads <--> /mnt/disks/downloads for transferred data. docker.img is on SSD cache drive, /mnt/disks/downloads is unassigned HDD. In Transmission I see cumulative DL/UL data size of ~10 TB, which, if my calculations are correct, corresponds to cache SSD S.M.A.R.T. attribute "246 Total host sector write" which is 21877021800. SSD Sector sizes: 512 bytes logical, 4096 bytes physical. In addition to Transmission's data I also saw docker.img size increase when I uploaded some large files (
  5. Got so used to docker-shell command, that I totally forgot it is not build in to unRAID as default command 😀 I recommend watching Spaceinvader One tutorial, where he explains how to get and enable command.
  6. This still works. Instead of docker exec -it nextcloud bash you can use command docker-shell and you will get list of all Docker containers. Press corresponding number next to Nextcloud Docker and you will access Nextcloud shell. All other commands are still the same for this version of NC.
  7. Today I was uploading some files to my Nextcloud and one of them was 6 GB of size. When I was uploading this file, I got email notice from unRAID server "Docker image disk utilization of 72%". When the upload finished, I got new email notice: "Docker image disk utilization returned to normal level". This made me curious of how does file transfer or rather file write to Nextcloud storage works? I always thought that files are written directly to Nextcloud HDDs. But it seems that files are initially stored to Nextcloud Docker instance which is on cache SDD and then written to Nex
  8. I did WebUI upgrade from 16.0.1 to 17.0.1 and got same error as @T0a and @PSYCHOPATHiO. My solution was manual upgrade as described in this post. Nextcloud is now upgraded to version 17.0.1 and working. Edit: typo
  9. I have set transcoding temporary path to /ramtranscode (mapping it to /tmp in docker config), restarted the Emby docker and Kodi client but the problem still persists. I have changed one of the users' Vero 4K configuration to use Emby in native mode (not add-on) and all video files are working fine. Was reading around and got information, that transcoding is done only when Emby add-on on client (Vero, Kodi) send information to server, that it can not play original file. Most of "problematic" files are in MKV HEVC format. The most interesting part is that in native mode (with or
  10. Transcoding is done on Kodi clients and all have same problem. Clients are: Vero 4K, Windows 10 PC (Ryzen 3 2200G), Ubuntu PC (i7 gen 3, with Nvidia GPU)...
  11. I am having problems with playback via Emby. In random time intervals (5 to 10 minutes) video stutters and then video and sound jumps back for about 30 seconds and keeps playing. Subtitles are displaying as nothing has happened and are not matching video anymore. This is not with all videos but just some of them (random), mostly movies (TV shows are OK - for now). If I restart video from beginning the problem keeps repeating but always in different time interval. Playback is done via Kodi on different devices (Vero, Chromebox, Windows PC, Ubuntu PC). Devices were on different Kodi versions
  12. I would like change SSL certificate for HTTPS WebUI and use my own certificate. Certificate is issued by self-signed CA (not Let's Encrypt cert). I am fairly sure that sometimes ago I read that SSL certifiacte can be changed. But I don't remember procedure how to do it, or where I read it and at this moment I can't find any instructions how to do it. How do I change SSL certificate? unRAID version: 6.6.6 Thanks
  13. Transmission, Extra Parameters not applied to container. I am trying to set Extra Parameters --dns=208.67.222.222 and when I hit Save or Apply I get response: Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='transmission' --net='br0' --ip='10.0.0.32' -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e 'TCP_PORT_9091'='9091' -e 'TCP_PORT_51413'='51413' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/disks/downloads/':'/downloads':'rw,slave' -v '/mnt/disks/downloads/transmission-watch/':'/watch':'rw,slave' -v '/mnt/cache/docker/appdata/Transmis
  14. Well... the most obvious things are the easiest to miss for me... Thanks for the info.