Leaderboard

Popular Content

Showing content with the highest reputation since 05/26/21 in Report Comments

  1. @limetech I solved this issue as follows and successfully tested it in: Unraid 6.9.2 Unraid 6.10.0-rc1 Add this to /boot/config/go (by Config Editor Plugin): # ------------------------------------------------- # RAM-Disk for Docker json/log files # ------------------------------------------------- # create RAM-Disk on starting the docker service sed -i '/^ echo "starting \$BASE ..."$/i \ # move json/logs to ram disk\ rsync -aH --delete /var/lib/docker/containers/ ${DOCKER_APP_CONFIG_PATH%/}/containers_backup\ mount -t tmpfs tmpfs /var/lib/docker/containers\ rsync -aH --delete ${DOCKER_APP_CONFIG_PATH%/}/containers_backup/ /var/lib/docker/containers\ logger -t docker RAM-Disk created' /etc/rc.d/rc.docker # remove RAM-Disk on stopping the docker service sed -i '/^ # tear down the bridge$/i \ # backup json/logs and remove RAM-Disk\ rsync -aH --delete /var/lib/docker/containers/ ${DOCKER_APP_CONFIG_PATH%/}/containers_backup\ umount /var/lib/docker/containers\ rsync -aH --delete ${DOCKER_APP_CONFIG_PATH%/}/containers_backup/ /var/lib/docker/containers\ logger -t docker RAM-Disk removed' /etc/rc.d/rc.docker # Automatically backup Docker RAM-Disk sed -i '/^<?PHP$/a \ $sync_interval_minutes=30;\ if ( ! ((date('i') * date('H') * 60 + date('i')) % $sync_interval_minutes) && file_exists("/var/lib/docker/containers")) {\ exec("mkdir /var/lib/docker_bind");\ exec("mount --bind /var/lib/docker /var/lib/docker_bind");\ exec("rsync -aH --delete /var/lib/docker/containers/ /var/lib/docker_bind/containers");\ exec("umount /var/lib/docker_bind");\ exec("rmdir /var/lib/docker_bind");\ exec("logger -t docker RAM-Disk synced");\ }' /usr/local/emhttp/plugins/dynamix/scripts/monitor Optional: Limit the Docker LOG size to avoid using too much RAM: Reboot server Notes: By this change /var/lib/docker/containers, which contains only status and log files, becomes a RAM-Disk and therefore avoids wearing out your SSD and allows a permanent sleeping SSD (energy efficient) It automatically syncs the RAM-Disk every 30 minutes to your default appdata location (for server crash / power-loss scenarios). If container logs are important to you, feel free to change the value of "$sync_interval_minutes" in the above code to a smaller value to sync the RAM-Disk every x minutes. If you like to update Unraid OS, you should remove the change from the Go File until it's clear that this enhancement is still working/needed! Your Reward: After you enabled the docker service you can check if the RAM-Disk has been created (and its usage): Screenshot of changes in /etc/rc.d/rc.docker and /usr/local/emhttp/plugins/dynamix/scripts/monitor
    19 points
  2. I like to highlight other improvements available in 6.10, which are maybe not so obvious to spot from the release notes and some of these improvements are internal and not really visible. - Event driven model to obtain server information and update the GUI in real-time The advantage of this model is its scalability. Multiple browsers can be opened simultaneously to the GUI without much impact In addition stale browser sessions won't create any CSRF errors anymore People who keep their browser open 24/7 will find the GUI stays responsive at all times - Docker labels Docker labels are added to allow people using Docker compose to make use of icons and GUI access Look at a Docker 'run' command output to see exactly what labels are used - Docker custom networks A new setting for custom networks is available. Originally custom networks are created using the macvlan mode, and this mode is kept when upgrading to version 6.10 The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off. - Docker bridge network (docker0) docker0 now supports IPv6. This is implemented by assigning docker0 a private IPv6 subnet (fd17::/64), similar to what is done for IPv4 and use network translation to communicate with the outside world Containers connected to the bridge network now have both IPv4 and IPv6 connectivity (of course the system must have IPv6 configured in the network configuration) In addition several enhancements are made in the IPv6 implementation to better deal with the use (or no-use) of IPv6 - Plugins page The plugins page now loads information in two steps. First the list of plugins is created and next the more time consuming plugin status field is retrieved in the background. The result is a faster loading plugins page, especially when you have a lot of plugins installed - Dashboard graphs The dashboard has now two graphs available. The CPU graph is displayed by default, while the NETWORK graph is a new option under Interface (see the 'General Info' selection) The CPU graph may be hidden as well in case it is not desired Both graphs have a configurable time-line, which is by default 30 seconds and can be changed independently for each graph to see a longer or shorter history. Graphs are updated in real-time and are useful to observe the behavior of the server under different circumstances
    14 points
  3. For Unraid version 6.10 I have replaced the Docker macvlan driver for the Docker ipvlan driver. IPvlan is a new twist on the tried and true network virtualization technique. The Linux implementations are extremely lightweight because rather than using the traditional Linux bridge for isolation, they are associated to a Linux Ethernet interface or sub-interface to enforce separation between networks and connectivity to the physical network. The end-user doesn't have to do anything special. At startup legacy networks are automatically removed and replaced by the new network approach. Please test once 6.10 becomes available. Internal testing looks very good so far.
    13 points
  4. Below I include my Unraid (Version: 6.10.0-rc1) "Samba extra configuration". This configuration is working well for me accessing Unraid shares from macOS Monterey 12.0.1 I expect these configuration parameters will work okay for Unraid 6.9.2. The "veto" commands speed-up performance to macOS by disabling Finder features (labels/tags, folder/directory views, custom icons etc.) so you might like to include or exclude these lines per your requirements. Note, there are problems with samba version 4.15.0 in Unraid 6.10.0-rc2 causing unexpected dropped SMB connections… (behavior like this should be anticipated in pre-release) but fixes expected in future releases. This configuration is based on a Samba configuration recommended for macOS users from 45Drives here: KB450114 – MacOS Samba Optimization. #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [global] vfs objects = catia fruit streams_xattr fruit:nfs_aces = no fruit:zero_file_id = yes fruit:metadata = stream fruit:encoding = native spotlight backend = tracker [data01] path = /mnt/user/data01 veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes My Unraid share is "data01". Give attention to modifying the configuration for your particular shares (and other requirements). I hope providing this might help others to troubleshoot and optimize SMB for macOS.
    12 points
  5. Someone please help me understand this? What if I don't wanna associate my keys and my home installs with my unraid forum account? I really like my privacy honestly and what is is my home have no business being associated with any cloud or external servers. This is a very slippery slope and I just don't like it. Is there an option to continue be offline just the way I am right now? I just don't want to be part of this new ecosystem unraid is creating. I trust my privacy and I trust no one, I am sorry..... And there’s absolutely no reason why you can’t support both ways of activating / running unraid. I should not be forced to connect with you if I have a valid key. "UPC and My Servers Plugin The most visible new feature is located in the upper right of the webGUI header. We call this the User Profile Component, or UPC. The UPC allows a user to associate their server(s) and license key(s) with their Unraid Community forum account. Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key. All key purchases and upgrades are also handled exclusively via the UPC"
    12 points
  6. I wonder if I need to enter the NO HEALTHCHECK parameter for all these containers? Will they work stably after that?
    12 points
  7. Since the UPC seems to be stirring up a lot of adverse reaction, maybe the easiest option is to set up a setting under either Settings->Identification or Settings->Management Access (whichever is deemed most appropriate) to remove the Login prompt from the top of the GUI? It can then be defaulted to Enabled until explicitly disabled by the user so new users see it is an option. That might also help with making it clearer that this is purely an optional feature
    11 points
  8. I'll add it back, don't want to get between anyone and their WINE
    7 points
  9. NFSv4 is enabled in this release and UD will now mount remote shares with NFSv4. Go to the UD settings and set the NFS version to NFSv4 and all UD mounted remote NFS shares will be mounted with NFSv4. You'll have to unmount and remount any remote NFS shares to get them mounted with v4.
    6 points
  10. I wont annoy anyone by posting my objection to the UPC again, but in case it makes any difference to the company, for whom I have had great respect and good feelings for about 11 years, this will represent the end of my support. I will not upgrade from my current state. I have ZERO interest in having my servers connected to the internet except for one application on my backup server. There is no need to take any risk whatsoever of allowing some mistake/mismanagement/malicious attack/ whatever at Lime technology and _especially_ over this "for information only" forum. I am stunned that connecting registration on this forum directly to our server license and information was even floated except over a beers. I really can't believe this is being considered. I suppose the modern way of things is subscriptions to gouge every last dime out of customers at a seemingly low price month by month but I am rejecting it from microsoft and will reject it here. I am quite happy with my purchase, have recommended UNRAID uncounted times to others and several friends are now users but that is at an end. I will remain at my current version of unraid that that's that. It sounds like i need also to delete this forum account, unfortunately. I am certain noone gives a rat's but I thought I would clarify my position before signing off of the forum. Why not just charge for version upgrades instead? Is that because people might decide they dont need the current version and you'd like to charge them anyway? At the price of the security of my servers? I just dont understand. I have happily paid for my licenses and was actually considering purchasing a third, but man this will get very expensive very quickly if i pay for it every month. what happens when i stop paying?
    6 points
  11. wohou !!! Congrats to the unraid team 🙂
    5 points
  12. I did some research some time ago and the i915 driver is very troublesome. There has been some work done in 6.10 with this, but there just isn't a lot that Limetech can do since it appears to be a driver issue, I've been using it on 6.10 and have not had any issues. On 6.10, the driver is loaded by Unraid and you don't need to put it in your go file. Of course this is the problem with the i915 driver. Certain things work for some, and not for others. It's all pretty hit and miss. There was recently an issue with Plex not handling the driver correctly, but they released an updated version that fixed the problem with Plex. So I can't say it has been definitely fixed, but it has been worked on.
    5 points
  13. Since you mention "for others to see", I take it as giving me right to comment (after all it IS in a public forum). So let me comment on this after reading your original post too. 1) Disclaimer: I am not taking the side of Limetech. I don't care. I had my own rough times in the past (with Tom too IIRC)... many years ago. Don't even remember why any more. Back then I "voted" with my decision. I stopped using unRAID for years. Yet I returned because it became what I dreamt it should be before I stopped using it. So being first and foremost a consumer, not a fanboy nor a hater, I just returned. My original Pro license waited for me patiently. 2) Since you are talking about "tone"... Your tone in your first post and this post is quite a Karen. You are only ONE customer. Who made you our representative and the right to speak for us? Who told you we want this removed (even if we don't use it, I don't either). It doesn't bother me. It just stays there, who cares. 3) I don't see any threat whatsoever by LT. Maybe you mean "treat", but still, I don't see an issue. 4) LT is a business, as you said. They make things, we buy them, they support them indefinitely ON the price we originally bought them (no service fees). So why would they be grateful, or would we be grateful? $$$ = product. And I bet you have the product already. It is a transaction - as simple as that. Yet, they stand by their clients all right and do it for years (and this is not proven by removing something nobody else asked to remove than entitled-you). 5) Also, since they are a business, it is in the end their choice if they want to actively promote a new feature (their "cloud" system) if it is not too intrusive. So that login up in the corner and the OPTIONAL plugin, is not what I would call "intrusive". 6) Nobody is forcing you to update unRAID to next version. Stay on the current one. Remove unRAID for all we care. 7) If this login button and menu is (or was) a real problem, I am sure someone will step in with a tiny plugin (like the one that widens the interface for super-wide screens), that removes it. Or you can try making such a plugin. 8 ) Back to tone. I am sure if your original post was something like "this thing on the top right about logging in... could you please make hide-able, maybe by a toggle in the settings in some future version, for us OCD people?". This possibly would get a better reply. Cheers.
    5 points
  14. I wonder if it's as simple as the "bluez-firmware: version 1.2" upgrade in 6.10.0-rc1 causing the issue as the NMBluezManager is a different version on the two logs you've attached?
    5 points
  15. One comment on this release. If you're one of the (very rare) users who still leverages the Template Repositories section, this has been entirely removed See here for how to manage your private containers if you used Template Repositories
    5 points
  16. OK we figured it out. There was a bug in 6.9.2 that allowed you to use https://servername.local even though it was not valid for the hash.unraid.net certificate the server was configured to use. And since self-signed certificates also throw errors the browser probably didn't make it clear exactly which error you were accepting. So it would have been tough for you to know that the system was misconfigured in 6.9.2. We are going to tweak the upgrade process so that anyone upgrading from 6.9.2 with USE_SSL=auto will change to USE_SSL=yes in 6.10.0. That will eliminate this problem, and put users in control of whether they want the more secure/restrictive USE_SSL=auto setting.
    4 points
  17. I really like this "webgui: Show IP on VM Manager VM Page"
    4 points
  18. Unfortunately not without diagnostics showing what happened... History lesson: At the beginning of docker introduction into the OS (6.0-beta something), it was originally a directory (and directory only). This however (at the time) imposed a rather strict limitation that the cache drive had to be formatted as BTRFS (at the time there wasn't an XFS (or reiserFS) driver for docker). Since this was rather annoying, the idea of using a BTRFS image came into being as it could be placed onto any particular filesystem without worry. Eventually with 6.9.x the folder idea was one solution to a extraneous writes to SSD problem and it was re-introduced, and it also helps with an eventual integration of ZFS into the system and the folder could also be hosted directly on a ZFS array which will massively increase performance. I'm personally a fan of the folder method as it tends to solve certain problems but it also comes with it's own big caveat. NEVER NEVER NEVER run the New Permission Tool against that folder. You will automatically have to recreate the folder because nothing will work after trashing the permissions.
    4 points
  19. If you need a temporary fix while waiting for 6.10, go to Develop (you will have to enable the Develop menu in Preferences) > Experimental Features and turn off WebGL 2.0.
    4 points
  20. Interesting, it's because that's when the skeleton post for this release was created. As we proceed with development and testing, I update the post as we go along. Normally I do this in a separate internal "test board" and then select/copy/paste into a new post here, but this time I just started it here to begin with and marked it "hidden" and until today when I "un-hid" it.
    4 points
  21. We are not going to remove it and your server functions identically whether you "sign in" or not, with exception of provisioning or renew of a Let's Encypt certificate, which evidently you are not interested in anyway. Nothing is being "pushed down anyone's throats". Just don't sign-in but nothing is exchanged which we don't already know (like your key/GUID) or that we care about (like your server name or LAN IP), those are transmitted for your convenience. Do you use Docker? Do you use plugins? Do you use automatic check for updates? Do you have NTP enabled? All those services contact resources on the internet. And honestly, we are lot more forthcoming in the nature of the data transfer happening than some of those might be. Lastly, out of respect, if anyone wants to discuss this further, please create a separate topic to do so.
    4 points
  22. There is a lot going on in the release, and a lot of good! Some mixed sentiment on the UPC and My Server stuff. Firstly the My Server stuff is fine, an optional additional service people can use to remotely monitor one or more servers. Great stuff useful for those that need or want this. The UPC stuff is a little more complex. I changed my key today, the old way, and it was super simple barely an inconvenience. I'll outline my concerns with this direction, take them as you will. UPC is linking to a forum. It could be that the forum backend is the core authentication system / CRM or the like, but it seems an odd choice to me. If a server is authenticated via UPC an open web socket is maintained. Generally not a big deal, but it's another thing to be exploited and as others have pointed out didn't work out so well for other companies. All information is useful to a hacker, no matter how little data may be captured if there is a breach it is exposing potentially vast configurations, IPs, and so on. On the configuration backups, why a private repo? This seems odd to me, are these encrypted per server? Wouldn't just end to end encrypted file blobs be more secure, regardless of saying "it doesn't include files with sensitive info". No company regardless of design or merit is immune to breaches, hacks, or acquisitions. While it's clear now that if you have a valid key you do not need to authenticate with UPC (forum), this is pretty much how all non-cloud authentications go to die. I've seen, you've seen it... And I get it, from a business perspective, it's easier for you to manage centrally, oversee, and move towards the subscription model. Confidence that a path like this isn't in the future would ease many, especially in the area of data storage where moving is not always trivial. Are you GDPR compliant, or similar data protection schemes (kind of not specific to the release, just generally) Are you ISO27001 and SOC certified such that we can be sure your development pipelines to your infrastructure won't be compromised with active connections to our servers? These are my concerns, the features and functions of Unraid in this release are great. Thanks for the work put into them
    4 points
  23. That works, I have also tried yesterday to add the following to `go` file: /usr/bin/sed -i -e 's/#HandleLidSwitch=suspend/HandleLidSwitch=ignore/g' /etc/elogind/logind.conf /etc/rc.d/rc.elogind restart This will not work during boot since the laptop already sleeps until go file is executed, if I wake up the laptop manually after it sleeps during boot it will not get back to sleep. Is there a way to make the change before `elogind` runs?
    4 points
  24. 4 points
  25. Can I please ask limetech for some FAQ or written details around the existing users / licenses behaviors / expectations / changes in light of this upgrade? Is really not clear to me who does what, just assumptions at this point. I for one, will opt out from associating any of my licenses with this forum credentials and that's a show stopper for me. I value my privacy and my control more than any social or cloud services and I will not sign my life away down the road to some vague license agreement. Not pointing at limetech but tech history proved over and over again that we're going down a very slippery slope when extend our own devices over some fashion of cloud services. I simply don't trust that model, full, stop, period. This is not what I signed up for and I would like to keep it that way. I can appreciate some of the business benefits explained and I respect that, but also one have to respect our privacy.
    4 points
  26. "Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key. All key purchases and upgrades are also handled exclusively via the UPC." I do also think this needs more clarification for current users who don't want to sign or associate their servers with UPC regarding key management. How it will be handled in the future etc...
    4 points
  27. Where do you think this is "heading"? Any "cloud" services and features we offer are, and will continue to be completely "opt in" with the default being "opt out".
    4 points
  28. Until now every Unraid 6.x version relied on traditional polling of the server to update the GUI in real-time. On the Dashboard there are multiple fields which are getting updated regularly. It is the task of the browser to initiate each time a poll request to obtain the new information and update the GUI accordingly. Polling puts load on both the browser and server, and may consume more memory over time (depending on the browser). Starting with Unraid version 6.10 the traditional polling mechanism is replaced by a websocket event driven model using Nchan. An event driven model has a number of key advantages. - It allows the server to send information when changes take place (better efficiency) - Multiple clients can be served at the same time without huge impact on the server load (better scalability) - A client only needs to act when new information is received (better responsiveness) The event driven model also solves the issue of stale sessions when people open multiple browsers (on different computers) and forget to close them after usage. This resulted in csrf token mismatches when the server was restarted. So far all testing with the event driven model looks very promising and a solid improvement!
    4 points
  29. Default poll interval dates back a number of years. It was chosen to minimize video "glitching" in lower-performance servers - Atom processors, 4G or less of RAM, older hard drives with small caches. These days I think something like 30 seconds would be better. Then if someone posts that they are seeing video glitches every 30 sec we can suggest raising the value.
    3 points
  30. A couple that you might look at. I tried to pick ones that might have multi-language support and with a minimum of licensing restrictions. ============================= =================
    3 points
  31. This is already updated for the next release to highlight line rather than change colour.
    3 points
  32. Try this, looks like the same issue, and it worked also on a Dell: https://forums.unraid.net/topic/119502-bzimage-checksum-error/?do=findComment&comment=1120488
    3 points
  33. I just wiped unraid and did a fresh install like 4 hours ago...I wish this was like 6 hours earlier lol
    3 points
  34. The release of rc4 felt in between PRs for highlighting. In the latest PR highlighting is done by changing the font color instead of the background, this is less intrusive. Also dashboard should not show highlighting, this was unintentional in the earlier PR. See the latest version of the Dynamix File Manager to see the intended highlighting in action.
    3 points
  35. Yes the project was rebranded as "moby" which requires our build procedure to change.
    3 points
  36. After a long wait, I made the necessary fix for this (together with some other enhancements). Should be available in the next rc of 6.10.
    3 points
  37. I have been using Unraid since 6.1.8, and I believe I've been experiencing a similar issue with 6.9.2 This year in June I upgraded my motherboard & CPU (built in 2015: Asrock H97 Pro4S, Xeon E3-1231v3 24GB 1600 ram, upgraded this year to: Asrock Z170S, i5-7600k, 16GB 3200 ram) and I had upgraded specifically for the Intel QuickSync hardware transcoding. On the Xeon hardware, the server was perfectly stable, but it was at its limit in terms of software transcoding, hence the upgrade. After the upgrade, I started noticing frequent crashes occurring more & more frequently -- at first once per month, then once per week, and now every few days. I thought I had successfully troubleshooted (troubleshot?) the issue when I noticed the NTP server was causing a kernel panic. I found this after I set up a syslog server on a raspberry pi I had lying around. Unfortunately, even after disabling NTP entirely, the crashes persisted, but now there was no trace of any issues in the syslog. My raspberry pi is also a pihole, so I am able to see when the DNS requests cease, and that the server crashes most frequently in the early hours of the morning, but beyond that I'm stumped. This morning, I found the threads posted by @Tristankin, and rather than downgrade back to 6.8.3, I decided to experiment by commenting out the # modprobe i915 line in my go file. I'm hoping that the server continues to function, and I think I'll be able to make do with software transcoding for the time being, but I would like very much for this issue to be resolved. Happy to provide any details as necessary.
    3 points
  38. With all due respect, have you addressed the UPC / login option located in the upper right of the webGUI header? Give us an option to take it off, remove it? I don't care to log in, I don't care for the cloud intrusion in my personal life, I don't care to see it, full stop period, regardless of your business case. And I am very unhappy how some of these intrusive feature are being pushed down our throats. I just want it off my GUI header and I don't want anything to do with unraid cloud service as working offline (OFF THE GRID) is my primary priority. Can we have that option?
    3 points
  39. I was having a lot of issues with transcodes on Intel iGPU on Unraid 6.9.2 so I upgraded to the RC to see if it would help and ran into this exact issue. UPDATE: Plex server version 1.25.0.5220 solves the issue. If using linuxserver.io's container, just make sure your VERSION environment variable is set to 'latest' and you should get it. Previous version of this post is quoted below, but the info is no longer relevant.
    3 points
  40. Agree, no risk like this is acceptable.
    3 points
  41. Thought I'd give an update. My system has an 11th Gen i9-11900K. In Unraid 6.9.2 (based on Linux kernel 5.10.28), I created this file on the flash: config/modprobe.d/i915.conf containing this text to activate the experimental i915 drivers for this GPU: options i915 force_probe=4c8a and Plex was able to do hardware transcoding. In some of the earlier private betas of 6.10, this worked as well. Starting with 6.10.0-rc1 (kernel 5.13.8) Plex was unable to do hardware transcoding on this system (it works on 9th and 10th gen Intel CPUs, just not 11th gen.) Internally today we are up to kernel 5.13.12 and Plex still will not do hardware transcoding on this system. In the 'Plex Media Server.log' it reports: TPU: hardware transcoding: enabled, but no hardware decode accelerator found On the plus side, you no longer need to create an i915.conf file with those custom options, the GPU activates right out of the box. And an interesting data point, this Jellyfin docker does hardware transcoding beautifully on the 6.10 rc's: https://forums.unraid.net/topic/102787-support-ich777-jellyfin-amdintelnvidia/ Now I'm not suggesting that die hard Plex fans need to switch to Jellyfin, I don't intend to. Just saying that the Linux drivers for the latest Intel CPU/GPUs are still in flux and for whatever reason, Jellyfin works with them and Plex does not. I do not know if a future Linux kernel will solve the problem, or if it will take an update from Plex. But I do not have high hopes for the current version of Plex doing hardware transcoding in rc2 on the latest Intel CPUs. Update - For completeness I will add that I am using the LSIO Plex Container: https://forums.unraid.net/topic/40463-support-linuxserverio-plex-media-server/ and Plex itself is currently (as of 8/25/21) version 1.24.1.4931. I have a Plex Pass.
    3 points
  42. Sure we can make that change for rc2
    3 points
  43. Yes a detailed doc is forthcoming. It's going to say: if you have not installed the 'My Servers' plugin then no interaction with outside servers takes place with one exception: If you download a Let's Encrypt SSL cert then a background daemon is activated which updates the DNS A-record on our DNS server, and also wakes up every 24 hours to see if time to auto-renew the cert. If you don't want this to happen, then don't download a LE cert. Note you can always create a new Forum account during the Sign-in/Sign-up process dedicated to this purpose.
    3 points
  44. 👍 I don't understand this part. Is it still possible to use a paid license without internet access or not? And why is it needed to have an account for security-related notifications? Why don't you simply use the e-mail address which was used to buy the license (or the newsletter)?! So I'm forced to use My Servers if I want to receive security notifications?! And how is it possible to pull data from my server if I did not open any ports? You explained it through a reverse-proxy relay. This means a registered server has a 24/7 connection to the relay?! Qnap and Ubiquiti proved that it is a bad idea to use such services and having a random DDNS url with a random port is only security through obscurity. This is why I don't plan to use My Servers.
    3 points
  45. It doesn't matter, both scenarios work. WireGuard keeps on working as before with your current settings
    3 points
  46. Manged to catch this today. With the lightest of google searches it looks like it may be a bug/regression in the kernel. I very well could be wrong but maybe? https://askubuntu.com/questions/1293945/20-10-complete-system-freeze-with-general-protection-fault-smp-nopti https://www.spinics.net/lists/linux-nfs/msg78091.html https://www.spinics.net/lists/amd-gfx/msg48596.html Jun 12 14:00:01 thelibrary kernel: Jun 12 14:00:44 thelibrary kernel: general protection fault, probably for non-canonical address 0x1090000ffffff76: 0000 [#1] SMP NOPTI Jun 12 14:00:44 thelibrary kernel: CPU: 6 PID: 10937 Comm: qbittorrent-nox Tainted: P S W O 5.10.28-Unraid #1 Jun 12 14:00:44 thelibrary kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470D4U, BIOS L4.21 04/15/2021 Jun 12 14:00:44 thelibrary kernel: RIP: 0010:nf_nat_setup_info+0x129/0x6aa [nf_nat] Jun 12 14:00:44 thelibrary kernel: Code: ff 48 8b 15 ef 6a 00 00 89 c0 48 8d 04 c2 48 8b 10 48 85 d2 74 80 48 81 ea 98 00 00 00 48 85 d2 0f 84 70 ff ff ff 8a 44 24 46 <38> 42 46 74 09 48 8b 92 98 00 00 00 eb d9 48 8b 4a 20 48 8b 42 28 Jun 12 14:00:44 thelibrary kernel: RSP: 0018:ffffc90000338700 EFLAGS: 00010202 Jun 12 14:00:44 thelibrary kernel: RAX: ffff88818b422f06 RBX: ffff888108b21a40 RCX: 0000000000000000 Jun 12 14:00:44 thelibrary kernel: RDX: 01090000ffffff76 RSI: 000000003f50ed19 RDI: ffffc90000338720 Jun 12 14:00:44 thelibrary kernel: RBP: ffffc900003387c8 R08: 0000000098f45bae R09: ffff88813dd40620 Jun 12 14:00:44 thelibrary kernel: R10: 0000000000000348 R11: ffffffff815cbe4b R12: 0000000000000000 Jun 12 14:00:44 thelibrary kernel: R13: ffffc90000338720 R14: ffffc900003387dc R15: ffffffff8210b440 Jun 12 14:00:44 thelibrary kernel: FS: 0000146c98419700(0000) GS:ffff88881e980000(0000) knlGS:0000000000000000 Jun 12 14:00:44 thelibrary kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 12 14:00:44 thelibrary kernel: CR2: 0000150d3d688320 CR3: 000000020149a000 CR4: 0000000000350ee0 Jun 12 14:00:44 thelibrary kernel: Call Trace: Jun 12 14:00:44 thelibrary kernel: <IRQ> Jun 12 14:00:44 thelibrary kernel: ? fq_enqueue+0x25b/0x4e8 Jun 12 14:00:44 thelibrary kernel: ? igb_xmit_frame_ring+0x7c5/0x8fd [igb] Jun 12 14:00:44 thelibrary kernel: ? __ksize+0x15/0x64 Jun 12 14:00:44 thelibrary kernel: ? krealloc+0x26/0x7a Jun 12 14:00:44 thelibrary kernel: nf_nat_masquerade_ipv4+0x10b/0x131 [nf_nat] Jun 12 14:00:44 thelibrary kernel: masquerade_tg+0x44/0x5e [xt_MASQUERADE] Jun 12 14:00:44 thelibrary kernel: ? __qdisc_run+0x21d/0x3c9 Jun 12 14:00:44 thelibrary kernel: ipt_do_table+0x51a/0x5c0 [ip_tables] Jun 12 14:00:44 thelibrary kernel: ? __dev_queue_xmit+0x4d9/0x501 Jun 12 14:00:44 thelibrary kernel: ? fib_validate_source+0xb0/0xda Jun 12 14:00:44 thelibrary kernel: nf_nat_inet_fn+0xe9/0x183 [nf_nat] Jun 12 14:00:44 thelibrary kernel: nf_nat_ipv4_out+0xf/0x88 [nf_nat] Jun 12 14:00:44 thelibrary kernel: nf_hook_slow+0x39/0x8e Jun 12 14:00:44 thelibrary kernel: nf_hook+0xab/0xd3 Jun 12 14:00:44 thelibrary kernel: ? __ip_finish_output+0x146/0x146 Jun 12 14:00:44 thelibrary kernel: ip_output+0x7d/0x8a Jun 12 14:00:44 thelibrary kernel: ? __ip_finish_output+0x146/0x146 Jun 12 14:00:44 thelibrary kernel: ip_forward+0x3f1/0x420 Jun 12 14:00:44 thelibrary kernel: ? ip_check_defrag+0x18f/0x18f Jun 12 14:00:44 thelibrary kernel: ip_sabotage_in+0x43/0x4d [br_netfilter] Jun 12 14:00:44 thelibrary kernel: nf_hook_slow+0x39/0x8e Jun 12 14:00:44 thelibrary kernel: nf_hook.constprop.0+0xb1/0xd8 Jun 12 14:00:44 thelibrary kernel: ? l3mdev_l3_rcv.constprop.0+0x50/0x50 Jun 12 14:00:44 thelibrary kernel: ip_rcv+0x41/0x61 Jun 12 14:00:44 thelibrary kernel: __netif_receive_skb_one_core+0x74/0x95 Jun 12 14:00:44 thelibrary kernel: netif_receive_skb+0x79/0xa1 Jun 12 14:00:44 thelibrary kernel: br_handle_frame_finish+0x30d/0x351 Jun 12 14:00:44 thelibrary kernel: ? br_pass_frame_up+0xda/0xda Jun 12 14:00:44 thelibrary kernel: br_nf_hook_thresh+0xa3/0xc3 [br_netfilter] Jun 12 14:00:44 thelibrary kernel: ? br_pass_frame_up+0xda/0xda Jun 12 14:00:44 thelibrary kernel: br_nf_pre_routing_finish+0x23d/0x264 [br_netfilter] Jun 12 14:00:44 thelibrary kernel: ? br_pass_frame_up+0xda/0xda Jun 12 14:00:44 thelibrary kernel: ? br_handle_frame_finish+0x351/0x351 Jun 12 14:00:44 thelibrary kernel: ? nf_nat_ipv4_pre_routing+0x1e/0x4a [nf_nat] Jun 12 14:00:44 thelibrary kernel: ? br_nf_forward_finish+0xd0/0xd0 [br_netfilter] Jun 12 14:00:44 thelibrary kernel: ? br_handle_frame_finish+0x351/0x351 Jun 12 14:00:44 thelibrary kernel: NF_HOOK+0xd7/0xf7 [br_netfilter] Jun 12 14:00:44 thelibrary kernel: ? br_nf_forward_finish+0xd0/0xd0 [br_netfilter] Jun 12 14:00:44 thelibrary kernel: br_nf_pre_routing+0x229/0x239 [br_netfilter] Jun 12 14:00:44 thelibrary kernel: ? br_nf_forward_finish+0xd0/0xd0 [br_netfilter] Jun 12 14:00:44 thelibrary kernel: br_handle_frame+0x25e/0x2a6 Jun 12 14:00:44 thelibrary kernel: ? br_pass_frame_up+0xda/0xda Jun 12 14:00:44 thelibrary kernel: __netif_receive_skb_core+0x335/0x4e7 Jun 12 14:00:44 thelibrary kernel: __netif_receive_skb_one_core+0x3d/0x95 Jun 12 14:00:44 thelibrary kernel: process_backlog+0xa3/0x13b Jun 12 14:00:44 thelibrary kernel: net_rx_action+0xf4/0x29d Jun 12 14:00:44 thelibrary kernel: __do_softirq+0xc4/0x1c2 Jun 12 14:00:44 thelibrary kernel: asm_call_irq_on_stack+0x12/0x20 Jun 12 14:00:44 thelibrary kernel: </IRQ> Jun 12 14:00:44 thelibrary kernel: do_softirq_own_stack+0x2c/0x39 Jun 12 14:00:44 thelibrary kernel: do_softirq+0x3a/0x44 Jun 12 14:00:44 thelibrary kernel: __local_bh_enable_ip+0x3b/0x43 Jun 12 14:00:44 thelibrary kernel: ip_finish_output2+0x2ec/0x31f Jun 12 14:00:44 thelibrary kernel: ? ipv4_mtu+0x3d/0x64 Jun 12 14:00:44 thelibrary kernel: __ip_queue_xmit+0x2a3/0x2df Jun 12 14:00:44 thelibrary kernel: __tcp_transmit_skb+0x845/0x8ba Jun 12 14:00:44 thelibrary kernel: tcp_connect+0x76d/0x7f4 Jun 12 14:00:44 thelibrary kernel: tcp_v4_connect+0x3fc/0x455 Jun 12 14:00:44 thelibrary kernel: __inet_stream_connect+0xd3/0x2b6 Jun 12 14:00:44 thelibrary kernel: inet_stream_connect+0x34/0x49 Jun 12 14:00:44 thelibrary kernel: __sys_connect+0x62/0x9d Jun 12 14:00:44 thelibrary kernel: ? __sys_bind+0x78/0x9f Jun 12 14:00:44 thelibrary kernel: __x64_sys_connect+0x11/0x14 Jun 12 14:00:44 thelibrary kernel: do_syscall_64+0x5d/0x6a Jun 12 14:00:44 thelibrary kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 12 14:00:44 thelibrary kernel: RIP: 0033:0x146c9bdec53b Jun 12 14:00:44 thelibrary kernel: Code: 83 ec 18 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 bb fa ff ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 f1 fa ff ff 8b 44 Jun 12 14:00:44 thelibrary kernel: RSP: 002b:0000146c98416f20 EFLAGS: 00000293 ORIG_RAX: 000000000000002a Jun 12 14:00:44 thelibrary kernel: RAX: ffffffffffffffda RBX: 0000146c90d18c60 RCX: 0000146c9bdec53b Jun 12 14:00:44 thelibrary kernel: RDX: 0000000000000010 RSI: 0000146c90e4ac94 RDI: 000000000000004b Jun 12 14:00:44 thelibrary kernel: RBP: 0000146c98417160 R08: 0000000000000000 R09: 0000146c98418258 Jun 12 14:00:44 thelibrary kernel: R10: 0000146c9841710c R11: 0000000000000293 R12: 0000146c90e4ac94 Jun 12 14:00:44 thelibrary kernel: R13: 0000000000000000 R14: 0000146c98418258 R15: 0000146c90003310 Jun 12 14:00:44 thelibrary kernel: Modules linked in: nvidia_uvm(PO) xt_nat xt_tcpudp veth macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nvidia_drm(PO) nvidia_modeset(PO) drm_kms_helper drm backlight agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia(PO) ip6table_filter ip6_tables iptable_filter ip_tables x_tables igb i2c_algo_bit ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd wmi_bmof kvm crct10dif_pclmul crc32_pclmul crc32c_intel mpt3sas ghash_clmulni_intel aesni_intel i2c_piix4 crypto_simd cryptd raid_class i2c_core nvme ahci scsi_transport_sas nvme_core wmi glue_helper acpi_ipmi ccp k10temp rapl libahci button ipmi_si acpi_cpufreq [last unloaded: i2c_algo_bit] Jun 12 14:00:44 thelibrary kernel: ---[ end trace 98e92523c69e7e44 ]--- Jun 12 14:00:44 thelibrary kernel: RIP: 0010:nf_nat_setup_info+0x129/0x6aa [nf_nat] Jun 12 14:00:44 thelibrary kernel: Code: ff 48 8b 15 ef 6a 00 00 89 c0 48 8d 04 c2 48 8b 10 48 85 d2 74 80 48 81 ea 98 00 00 00 48 85 d2 0f 84 70 ff ff ff 8a 44 24 46 <38> 42 46 74 09 48 8b 92 98 00 00 00 eb d9 48 8b 4a 20 48 8b 42 28 Jun 12 14:00:44 thelibrary kernel: RSP: 0018:ffffc90000338700 EFLAGS: 00010202 Jun 12 14:00:44 thelibrary kernel: RAX: ffff88818b422f06 RBX: ffff888108b21a40 RCX: 0000000000000000 Jun 12 14:00:44 thelibrary kernel: RDX: 01090000ffffff76 RSI: 000000003f50ed19 RDI: ffffc90000338720 Jun 12 14:00:44 thelibrary kernel: RBP: ffffc900003387c8 R08: 0000000098f45bae R09: ffff88813dd40620 Jun 12 14:00:44 thelibrary kernel: R10: 0000000000000348 R11: ffffffff815cbe4b R12: 0000000000000000 Jun 12 14:00:44 thelibrary kernel: R13: ffffc90000338720 R14: ffffc900003387dc R15: ffffffff8210b440 Jun 12 14:00:44 thelibrary kernel: FS: 0000146c98419700(0000) GS:ffff88881e980000(0000) knlGS:0000000000000000 Jun 12 14:00:44 thelibrary kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 12 14:00:44 thelibrary kernel: CR2: 0000150d3d688320 CR3: 000000020149a000 CR4: 0000000000350ee0 Jun 12 14:00:44 thelibrary kernel: Kernel panic - not syncing: Fatal exception in interrupt
    3 points
  47. sure, let me zip up and send you DM, i don't want people downloading until we get a confirmed use case.
    3 points