Leaderboard

Popular Content

Showing content with the highest reputation on 07/12/21 in all areas

  1. 2 points
  2. Here are other options for Dell machines 😎
    2 points
  3. Community Applications (aka CA) This thread is rather long, and it is NOT necessary to read it in order to utilize Community Applications (CA) Just install the plugin, go to the apps tab and enjoy the freedom. If you find an issue with CA, then don't bother searching for answers in this thread as all issues (when they have surfaced) are fixed generally the same day that they are found... (But at least read the preceding post or two on the last page of the thread) Simple interface and easy to use, you will be able to find and install any of the unRaid docker or plugin applications, and also optionally gain access to the entire library of applications available on dockerHub (~1.8 million) INSTALLATION Under 6.10.x+ to install CA, just go to the already existing Apps Tab in the Unraid UI and you'll be prompted to automatically install it. For older versions of Unraid, paste the following URL into the Plugins / Install Plugin section: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg After installation, a new tab called "Apps" will appear on your unRaid webGUI. To see what the various icons do, simply press Help or the (?) on unRaid's Tab Bar. Note All screenshots in this post are subject to change as Community Applications continues to evolve Easily search or browse applications Get full details on the application Easily reinstall previously installed applications Find out about your favourite authors And much, much more Multi-Language Installations When running on a supported version of Unraid that supports Multi-Language (6.9.0+), CA is the recommended way to install any of the Language Packs available. See this post for more detail Note that CA is always (and always will be) compatible with the latest Stable version of unRaid, and the Latest/Next version of unRaid. Intermediate versions of various Release Candidates may or may not be compatible (though they usually are - But, if you have made the decision to run unRaid Next, then you should also ensure that all plugins and unRaid itself (not just CA) are always up to date). Additionally, every attempt is made to keep CA compatible with older versions of unRaid. As of this writing, CA is compatible with all versions of unRaid from 6.12.0 onward. Require a proxy? See this post for CA to operate through a proxy Cookie Note: CA utilizes cookies in its regular operation. Some features of CA may not be available if cookies are not enabled in your browser. No personally identifiable information is ever collected, no cookies related to any software or media stored on your server are ever collected, and none of the cookies are ever transmitted anywhere. Cookies related to the "Look & Feel" of Community Applications will expire after a year. Any other cookies related to the operation of CA are automatically deleted after they are used. Multi-language Note: When running on a version of unRaid that supports multi-language, CA will operate in the language of your choice. However, translations of the descriptions of the applications themselves are outside the scope of the translations, and will always appear in whatever the author themselves has dictated (ie: English) Additionally, CA supports translations on the spotlighted apps "Reason". Translations can be submitted against https://github.com/Squidly271/Community-Applications-Moderators/blob/master/Recommended.json if you wish to contribute Contribute towards development (or simply buy me a beer) Credits Development Andrew Zawadzki Additional Contributions bonienl, eschultz GUI Layout Design Mex Application Feed Andrew Zawadzki, Kode, Limetech Additional Testing CHBMB, SpaceInvaderOne, Sparklyballs, wgstarks, DJoss, Zer0Nin3r, Mex, prostuff1, bonienl, ljm42, kizer, trurl, Jos, Limetech, SimonF, ich777, jimmy898, Alex.b, neruve, Eugeni_CAT, ChaseCares, TheEyeTGuy Moderation dockerPolice, pluginCop Additional Libraries Awesomeplete (Lea Verou), Chart.js (Various), XML2Array, Array2XML (Miles Johnson), chartjs-plugin-trendline (Marcus Alsterfjord), Magnific-Popup (Dmitry Semenov) Copyright © 2015-2023 Andrew Zawadzki For the details regarding the various policies that Community Applications has regarding applications, see here
    1 point
  4. Note: this community guide is offered in the hope that it is helpful, but comes with no warranty/guarantee/etc. Follow at your own risk. What can you do with WireGuard? Let's walk through each of the connection types: Remote access to server: Use your phone or computer to remotely access your Unraid server, including: Unraid administration via the webgui Access dockers, VMs, and network shares as though you were physically connected to the network Remote access to LAN: Builds on "Remote access to server", allowing you to access your entire LAN as well. Server to server access: Allows two Unraid servers to connect to each other. LAN to LAN access: Builds on "Server to server access", allowing two entire networks to communicate. (see this guide) Server hub & spoke access: Builds on "Remote access to server", except that all of the VPN clients can connect to each other as well. Note that all traffic passes through the server. LAN hub & spoke access: Builds on "Server hub & spoke access", allowing you to access your entire LAN as well. VPN tunneled access: Route traffic for specific Dockers and VMs through a commercial WireGuard VPN provider (see this guide) Remote tunneled access: Securely access the Internet from untrusted networks by routing all of your traffic through the VPN and out Unraid's Internet connection In this guide we will walk through how to setup WireGuard so that your trusted devices can VPN into your home network to access Unraid and the other systems on your network. Prerequisites You must be running Unraid 6.8-6.9 with the Dynamix WireGuard plugin from Community Apps or Unraid 6.10+ (which has the plugin built in). Understand that giving someone VPN access to your LAN is just like giving them physical access to your LAN, except they have it 24x7 when you aren't around to supervise. Only give access to people and devices that you trust, and make certain that the configuration details (particularly the private keys) are not passed around insecurely. Regardless of the "connection type" you choose, assume that anyone who gets access to this configuration information will be able to get full access to your network. This guide works great for simple networks. But if you have Dockers with custom IPs or VMs with strict networking requirements, please see the "Complex Networks" section below. Unraid will automatically configure your WireGuard clients to connect to Unraid using your current public IP address, which will work until that IP address changes. To future-proof the setup, you can use Dynamic DNS instead. There are many ways to do this, probably the easiest is described in this 2 minute video from SpaceInvaderOne If your router has UPnP enabled, Unraid will be able to automatically forward the port for you. If not, you will need to know how to configure your router to forward a port. You will need to install WireGuard on a client system. It is available for many operating systems: https://www.wireguard.com/install/ Android or iOS make good first systems, because you can get all the details via QR code. Setting up the Unraid side of the VPN tunnel If UPnP is enabled on your router and you want to use it in Unraid, go to Settings -> Management Access and confirm "Use UPnP" is set to Yes On Unraid 6.8, go to Settings -> VPN Manager Give the VPN Tunnel a name, such as "MyHome VPN" Press "Generate Keypair". This will generate a set of public and private keys for Unraid. Take care not to inadvertently share the private key with anyone (such as in a screenshot like this) By default the local endpoint will be configured with your current public IP address. If you chose to setup DDNS earlier, change the IP address to the DDNS address. Unraid will recommend a port to use. You typically won't need to change this unless you already have WireGuard running elsewhere on your network. Hit Apply If Unraid detects that your router supports UPnP, it will automatically setup port forwarding for you: If you see a note that says "configure your router for port forwarding..." you will need to login to your router and setup the port forward as directed by the note: Some tips for setting up the port forward in your router: Both the external (source) and internal (target/local) ports should be the set to the value Unraid provides. If your router interface asks you to put in a range, use the same port for both the starting and ending values. Be sure to specify that it is a UDP port and not a TCP port. For the internal (target/local) address, use the IP address of your Unraid system shown in the note. Google can help you find instructions for your specific router, i.e. "how to port forward Asus RT-AC68U" Note that after hitting Apply, the public and private keys are removed from view. If you ever need to access them, click the "key" icon on the right hand side. Similarly, you can access other advanced setting by pressing the "down chevron" on the right hand side. They are beyond the scope of this guide, but you can turn on help to see what they do. In the upper right corner of the page, change the Inactive slider to Active to start WireGuard. You can optionally set the tunnel to Autostart when Unraid boots. Defining a Peer (client) Click "Add Peer" Give it a name, such as "MyAndroid" For the initial connection type, choose "Remote access to LAN". This will give your device access to Unraid and other items on your network (there are some caveats to this covered below) Click "Generate Keypair" to generate public and private keys for the client. The private key will be given to the client / peer, but take care not to share it with anyone else (such as in a screenshot like this) For an additional layer of security, click "Generate Key" to generate a preshared key. Again, this should only be shared with this client / peer. Click Apply. Note: Technically, the peer should generate these keys and not give the private key to Unraid. You are welcome to do that, but it is less convenient as the config files Unraid generates will not be complete and you will have to finish configuring the client manually. Configuring a Peer (client) Click the "eye" icon to view the peer configuration. If the button is not clickable, you need to apply or reset your unsaved changes first. If you are setting up a mobile device, choose the "Create from QR code" option in the mobile app and take a picture of the QR code. Give it a name and make the connection. The VPN tunnel starts almost instantaneously, once it is up you can open a browser and connect to Unraid or another system on your network. Be careful not to share screenshots of the QR code with anyone, or they will be able to use it to access your VPN. If you are setting up another type of device, download the file and transfer it to the remote computer via trusted email or dropbox, etc. Then unzip it and load the configuration into the client. Protect this file, anyone who has access to it will be able to access your VPN. Complex Networks The instructions above should work out of the box for simple networks. With "Use NAT" defaulted to Yes, all network traffic on Unraid uses Unraid's IP, and that works fine if you have a simple setup. However, if you have Dockers with custom IPs or VMs with strict networking requirements, you'll need to make a few changes: In the WireGuard tunnel config, set "Use NAT" to No In your router, add a static route that lets your network access the WireGuard "Local tunnel network pool" through the IP address of your Unraid system. For instance, for the default pool of 10.253.0.0/24 you should add this static route: Destination Network: 10.253.0.0/24 (aka 10.253.0.0 with subnet 255.255.255.0) Gateway / Next Hop: <IP address of your Unraid system> Distance: 1 (your router may not have this option) If you use pfSense, you may also need to check the box for "Static route filtering - bypass firewall rules for traffic on the same interface". See this. If you have Dockers with custom IPs then on the Docker settings page, set "Host access to custom networks" to "Enabled". see this: https://forums.unraid.net/topic/84229-dynamix-wireguard-vpn/page/8/?tab=comments#comment-808801 There are some configurations you'll want to avoid, here is how a few key settings interact: With "Use NAT" = Yes and "Host access to custom networks" = disabled (static route optional) server and dockers on bridge/host - accessible! VMs and other systems on LAN - accessible! dockers with custom IP - NOT accessible (this is the "simple network" setup assumed by the guide above) With "Use NAT" = Yes and "Host access to custom networks" = enabled (static route optional) server and dockers on bridge/host - accessible! VMs and other systems on LAN - NOT accessible dockers with custom IP - NOT accessible (avoid this config) With "Use NAT" = No and no static route server and dockers on bridge/host - accessible! VMs and other systems on LAN - NOT accessible dockers with custom IP - NOT accessible (avoid this, if "Use NAT" = No, you really need to add a static route in your router) With "Use NAT" = No and "Host access to custom networks" = disabled and static route server and dockers on bridge/host - accessible! VMs and other systems on LAN - accessible! dockers with custom IP - NOT accessible (You've come this far, just set "Host access to custom networks" to enabled you're set) With "Use NAT" = No and "Host access to custom networks" = enabled and static route server and dockers on bridge/host - accessible! VMs and other systems on LAN - accessible! dockers with custom IP - accessible! (woohoo! the recommended setup for complex networks) About DNS Everything discussed so far should work if you access the devices by IP address or with a Fully Qualified Domain Name such as yourpersonalhash.unraid.net. Short names such as "tower" probably won't work, nor any DNS entries managed by the router. To get those to work over the tunnel, return to the VPN Manager page in Unraid, switch from Basic to Advanced mode, and add the IP address of your desired DNS server into the "Peer DNS Server" field (don't forget to put the updated config file on the client after saving it!) You may want to use the IP address of the router on the LAN you are connecting to, or you could use a globally available IP like 8.8.8.8 ** "WireGuard" and the "WireGuard" logo are registered trademarks of Jason A. Donenfeld.
    1 point
  5. A container to easily download the windows 11 preview iso directly from microsoft and put in the Unraid iso share
    1 point
  6. Please give it a little time to pick up the data and make sure the exporter is running in the plugin page. PiHole can take a little to update if you configured it for the first time.
    1 point
  7. You have set the IP wrong in the prometheus.yml you have to specify the unRAID IP not the PiHole IP. The PiHole Exporter is a bridge between your PiHole and Prometheus that runs on unRAID.
    1 point
  8. @DBone-Unraid Oh My Goodness! You are THE MAN!! Thanks so much for this help. I went ahead and installed the User Scripts plugin, which is very awesome and easy to use.... I then created a script that removes all -i from the ini files and deletes them, and copies over my edited versions from a "Safe Folder" and reapplies the +i attribute... All my settings stick now, and it is as easy as running that plugin script from unraid after I edit the INI files from my safe folder Thanks so so much for helping me with this. a lot of hair pulling not happening now.
    1 point
  9. Oh, das löst Plex sehr geschickt. Passiert bei mir täglich ... Metadaten sind vom Content abgekoppelt. Das hängt Plex einfach um. Wenn sich ein Ordner-/Dateiname ändert und Plex aus Versehen Duplikate erzeugt, musst Du höchstens den Papierkorb löschen. Man darf den Papierkorb nur nicht löschen wenn ein Ordner, eine Datei oder gar eine komplette Platte mit Content vorübergehend weggefallen ist. Ansonsten verliert man die Metadaten (z.B. Gesehen-Markierung).
    1 point
  10. That statement does not compute. Parity is realtime, a check just verifies that all drives can be read accurately and the realtime parity has stayed in sync. If everything is working properly you should be able to replace the drive at any time and not lose anything.
    1 point
  11. OK right now i have the monitor attached to the NVIDIA card.. iGPU is set as primary in the graphics card.. I rebooted and so far it's OK.. i have a feeling it isn't because of plugging into the HDMI but I could be wrong, I also removed gpu statistics plugin. It seemed after I booted up if I go to the Dashboard or NVIDIA plugin page it would do that init fail message.. so far so good but we'll see
    1 point
  12. Das meinte ich damit quasi. Das war etwas ungünstig von mir erklärt. Das hatte mich nämlich am Anfang auch etwas verwirrt. Wenn man die Backups nicht löscht oder gelöscht werden und dann per Windows-Explorer, WinSCP etc. die Größe checkt, wundert man sich erstmal.
    1 point
  13. It has been a long time hasn't it... I do plan to continue and have been working on some of the oldest requests! But the truth of the matter is that working from home for over a year now has put a bit of a damper on me. Sitting alone in front of the computer all day and then continue in the evening has been a bit of a tough sell for me. The cases are coming, just not very fast
    1 point
  14. Petite update après une petit heure en "visio-conférence" avec un ingénieur réseau de chez Kemp. Après vérification et multiples tests, (dernière MaJ du container docker datant d'il y a 4 ans), le container n'est donc plus supporté par les versions actuelles de Docker. Le container étant très peu utilisé le développement as donc été arrêté par l'équipe. Une relance as été faite mais rien n'assure la reprise du dev. Il reste tout de même un moyens de faire fonctionner leur LoadMaster (LoadBalancer) dans une VM, je fais actuellement des tests de mon côté et tiendrais au courant si des résultats positifs en résultent. Cordialement ^^
    1 point
  15. this makes sense my parity drives are seagate 8TB disks but are always spinning. i am not going crazy.. thanks JorgeB applied the changes to the 3 drives and rebooted. see how it goes.
    1 point
  16. Hey, thanks for replying and also thanks for developing this. For the record, the 'culprit' is the 2nd entry of plots_dir which doesn't have an edit button. That being said, I did change this one to the correct value (along with the first one). I also had to go into config.yaml and and manually add the 2nd folder. Now I have this in there: plot_directories: - /plotting2 - /plots - /plots,/plotting2 Everything works as intended now and I do see everything properly listed on the farming page. Thanks!
    1 point
  17. just wanted to make sure this was correct. I have a standard wallet and 2 pooling wallets. My pool I joined is on wallet ID 2, and it appears to be functioning properly. Wasn't sure if wallet ID 3 should be any concern. I had joined and left another pool previously before figuring out how to properly setup my pool and plotting. Only wallet ID 2 and 3 show up on my pooling page. I'm seeing frequent partials as well on my pool.
    1 point
  18. All you need are some portable plots and you're good to go. Make sure they are plotted with the correct farmer_pk, pool_contract_address keys. You can find this in the bottom of the plotman.yaml file.
    1 point
  19. Tried to bypass NginxProxyManager, and tried to connect to collabora directly, with self signed cert, and disabled cert verification from NC side. On 6.4.10.3 it does NOT work even like this. but on 6.4.9.3 it DOES work. Something is going very wrong with these images. Collabora did some RE-UPLOADS of 6.4.10.3 (and i think on 6.4.10.2 also) and REMOVED 6.4.10.4. TBH, removing and overwriting images on a repository is a very very very bad tactic and can mess up with a lot of automated systems. If something goes wrong just issue a patch and create a new image. Imagine someone have updated to the broken 6.4.10.3 image and they re-upload a working 6.4.10.3 image, the poor guy will never see the update because the update check will tell him that he is up to date. And he will be struggling for no reason. I hope OnlyOffice starts supporting Cell Locking/protection soon (it's been on their todo list since 2017..) so I can move there. rant over..
    1 point
  20. Edited : Figured out the problem. Thank you Didn't realize there were three thing I had to put in. Had the farmer address missing. -t -e controller_host=10.0.0.100 -e farmer_address=10.0.0.100 -e worker_address=10.0.0.90
    1 point
  21. I ended up adding a completely new NPM container and was able to register new certs without issue, i guess I'll see if they renew in a couple months. Thanks for your help in troubleshooting, I'm still learning Linux and Docker, so any help is invaluable.
    1 point
  22. When I open up my dashboard I'm able to login but it's not showing any of my hosts, nothing shown in the main dashboard tab, just blank white below. Functionally all of the hosts are working. I tried restarting the container and clearing cache without luck. I did a few docker container updates so not sure if this was one that upgrading to the latest version has caused it. Any ideas on fixing it? Also, could I get a reminder on how to set a version tag for unraid/docker to revert to? Edit: Nevermind, changed browser and it appears to be a browser related issue. However, still curious the best way to revert container versions based on the tag. I tried adding :v1.16.1 and it didn't work..
    1 point
  23. so thank you again @JorgeB for the suggestion, the method seems to work and i have already rebuilt two disks with it my data seems alright
    1 point
  24. As @TexasUnraid said, the CLI tools have no issue. So for now I select the Krusader Docker container and open a console vs the web GUI. From the console it's easy enough to use 'unrar e myfile.rar' which has worked perfectly every time I've needed it. I'm curious though - as I'm still running unrar from the Krusader container, you would think that using the console and the CLI tools would have the same memory issue but they don't. At least there's a simple workaround and it's rarely needed anyhow. I'll also occasionally use Windows and the old standby QuickPAR to try and repair a rar set if the unRAID version of the par tools didn't work.
    1 point
  25. It's probably not referring to free space, but inode allocation. You need to run a balance https://forums.unraid.net/topic/62230-out-of-space-errors-on-cache-drive/?tab=comments#comment-610551
    1 point
  26. Hello thanks for the headsup! I had trouble launching the memtest included with UNRAID. After downloading it seperatly and running I found 1 RAM stick faulty. Most likely causing the issue. Reformatting the cache drives etc and testing now.
    1 point
  27. @codefaux hey, thanks. My server has been running for 69 nice days without interruption. thanks for your help
    1 point
  28. I was actually able to import the pools fine and access the data just as you would any mounted drive. But i made a mistake of where i mounted the pools and they now overlap and don't work... Have to figure out how to stop it from mounting them on startup. Any tips? Ok got that sorted actually... Just imported the pools back into TrueNAS and Unraid allowed me to import them manually. Got rid of all my VM's and moved to dockers so now should be nice and easy to get this to work...
    1 point
  29. its cloudflared and zerotier that's not working. will try to change that setting again later, cant stop docker now. Edit: just retried, now everything works just fine. Thanks!
    1 point
  30. Yeah i have sorted it. But update must of done it because i had youtube-dl.subfolder.conf and youtube-dl.subfolder.conf.sample in the folder! i've not touched it since installing it!
    1 point
  31. Check the recent posts for the solution. The last update did not add the youtube-dl.subfolder.conf. That happened last year.
    1 point
  32. Hi @Body Karate, I too was having issues with my GUS.ini & Gami.ini files being overwritten upon server restart. It was happening randomly. One way I found to keep the files intact was to use the linux chattr command to change the attribute of those two files so that they could not be modified, deleted or overwritten at all. To accomplish this once you have your settings how you want them in those files you would open up a terminal window from your unraid web interface and then change directory into to where those files are saved. Then issue the following commands on those files: chattr +i Game.ini chattr +i GameUserSettings.ini Keep in mind that you will not be able to edit these files once the command has been run. In order to make changes to the files you will need to run the command using the -i option as follows: chattr -i Game.ini chattr -i GameUserSettings.ini Once you make your changes run the command with the +i option mentioned previously and they should not get changed/overwritten when the server starts. You will get an error in the Docker log when the docker tries to change ownership of the files but that is fine because you don't want them to be touched once you have them set how you want them. For one server this will work just fine but once you get multiple servers up and running and they each have their own GUS.ini & Game.ini settings then you will definitely want to look into the User Scripts plugin for unraid. With that plugin you can write a script that can unlock the files, copy over the updated files that you updated from a location on your server that you can modify and then lock the files down again.
    1 point
  33. @limetech Do you have any feedback, there are users that cannot move off 6.9.1 as their drives no longer spindown > 6.9.1
    1 point
  34. After updating to 1.17.0-ls71 SWAG doen't start: nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/debianbullseye.subdomain.conf:36 nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/debianbuster.subdomain.conf:36 nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/ferdi-client.subdomain.conf:36 nginx: [emerg] "proxy_redirect" directive is duplicate in /config/nginx/proxy-confs/onlyoffice.subdomain.conf:22 i have to commenting out "proxy_redirect" in my all *.subdomain.conf to get SWAG work.
    1 point
  35. Kommt auf Deine Risikobereitschaft und ein gutes Backup an ... Bei einer existierenden Dual-Parity mache ich vorab kein Preclear. In allen anderen Fällen sehr wohl. Ist halt meiner Paranoia geschuldet. Ich will nichts, überhaupt nichts, verlieren. Dafür sind mir merine Daten zu kostbar. Sind die das Backup oder werden die gerade precleared? Das geht aus Deinem Post nicht ganz klar hervor.
    1 point
  36. On version 6.9.1, the Linux kernel updated to 5.10 and it supports swapfile on BTRFS. On filesystem BTRFS, you should follow this [url] to make a swapfile, and then it will work. Hope this will be fixed.
    1 point
  37. OK, can't believe this but me setting up a cache pool has coincided with an update from avast that has dropped my speeds to 230mb/s! I tried a transfer from VM to VM (unraid1 to unraid2) and speeds were spot on, looked through all my Windows programs and stopped them one by one and as soon as I stopped avast speeds are back to 1000mb/s So sorry to have wasted yours and anyone else's time but hope this helps someone else at some point!
    1 point
  38. Just wanted to add that Windows 10 Update Version 2004 broke access for both computers I applied the update to. While the GPO showed Lanman Workstation allowing insecure guest logons, it wasn't working. When investigating the Registry, it showed a value of 0, so it was not active, and the GPO was not being applied. Had to perform registry edit as show in previous link to once again make active and restore connectivity. Regedit Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters SHOW LESS
    1 point
  39. Ryzen 5 2600 16GB DDR4 2666mhz Crucial Ballistix AT Asus TUF B450-Plus Gaming 512GB Intel NVME for Appdata/dockers Dell H310 PERC Be Quiet 750W Power Zone Power Supply Unit Silverstone SST-FS303B 2*5.25 to 3*3.5 bay adapter Additional front intake fan Fractal Design Dynamic GP-14 Fractal Define R5 Case Array: 3*3TB (WD3001FYYG) 3*6TB (WDC_WD60EZRZ) 3*2TB (TOSHIBA_DT01ACA200_63NKVAMKS) 1*2TB (WDC_WD20EZRX) 29TB usable space. Unassigned (for downloads) 1*2TB (ST32000444SS) MSI GT710 2GB DDR3 Passthrough to Windows 10 VM This picture is after 6 months of operation, the dust filters on the front of the case really do their job!
    1 point
  40. @Subtletree One of the passed through devices causing this error. Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.1 Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: device [1022:1483] error status/mask=00100000/04400000 Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: [20] UnsupReq (First) Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: TLP Header: 34000000 0a000010 00000000 80008000 Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: broadcast error_detected message Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: broadcast mmio_enabled message Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: broadcast resume message Apr 28 18:37:25 Tower kernel: pcieport 0000:00:03.1: AER: Device recovery successful 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] Kernel driver in use: pcieport One of the devices you pass through causing this PCI-bridge to throw an error. It might be the following or one of the 2 USB controllers you're passing through 07:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Remove them one by one and test if it helps.
    1 point
  41. The 2.0.4 label is either a typo by the dev team or is an early beta of 2.0.4. In any case that version, it's the version I'm using and it works with the ltConfig plugin. To get the plugin working, you'll need to compile it from scratch using the python version that's used in the container. Instructions On the same page you tried download the .egg from, https://github.com/ratanakvlun/deluge-ltconfig/releases instead download one of the compressed Source Code files. Extract the folder and copy or scp it to the plugins folder of the delugevpn container. e.g. /mnt/user/appdata/binhex-delugevpn/plugins on your unRAID server. Now go to the webGUI of your unRAID server, click on the Docker tab, click on the icon of the delugevpn container and open the Console. In the console, go to the Source Code folder you just uploaded in the plugins directory which will most likely be in /config/plugins. Then compile the plugin. cd /config/plugins/deluge-ltconfig-2.0.0 python setup.py bdist_egg The compiled egg will be located at /config/plugins/deluge-ltconfig-2.0.0/dist/ltConfig-2.0.0-py3.8.egg. Copy it to the root of the plugins directory. cp /config/plugins/deluge-ltconfig-2.0.0/dist/ltConfig-2.0.0-py3.8.egg /config/plugins You may need to restart your delugevpn container after this, but the plugin should now show in the WebUI of Deluge. In the Deluge WebUI, go to Preferences -> Plugins and enable the ltConfig plugin. A new ltConfig menu option will become available inside Preferences. Click ltConfig and make sure "Apply settings on startup" is checked. Scroll down the menu until you locate enable_outgoing_utp enable_incoming_utp Make sure these two settings are unchecked and Apply the changes. Restart the delugevpn container one more time and double check that the ltConfig plugin loaded on startup and the two settings are unchecked. Enjoy your faster torrent speeds again.
    1 point
  42. 1. On Linux or Mac, use ssh-keygen to generate a key pair, there'll be 2 files generated, a private key file (e.g. id_rsa) and a public key file (e.g. id_rsa.pub); 2. On your unRAID server, enter folder /root/.ssh (create the folder if it doesn't exist), then edit the file /root/.ssh/authorized_keys (create the file if it doesn't exist), and copy/paste the contents of public key file (id_rsa.pub) into authorized_keys. If you have multiple Linux/Mac computers, you may put multiple public keys into authorized_keys, one in a line; 3. Change permission of authorized_keys to 600: chmod 600 /root/.ssh/authorized_keys Now you can ssh into unRAID w/o entering password. However, after reboot, you'll lose everything in /root folder, so you need to find a way to keep everything during a reboot. Here's how I made it: 1. Create a script /boot/config/ssh/setup_ssh_client.sh: #!/bin/bash SSH_DIR=/root/.ssh mkdir ${SSH_DIR} chmod 755 ${SSH_DIR} cp /boot/config/ssh/authorized_keys ${SSH_DIR}/authorized_keys chmod 600 ${SSH_DIR}/authorized_keys make it executable: chmod 755 /boot/config/ssh/setup_ssh_client.sh 2. Copy the previously created authorized_keys into /boot/config/ssh folder cp /root/.ssh/authorized_keys /boot/config/ssh/ 3. Edit /boot/config/go and add the following line at the end, so that our setup script can be called during reboot: /boot/config/ssh/setup_ssh_client.sh All done. Now your ssh settings will be setup automatically at reboot.
    1 point