Jump to content

testdasi

Members
  • Content Count

    2811
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by testdasi

  1. For (3) an safer alternative rather than enabling disk share universally is to have custom SMB config file pointing to a top level folder on a disk (e.g. for a share called sharename, have custom SMB config pointing to /mnt/cache/sharename or /mnt/disk1/sharename). Then have the SMB Extras in SMB Settings "include" that config file. That way you just need to restart SMB to change the config file (instead of needing to stop the array to change SMB Extras). Works really well with my cache-only nvme-raid0 share. More detailed guide: Let's say you have a cache-only share called "sharename" that you want a user called "windows" to access via SMB with shfs-bypass. Create a smb-custom.conf with the content below and save it in /boot/config [sharename-custom] path = /mnt/cache/sharename comment = browseable = no Force User = nobody valid users = windows write list = windows vfs objects = Then with the array stopped -> Settings -> SMB -> add this line to Samba extra configuration box: include = /boot/config/smb-custom.conf Apply, done, start array. You can now access the bypassed share at \\tower\sharename-custom or \\server-ip\sharename-custom Some hints It's critical that the name of the bypassed share (e.g. sharename-custom) is DIFFERENT from the normal share name or you will run into weird quirks i.e. Unraid share conflicts with your custom share. To add more shares, just copy-paste the above block in the smb-custom.conf and make appropriate changes (e.g. name, path, user), save and then restart SMB. No need to stop array. Similarly, for edit, just edit smb-custom.conf, save and restart SMB.
  2. There shouldn't be any gotchas. Compare the folder structure of these: Telegraf docker: the host folder that corresponds to /var/lib/influxdb GUS: the host folder that corresponds to /data/influxdb They should look identical in terms of structure. If that is confirmed then just turn the dockers off, backup the data before proceeding further (if the data is important to you), delete the existing GUS /data/influxdb content and then just copy the Telegraf /var/lib/influxdb data over (ensuring no change to the previous folder structure). I suggest to use mc from command line (or Krusader or similar 2-panel docker) so it looks a lot more obvious.
  3. Yep. Specified that it's 1.3 now. I'll keep an eye out for v1.4.
  4. @Hoopster: the latest version of GUS has all the configs enabled, including inputs.apcupsd. However, it won't delete the old Telegraf config. You just need to delete the telegraf.conf file and update to latest version (and restart the docker if already updated) and it should work.
  5. Update (23/09/2020): Grafana Unraid Stack changes: Expose Influxdb RPC port and change it to a rarer default value (58083) instead of the original common 8088. Added falconexe's Ultimate UNRAID Dashboard Thanks. It's done. The GUS dashboard is based on Threadripper 2990WX. You will have to customize the default dashboard to suit your own exact hardware. Also give UUD a try to see if you like that layout more.
  6. I hate it when apps do that. That 8088 is for Influx backup / restore but their config file doesn't allow disabling that if not used. And to make it worse, they use a rather common value of 8088. Sounds like something on the to do list. I'll have to add that to the expose port so it's transparent to people (and probably pick a different port from 8088 - I'm probably just gonna pick 58083 or something random like that).
  7. Show me your docker settings please. Also go to the folder you map to /config and look for influxd.log under influxdb folder and attach it here. Hopefully it tells me what's wrong.
  8. You can either edit the graph to change the parameters to use hddtemp or alternatively just wipe your config folder and reinstall with USE_HDDTEMP=no. The panels use SMART, not HDD_Temp. I only included the option because some prefer it over SMART (which is why it defaults to no). I kinda wonder if I should make a UUD edition that includes @falconexe's dashboard. That looks pretty damn sleek out of the box. Try use host network and in the nginx config file, change: set $upstream_app grafana; set $upstream_port 3000; to set $upstream_app 192.168.0.2; set $upstream_port 3006; (Replace 192.168.0.2 with the actual IP of your Unraid server). With bridge network (including custom), you have to map the ports yourself (it's the "Add blablabla" at the bottom of the Docker edit GUI). But that shouldn't be necessary with host network.
  9. You just edit add more path mappings in the Unraid GUI (from Dashboard, click on Docker then Edit then scroll to the bottom for the + Add blabla option). The default mapping is for 1 mapping to docker /config (settings) and 1 mapping to /data (watch, downloads etc.) just for simplicity. The one I'm using on my server, I have individual mappings for each /data subfolder so for example e.g. /data/rtorrent/watch, /data/rtorrent/incomplete and /data/rtorrent/complete all point to different folders on the host (they are on different pools on my server). Note that if you map subfolders then you can't map the parent. Settings should not reset after restart, btw. Mine is all fine so you might have done incorrect path mappings. Please attach log.
  10. Quoting from your post, I wouldn't call this working. In any case, you are the first report of a primary RX580 pass-through working (albeit intermittently) that I know of so maybe AMD is finally starting to fix stuff. "Think some luck is involved, after starting the VM, and seeing a black screen, I went on to reading forums on the other computer. Prob after couple minutes delay the screen just came on... I tried to passthrough the keyboard and mouse afterwards (quite straight forward, just 2 checkboxes in VM settings), that seems to have messed with the GPU passthrough which didnt work for a while (even when all the settings were the same as before, when it did work :s). Anyways, after a few VM restarts, everything seems to work again................... Luck I tell you, this doesnt make sense to me...."
  11. Plex support specifically mentioned remote access is encrypted. I guess you can use a Reverse Proxy if you don't trust their words. https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/ Also even with encryption, your ISP will know you are streaming stuff if they bother to look, just by the pattern and amount of data transfer. Encryption just stops them from knowing WHAT you stream.
  12. Binhex has implemented multi-remote functionality (see post below). I have deprecated my docker - it was intended as a temp workaround while waiting for binhex anyway.
  13. The high level instruction is login (default is admin/admin) then hover mouse over the + sign and pick Import. Then upload the json file from UUD topic.
  14. I don't have a UPS so unfortunately can't really test adding ups functionality. Installing the apcupsd exporting script is (somewhat) trivial but without actual device to test, it's pure luck if anything works. You are probably better off installing the apcupsd-influxdb-exporter docker from the Apps page and point it to your Gus docker IP + 8086 port. Have a look at this guide to see if it helps. You will also have to read up a bit on how to edit grafana dashboard / panel to update the queries. Each person's hardware has some unique parameters (e.g. which sensor to read CPU temperature), making a completely hands-off dashboard virtually impossible. Usually it just involves picking a few values from the drop-down to see which one makes the most sense. The loop is intentional to make sure a vpn connection is established before anything else is run. Assuming your VPN server is working and no issue with Internet connection then the most likely reason is an issue with the ovpn config file. The most frequent mistake is missing credentials (i.e. login). Create a file e.g. login.txt with exactly 2 lines, 1st line is username, 2nd line is password. Save that file in the same folder as the openvpn.ovpn. Then edit your openvpn.ovpn and find auth-user-pass line and add login.txt after it so it's like this: ... auth-user-pass login.txt ... If that still doesn't work then copy-paste your openvpn.ovpn file here and I can help have a look.
  15. Whether it's possible or not depends on whether your hardware requires UEFI or not. Some rare hardware just wouldn't boot properly without UEFI so in most cases, Legacy ("BIOS") boot is an option. That may or may not fix the issue but worth a try.
  16. 🤣 ahhh nostalgia! I don't use airsonic specifically but I can answer in more general terms. OpenVPN server is generally better for admin-level stuff as it allows you access to everything. It's like the door to your house. If you just want to access a few services, especially if that service has a Web UI, then Reverse Proxy is better as it is basically specialised for web stuff. So needless to say, AirSonic should be done through Reverse Proxy. For Plex, you don't need a reverse proxy. Plex has built-in support for remote access so you can stream your own stuff through Plex.tv.
  17. The RX580 generally can only be passed through if the BIOS boots Unraid on a different (primary) graphic card. There isn't any resolution since the issue lies in the card.
  18. That is mostly a BIOS function since a shutdown is kinda the same with all OS. You can test it with a bare metal Windows or a Ubuntu USB stick to see if there's any diff. If there's a diff with the test then the quirk may be to do with UEFI boot vs Legacy boot.
  19. Reattach new diagnostics. Also read the release notes for 6.9.0-beta25, the "virtio-net" section for more details.
  20. If it's from the same repo (e.g. "steefdebruijn/docker-roonserver") then no diff. What he did was just to create Unraid template for the docker so the necessary mappings are visible.
  21. Update (21/09/2020): OpenVPN-based dockers now will crash out if the user doesn't provide an ovpn file as per instructions. Deprecated rutorrent-plus-plus as binhex has implemented multi-remote functionality. Please use his docker instead. Added Grafana Unraid Stack Quick screenshot:
  22. That shouldn't happen. I tested specifically for that scenario. It's like doing car crash prevention technology. It has to assume you wear a seatbelt and build additional safety around that assumption e.g. some of the emergency braking is so sudden that at sufficient speed, you can break a few rib crashing into the steering wheel without wearing a seatbelt. So in this particular case, I provided specific instructions that say "put on a seatbelt" and "DON'T FORGET THE SEATBELT" reminder so I assume people already wear a seatbelt. Completely different scenarios. The new logic would not start the engine if there's no seatbelt.
  23. Thanks for reporting. I fixed that. I was assuming users would follow the instructions (even added reminder "DON'T FORGET THE OVPN FILE!!!" in the docker description) but I guess just crashing the docker is a better approach.
  24. Check out my Pi-Hole DoT DoH docker. 😉
  25. Update (18/09/2020): Added OpenVPN HyRoSa docker Recoded HyDeSa and HyRoSa to use centralised static repo Coded a Web quick launcher for HyDeSa and HyRoSa