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.

vast

Members
  • Joined

  • Last visited

Everything posted by vast

  1. I am sure in time they will pick up your template in the CA. They must!!! If you need any help let me know!
  2. Just made a quick guide on how to do it here ;)
  3. I have managed to install it just now. Open Unraid console from Web-UI. Navigate to DockerMan Template folder using "cd /boot/config/plugins/dockerMan/templates-user/" Then use wget to the download the template from Github using "wget https://raw.githubusercontent.com/Mayo-248/unraid-templates/refs/heads/main/teamspeak6server/my-TeamSpeak6-Server-Beta.xml" You should now have a template file called "my-Teamspeak6-Server-Beta.xml" in that folder. Go to your Unraid "Docker" tab, click "Add Container", and select the newly added template from the "Template" dropdown menu. Just install and done ;)
  4. Thanks for doing this Mayo, greatly appreciated!
  5. I keep getting the following error, not sure what to do about it: socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported Traceback (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 makedirs PermissionError: [Errno 13] Permission denied: '/media_store'
  6. binhex/arch-qbittorrentvpn:5.1.2-1-03 fixed it for me thanks, not the first time this has happened unfortunately
  7. I have a different problem now, just updated to the latest version of the docker image and now I've got this happeneing: 2025-07-14 11:38:59.593374 [info] Host is running unRAID 2025-07-14 11:38:59.611980 [info] System information: Linux 0318619ed79f 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 GNU/Linux 2025-07-14 11:38:59.632850 [info] Image tags: BASE_RELEASE_TAG=2025071102,INT_RELEASE_TAG=2025071102,IMAGE_RELEASE_TAG=5.1.2-1-04 2025-07-14 11:38:59.667996 [info] PUID defined as '99' 2025-07-14 11:38:59.728295 [info] PGID defined as '100' 2025-07-14 11:39:00.104598 [info] UMASK defined as '000' 2025-07-14 11:39:00.132961 [info] Permissions already set for '/config' 2025-07-14 11:39:00.187957 [info] Deleting files in /tmp (non recursive)... 2025-07-14 11:39:00.223388 [info] VPN_ENABLED defined as 'yes' 2025-07-14 11:39:00.254178 [info] VPN_CLIENT defined as 'wireguard' 2025-07-14 11:39:00.278685 [info] VPN_PROV defined as 'pia' 2025-07-14 11:39:00.353402 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf /usr/sbin/init.sh: line 212: /usr/local/bin/dos2unix.sh: No such file or directory
  8. Well it was 50 exactly, dunno if thats what you mean, I went ahead and set it to 10 now, just to see if anything changes.
  9. For a while now I've been having issues with the client using excessive CPU resources. All of my cores are running on 100% which only leaves me with hyper-threads. I'm not sure what's going on. The torrent client isn't even downloading anything. The logs don't seem to indicate anything special either: 2025-06-12 17:47:44,059 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32775' 2025-06-12 17:57:44,127 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32775' 2025-06-12 18:07:44,167 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32775' 2025-06-12 18:17:44,208 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32775' 2025-06-12 18:27:44,248 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32775' 2025-06-12 18:37:44,290 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '32775' I have looked into the other supervisord files as well and I'm not sure what to look for, it all seems relatively normal for me. Any input would really help!
  10. My worry is as soon as I start transferring everything (about 18 TB) back to the server with all the QVOs and writing it onto them, that the performance will completely plummet as soon as the transfer is complete. That would be the most write intensive task. Sometimes I write bigger shows with entire seasons or entire shows to the disks, sometimes it requires extraction of files too. So if those don't have major an impact it's fine, but if its an issue, then the QVOs would not do the job.
  11. Yes, that is my expectation. I would offload all the data onto another server I have with Krusader, then take out replace all the drives and setup a new array. Yeah I was thinking of that and it sounds reasonable, but I heard that the QVOs would definitely not be good with that.. Maybe you can give advise on the drives you'd recommend for that purpose...
  12. Yep, I would assume so. I should have clarified this in my post, and will edit it, I would like to replace the entire array with SSDs if and when I do.
  13. Nope, so the idea would be replacing the entire array with SSDs only.
  14. Hi everyone, I'd appreciate you opinion on this matter. I've been having a Seagate drive in my Plex Unraid server failing (SMART Report Reallocated sector count is increasing slowly) potentially due to overheating (Sometimes they run about 50 Celcius). Not sure if I should just leave it or replace it. Its the parity drive ironically. Unfortunately, I can't really get the server much cooler with noise/fan speed ratio as it is all in a cupboard and the hot air circulates in there. I was thinking a practical solution would be to just scrap all the hdds as they run quite hot and need quite a bit of cooling. So I came across QVO drives by Samsung that have 8TB, the only thing I'm concerned about is them completely slowing down after a while, especially while being in an array. I was also thinking about the PM drives as they seem more resilient. I'm evaluating on replacing all my HDDs to SSDs. I'm curious for your opinions and feedback. Thank you!
  15. On another note, I saw PIA recently added Switzerland as a dedicated IP location. So I am considering getting that again. Do you think there would be a way to select this dedicated IP via the ENDPOINT variable?
  16. I see to be having huge issues with speed, dropping to a couple of KB/s. I used to have 25 MB/s. Furthermore, I've gone ahead and set qBit to TCP connections only. Yet, it seems that my speeds are very bad on the PIA network. Not sure what is going on. Maybe it would be interesting to see if you have recommended settings for qBit to use together with PIA.
  17. Oh okay, I think I understood this incorrectly then. The ENDPOINT requires an IP from the vpn provider, not a written string like "Switzerland" or "Netherlands". I just thought since there is a generator that operates that way for PIA, it would be the same here. That should also explain as to why the generator did not work when running it the first time with my PIA credentials.
  18. I was also wondering where can I find the ENDPOINT variable, for the PIA Wireguard config generator, in which config file? I would love to change it to Switzerland instead of the Netherlands.
  19. Somehow it seems that via PIA my Wireguard configuration is not properly obtained. The Address and Public Key is missing in the config file when obtained and therefore the Wireguard instance fails to connect properly. Erroring out on those lines missing. Address = PrivateKey = ************************************* PostUp = '/root/wireguardup.sh' PostDown = '/root/wireguarddown.sh' [Peer] PublicKey = AllowedIPs = 0.0.0.0/0 Endpoint = ************************************
  20. So I checked and it seem I only have the issue when trying to run Wireguard, but it works completely fine when running OpenVPN. Obviously Wireguard would be nicer since the performance should be substantially better.
  21. Not sure what you mean by that?!? Host port 3 is set to 8080 as well as the WEBUI_PORT.
  22. I've just finished setting up docker using wireguard and the config provided from my vpn provider. I'm not sure why but I can't connect to the qbit web-ui. I've tried running it in host mode that doesn't seem to work at all. Only bridged mode works. I'm really unsure as to why the web-ui doesn't show up. I tried changing ports etc, and I'm aware that no other app is using that port. Any suggestions? text error warn system array login -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i wg0 -j ACCEPT -A OUTPUT -d <HIDDEN-for-my-PRIVACY>/32 -o eth0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --sport 8080 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o wg0 -j ACCEPT 2023-02-18 13:58:11,311 DEBG 'start-script' stdout output: -------------------- 2023-02-18 13:58:11,464 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2023-02-18 13:58:11,889 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2023-02-18 13:58:11,896 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2023-02-18 13:58:11,897 DEBG 'start-script' stderr output: [#] wg setconf wg0 /dev/fd/63 2023-02-18 13:58:11,899 DEBG 'start-script' stderr output: [#] ip -4 address add 100.82.142.69/32 dev wg0 2023-02-18 13:58:11,904 DEBG 'start-script' stderr output: [#] ip link set mtu 1420 up dev wg0 2023-02-18 13:58:11,906 DEBG 'start-script' stderr output: [#] resolvconf -a wg0 -m 0 -x 2023-02-18 13:58:12,141 DEBG 'start-script' stderr output: could not detect a useable init system 2023-02-18 13:58:13,387 DEBG 'start-script' stderr output: [#] wg set wg0 fwmark 51820 2023-02-18 13:58:13,388 DEBG 'start-script' stderr output: [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 2023-02-18 13:58:13,389 DEBG 'start-script' stderr output: [#] ip -4 rule add not fwmark 51820 table 51820 2023-02-18 13:58:13,391 DEBG 'start-script' stderr output: [#] ip -4 rule add table main suppress_prefixlength 0 2023-02-18 13:58:13,393 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2023-02-18 13:58:13,497 DEBG 'start-script' stderr output: [#] iptables-restore -n 2023-02-18 13:58:14,184 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh' 2023-02-18 13:58:15,562 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2023-02-18 13:58:19,026 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address <HIDDEN-for-my-PRIVACY> 2023-02-18 13:58:19,027 DEBG 'start-script' stdout output: [info] WireGuard interface 'up' 2023-02-18 13:58:19,038 DEBG 'watchdog-script' stdout output: [info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 100.82.142.69 different, marking for reconfigure 2023-02-18 13:58:19,183 DEBG 'start-script' stdout output: [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment 2023-02-18 13:58:20,306 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2023-02-18 13:58:20,500 DEBG 'watchdog-script' stdout output: [info] Removing session lock file (if it exists)... 2023-02-18 13:58:20,508 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2023-02-18 13:58:24,959 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8080... 2023-02-18 13:58:25,559 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8080
  23. Here is a configuration I wrote for SWAG, based on the one @beep wrote previously. I will try to submit it to SWAG as a sample so people can use it in the future! Make sure to edit yourdomain.com and your-unraid-lan-ip when using this! ## Version 2022/11/25 # This is a configuration for IBRACORP’s setup of Pterodactyl # It assumes you have the panel configured on port 8001 # It assumes you have the node configured on port 8181 # This will enable a proper connection to Cloudflare # However the SSL security of the connection is not fully granted # This is likely SSL must be enabled for both the panel and then node # from the side of pterodactyl to fully support this. #pterodactyl panel server { listen 80; server_name panel.*; return 301 https://panel.yourdomain.com$request_uri; } server { listen 443 ssl http2; server_name panel.*; add_header X-Frame-Options "SAMEORIGIN" always; include /config/nginx/ssl.conf; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; location / { include /config/nginx/proxy.conf; proxy_pass http://your-unraid-lan-ip:8001; } } #pterodactyl node server { listen 80; server_name node.*; return 301 https://node.yourdomain.com$request_uri; } server { listen 443 ssl http2; server_name node.*; add_header X-Frame-Options "SAMEORIGIN" always; include /config/nginx/ssl.conf; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; location / { include /config/nginx/proxy.conf; proxy_pass http://your-unraid-lan-ip:8181; } }

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.