Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Hogwind

Members
  • Joined

  • Last visited

Everything posted by Hogwind

  1. Yes, the error message is correct. Both Radarr and Deluge need to have the same container path for downloads. Now Radarr have /downloads and Deluge have /data/completed. You have two options, either you change the container path for Deluge downloads to /downloads or you change Radarr container path from /downloads to /data/completed.
  2. Did you change the path in the docker template? What is the path for all your movies in the Movie Editor?
  3. Follow this guide https://www.youtube.com/watch?v=HLcj-p-lcXY
  4. We seem to have similar problems. I solved my problems with an uninstallation of Bitwarden, also deleted the folder in appdata. And after that I installed it again with the same settings. Now everything works like a charm.
  5. I have the exact same problem as BrunoVic. The date/time is correct. The Bitwarden dockerlogs tells me this: [WARNING] The following environment variables are being overriden by the config file, [WARNING] please use the admin panel to make changes to them: [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN [2020-03-20 09:00:11][ws][INFO] Listening for new connections on 0.0.0.0:3012. [2020-03-20 09:00:11][start][INFO] Rocket has launched from http://0.0.0.0:80 I have followed the guide that Spaceinvader One posted on youtube and used a xxx.duckdns.org domain. Is the letsencrypt config correct? resolver 127.0.0.11 valid=30s; upstream bitwarden { server bitwardenrs:80; } server { listen 443 ssl; server_name xxx.duckdns.org; include /config/nginx/ssl.conf; client_max_body_size 128M; location / { proxy_pass http://bitwarden; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } location /notifications/hub { proxy_pass http://bitwarden; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /notifications/hub/negotiate { proxy_pass http://bitwarden; } }
  6. Thanks, works like a charm. :)
  7. system.method.set_key has stopped working, is there a new parameter I can use instead? EDIT: Is there an easy way to roll back to rtorrent/0.9.6/0.13.6 ?
  8. Thanks, I'll try that. :)
  9. Okay, can anybody help me with the settings? So that the dockers only update when the backup is running or manually? I don't want the docker to update on a separate schedule.
  10. My unRaid just ran an scheduled backup, and it didn't update the dockers. I have the CA Auto Update Applications installed. Is there any specific settings that has to be checked other then "Update Applications On Restart? Yes"? EDIT: I found this line in the log: Oct 17 10:06:23 Tower Docker Auto Update: No settings file found Which leads to the question, do I manually create this setting file or does it get created when the correct settings is done?
  11. I just added port 2203 and now it works. By the looks of it you have to have two ports mapped 2202 and 2203. I noticed this in the sys log also: Fix Common Problems: Error: Docker Application ubooquity, Container Port 2203 not found or changed on installed application https://hub.docker.com/r/linuxserver/ubooquity/ tells you: -p 2202 - the library port -p 2203 - the admin port
  12. I find this in my log from time to time, should I ignore or take action? ... Jul 12 12:09:36 Tower kernel: mdcmd (241): spindown 9 Jul 12 12:43:28 Tower shfs/user: err: shfs_rmdir: rmdir: /mnt/cache/appdata/plex/Library/Application Support/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-9D1BA5A8-7EF4-4500-993B-052210E296B9-9ed53f7e-de53-4c19-8513-6f5cf1353d8c (39) Directory not empty Jul 12 12:44:07 Tower shfs/user: err: shfs_rmdir: rmdir: /mnt/cache/appdata/plex/Library/Application Support/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-3CD72CCE-712E-4BDB-AE4E-4E4A4F7BCCBE-c907b54c-cd77-49b0-9200-efbf03be953d (39) Directory not empty Jul 12 12:44:07 Tower shfs/user: err: shfs_rmdir: rmdir: /mnt/cache/appdata/plex/Library/Application Support/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-3CD72CCE-712E-4BDB-AE4E-4E4A4F7BCCBE-c907b54c-cd77-49b0-9200-efbf03be953d (39) Directory not empty Jul 12 13:12:25 Tower kernel: mdcmd (242): spindown 15 ...
  13. I have now set these values with the Tips and Tweaks plugin: Current Disk Cache Settings vm.dirty_background_ratio = 2 % vm.dirty_ratio = 3 % Do I need to reboot the server for the settings to kick in? It didn't catch my eye at first but when you mention mover = the time in the log when the "call traces" start, I hope this will help, thanks
  14. I have some problems with my unRaid that eventually crashes when the log gets filled up. I can see a lot of "call traces" in the log and I think it's because of my Plex app. Here is a log sample Jun 19 03:41:03 Tower kernel: Plex Media Serv: page allocation stalls for 10552ms, order:0, mode:0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD) Jun 19 03:41:03 Tower kernel: CPU: 5 PID: 18088 Comm: Plex Media Serv Not tainted 4.9.30-unRAID #1 Jun 19 03:41:03 Tower kernel: Hardware name: ASUSTeK COMPUTER INC. P10S WS/P10S WS, BIOS 3003 01/12/2017 Jun 19 03:41:03 Tower kernel: ffffc9002120fb28 ffffffff813a4a1b 0000000000000001 0000000000000000 Jun 19 03:41:03 Tower kernel: ffffc9002120fbb8 ffffffff810cb5b1 024201ca810c9d8d ffffffff8193d4e2 Jun 19 03:41:03 Tower kernel: ffffc9002120fb50 0000000000000010 ffffc9002120fbc8 ffffc9002120fb68 Jun 19 03:41:03 Tower kernel: Call Trace: Jun 19 03:41:03 Tower kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Jun 19 03:41:03 Tower kernel: [<ffffffff810cb5b1>] warn_alloc+0x102/0x116 Jun 19 03:41:03 Tower kernel: [<ffffffff810cbb67>] __alloc_pages_nodemask+0x541/0xc71 Jun 19 03:41:03 Tower kernel: [<ffffffff810d0d55>] ? __do_page_cache_readahead+0x1ed/0x21f Jun 19 03:41:03 Tower kernel: [<ffffffff81102d82>] alloc_pages_current+0xbe/0xe8 Jun 19 03:41:03 Tower kernel: [<ffffffff810c4d78>] __page_cache_alloc+0x89/0x9f Jun 19 03:41:03 Tower kernel: [<ffffffff810c6971>] filemap_fault+0x23d/0x458 Jun 19 03:41:03 Tower kernel: [<ffffffff810e8f38>] __do_fault+0x68/0xbb Jun 19 03:41:03 Tower kernel: [<ffffffff810edf55>] handle_mm_fault+0x6b1/0xf96 Jun 19 03:41:03 Tower kernel: [<ffffffff81042252>] __do_page_fault+0x24a/0x3ed Jun 19 03:41:03 Tower kernel: [<ffffffff81042438>] do_page_fault+0x22/0x27 Jun 19 03:41:03 Tower kernel: [<ffffffff81680f18>] page_fault+0x28/0x30 Jun 19 03:41:03 Tower kernel: Mem-Info: Jun 19 03:41:03 Tower kernel: active_anon:3674756 inactive_anon:8423 isolated_anon:0 Jun 19 03:41:03 Tower kernel: active_file:11205284 inactive_file:849453 isolated_file:992 Jun 19 03:41:03 Tower kernel: unevictable:0 dirty:847557 writeback:1442 unstable:0 Jun 19 03:41:03 Tower kernel: slab_reclaimable:234063 slab_unreclaimable:47429 Jun 19 03:41:03 Tower kernel: mapped:23935 shmem:118412 pagetables:13135 bounce:0 Jun 19 03:41:03 Tower kernel: free:99927 free_pcp:0 free_cma:0 Jun 19 03:41:03 Tower kernel: Node 0 active_anon:14699024kB inactive_anon:33692kB active_file:44821136kB inactive_file:3397812kB unevictable:0kB isolated(anon):0kB isolated(file):3968kB mapped:95740kB dirty:3390228kB writeback:5768kB shmem:473648kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 12660736kB writeback_tmp:0kB unstable:0kB pages_scanned:288 all_unreclaimable? no Jun 19 03:41:03 Tower kernel: Node 0 DMA free:15892kB min:32kB low:44kB high:56kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15976kB managed:15892kB mlocked:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Jun 19 03:41:03 Tower kernel: lowmem_reserve[]: 0 1054 63260 63260 Jun 19 03:41:03 Tower kernel: Node 0 DMA32 free:250960kB min:2252kB low:3328kB high:4404kB active_anon:679260kB inactive_anon:4kB active_file:266684kB inactive_file:4880kB unevictable:0kB writepending:4904kB present:1240076kB managed:1230080kB mlocked:0kB slab_reclaimable:25360kB slab_unreclaimable:852kB kernel_stack:112kB pagetables:1196kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Jun 19 03:41:03 Tower kernel: lowmem_reserve[]: 0 0 62206 62206 Jun 19 03:41:03 Tower kernel: Node 0 Normal free:132856kB min:132880kB low:196576kB high:260272kB active_anon:14019764kB inactive_anon:33688kB active_file:44554452kB inactive_file:3392932kB unevictable:0kB writepending:3391092kB present:64733184kB managed:63699800kB mlocked:0kB slab_reclaimable:910892kB slab_unreclaimable:188864kB kernel_stack:20016kB pagetables:51344kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Jun 19 03:41:03 Tower kernel: lowmem_reserve[]: 0 0 0 0 Jun 19 03:41:03 Tower kernel: Node 0 DMA: 1*4kB (U) 0*8kB 1*16kB (U) 0*32kB 2*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (U) 3*4096kB (M) = 15892kB Jun 19 03:41:03 Tower kernel: Node 0 DMA32: 4780*4kB (UME) 5006*8kB (UME) 4325*16kB (UME) 1369*32kB (UME) 275*64kB (UME) 82*128kB (UME) 44*256kB (UME) 27*512kB (UM) 21*1024kB (UM) 0*2048kB 1*4096kB (H) = 250960kB Jun 19 03:41:03 Tower kernel: Node 0 Normal: 6190*4kB (UMEH) 3604*8kB (UMEH) 4197*16kB (UMEH) 156*32kB (UMH) 45*64kB (H) 8*128kB (H) 2*256kB (H) 2*512kB (H) 0*1024kB 1*2048kB (H) 0*4096kB = 133224kB Jun 19 03:41:03 Tower kernel: 12174132 total pagecache pages Jun 19 03:41:03 Tower kernel: 0 pages in swap cache Jun 19 03:41:03 Tower kernel: Swap cache stats: add 0, delete 0, find 0/0 Jun 19 03:41:03 Tower kernel: Free swap = 0kB Jun 19 03:41:03 Tower kernel: Total swap = 0kB Jun 19 03:41:03 Tower kernel: 16497309 pages RAM Jun 19 03:41:03 Tower kernel: 0 pages HighMem/MovableOnly Jun 19 03:41:03 Tower kernel: 260866 pages reserved Diagnostics attached. tower-diagnostics-20170619-0833.zip
  15. I'm trying to get prowl notifications to work, what I have done is added a line of code in the rtorrent.rc file, located in cache\appdata\rutorrent\rtorrent. The following line is added with "edit file in Krusader". system.method.set_key = event.download.finished,notify_me,"execute=/config/rtorrent/sendNotification.sh,$d.get_name=" And I have created a file sendNotification.sh in the same location. And that files contains: #!/bin/sh API_KEY="XXXXXXXXXXXXXXXXXXXXXXXXXX" SUBJECT="Download finished" # The message is taken from # .rtorrent.rc ($d.get_name) MESSAGE=$1 curl -d "apikey=$API_KEY&application=rTorrent&event=$SUBJECT&description=$MESSAGE" https://api.prowlapp.com/publicapi/add With the XXXX being my api key. And I have set the chmod 755 on the sendNotification.sh file. But it doesn't work, can anybody see what I'm doing wrong? Is it the path to the *.sh file? or some typo. Or shouldn't I use Krusader to edit/create files, maybe mc is better? Thanks in advance.
  16. I don't know for sure, but I do know that trailing / are important to rsync. Perhaps it's a missmatch issue, where you did /mnt/disk3/ the first time and /mnt/disk3 the second time. I'd run it again like rsync -nrcv /mnt/disk3/ /mnt/disk14/t >/boot/verify_disk14.txt see if that comes back with an empty list (since the files are already in disk14/t) Thanks, I will try that. EDIT:It worked, the file ended up containing: sending incremental file list sent 382,411 bytes received 813 bytes 6.83 bytes/sec total size is 3,928,060,848,066 speedup is 10,250,038.75 (DRY RUN)
  17. So does anyone know why the command: "rsync -nrcv /mnt/disk3 /mnt/disk14/t >/boot/verify_disk14.txt" doesn't work for me?
  18. I just followed the guide and copied every file on disk3 to a folder t on disk14. And ran the command: rsync -nrcv /mnt/disk3 /mnt/disk14/t >/boot/verify_disk14.txt I ended up with a verify_disk14.txt file on my usb stick that contained every file on disk3, did I do something wrong? sending incremental file list disk3/ ... ... ... sent 403,033 bytes received 21,439 bytes 10.69 bytes/sec total size is 3,928,060,848,066 speedup is 9,253,992.84 (DRY RUN)
  19. I have precleared several disks 3-4Tb with v 1.13, is it a big problem? Did that version not completely test disks lager than 2.2Tb? The testing was fine, the written pre-clear signature was, at times, not recognized by unRAID as being present. Ok, I guess I'm fine then. Thanks for the answer.
  20. I have precleared several disks 3-4Tb with v 1.13, is it a big problem? Did that version not completely test disks lager than 2.2Tb?
  21. Ok, thanks Joe...I guess I'll have to make it without cache_dirs. :'(
  22. I'll try it and see if I can catch it when it begins to crash. It been running now for a few hours. [EDIT] free -l free -l total used free shared buffers cached Mem: 3374304 3267792 106512 0 231668 2663280 Low: 880408 789936 90472 High: 2493896 2477856 16040 -/+ buffers/cache: 372844 3001460 Swap: 0 0 0 ulimit -a ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 26101 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 26101 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited ps -eo size,pid,user,command | sort -n ps -eo size,pid,user,command | sort -n 0 2 root [kthreadd] 0 3 root [ksoftirqd/0] 0 6 root [migration/0] 0 7 root [migration/1] 0 9 root [ksoftirqd/1] 0 11 root [khelper] 0 158 root [sync_supers] 0 160 root [bdi-default] 0 162 root [kblockd] 0 289 root [ata_sff] 0 299 root [khubd] 0 408 root [rpciod] 0 428 root [kswapd0] 0 489 root [fsnotify_mark] 0 509 root [nfsiod] 0 512 root [cifsiod] 0 518 root [crypto] 0 679 root [deferwq] 0 888 root [scsi_eh_0] 0 901 root [scsi_eh_1] 0 902 root [scsi_eh_2] 0 903 root [scsi_eh_3] 0 904 root [scsi_eh_4] 0 905 root [scsi_eh_5] 0 906 root [scsi_eh_6] 0 912 root [kworker/u:7] 0 913 root [scsi_eh_7] 0 914 root [scsi_eh_8] 0 918 root [scsi_eh_9] 0 919 root [usb-storage] 0 1012 root [scsi_wq_0] 0 5713 root [flush-8:32] 0 11323 root [mdrecoveryd] 0 11326 root [spinupd] 0 11327 root [spinupd] 0 11328 root [spinupd] 0 11329 root [spinupd] 0 11330 root [spinupd] 0 11331 root [spinupd] 0 11332 root [spinupd] 0 11333 root [spinupd] 0 11334 root [spinupd] 0 11335 root [spinupd] 0 11336 root [spinupd] 0 11337 root [spinupd] 0 11401 root [unraidd] 0 11434 root [reiserfs] 0 13866 root [kworker/1:2] 0 14282 root [kworker/0:1] 0 25329 root [kworker/0:2] 0 27425 root [kworker/u:0] 0 27561 root [kworker/1:0] SZ PID USER COMMAND 284 1 root init 292 1230 root /usr/sbin/inetd 292 1260 root /usr/sbin/crond -l notice 296 1096 root /usr/sbin/syslogd -m0 296 1244 root /usr/sbin/acpid 296 1262 daemon /usr/sbin/atd -b 15 -l 1 296 12425 root logger -tunmenu -plocal7.info -is 300 1100 root /usr/sbin/klogd -c 3 -x 300 1216 bin /sbin/rpc.portmap 304 1126 root /sbin/dhcpcd -t 10 -h Tower eth0 304 11313 root /sbin/agetty 38400 tty1 linux 304 11314 root /sbin/agetty 38400 tty2 linux 304 11315 root /sbin/agetty 38400 tty3 linux 304 11316 root /sbin/agetty 38400 tty4 linux 304 11317 root /sbin/agetty 38400 tty5 linux 304 11318 root /sbin/agetty 38400 tty6 linux 320 1220 root /sbin/rpc.statd 324 1255 81 /usr/bin/dbus-daemon --system 376 22555 root in.telnetd: 192.168.1.9 408 12424 root /bin/bash /boot/unmenu/uu 456 11358 root /usr/sbin/nmbd -D 484 22556 root -bash 664 12323 root /usr/sbin/ntpd -g -p /var/run/ntpd.pid 676 11414 root /sbin/udevd --daemon 676 19097 root /sbin/udevd --daemon 680 707 root /sbin/udevd --daemon 736 11360 root /usr/sbin/smbd -D 768 21253 root ps -eo size,pid,user,command 992 11374 root /usr/sbin/smbd -D 1072 14279 root /usr/sbin/smbd -D 1560 11817 root /usr/sbin/smbd -D 8696 11312 root /usr/local/sbin/emhttp 10660 12428 root awk -W re-interval -f ./unmenu.awk 25908 21254 root sort -n 72148 11524 root /usr/local/sbin/shfs /mnt/user -disks 16777214 -o noatime,big_writes,allow_other,use_ino 276856 11553 nobody /usr/lib/java/bin/java -Xmx100m -Dsubsonic.home=/boot/config/plugins/subsonic -Dsubsonic.host=0.0.0.0 -Dsubsonic.port=37011 -Dsubsonic.httpsPort=0 -Dsubsonic.contextPath=/ -Dsubsonic.defaultMusicFolder=/var/music -Dsubsonic.defaultPodcastFolder=/var/music/Podcast -Dsubsonic.defaultPlaylistFolder=/var/playlists -Djava.awt.headless=true -verbose:gc -jar subsonic-booter-jar-with-dependencies.jar
  23. cache_dirs crashes for me all the time. If I have a putty telnet prompt open I can see this: root@Tower:/boot# cache_dirs -w cache_dirs process ID 5122 started, To terminate it, type: cache_dirs -q root@Tower:/boot# ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: subst.c:7606: cannot allocate 112 bytes (901120 bytes allocated) ./cache_dirs: xmalloc: execute_cmd.c:3599: cannot allocate 72 bytes (901120 bytes allocated) ./cache_dirs: line 462: [: : integer expression expected ./cache_dirs: xmalloc: stringlib.c:135: cannot allocate 120 bytes (901120 bytes allocated) I guess cache_dirs is crashing because it doesn't have enough memory. I have 4Gb of ram. I have also tried to start cache_dirs with only my movies and tv share, like this: cache_dirs -m 3 -M 5 -d 3 -i "Movies" -i "TV\ Series" -w But cache_dirs crashes within a couple of hours. My movie share is 7.58Tb and consist of ~1 190 movies with nfo, md5, folder.jpg, backdrop.jpg files in every folder. And my TV share is 10.01Tb and consist of ~7 397 episodes and the shares is spread across 11 disks. So at least it's ~ (1 190 x 5) + 7 397 = 13 347 files. And some movies and episodes is dvd backups like several *.vob *.ifo *.bup files. So my guess would be it's closer to 15 000 files that cache_dirs need to scan. Plugins that I run is Subsonic and unmenu. Is there anything I can try, so cache_dirs doesn't crash on me?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.