JimmyGerms

Members
  • Posts

    40
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

JimmyGerms's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. Would you mind going over how you manually edited that? I'd love to get a successful export to one of my drives even if it's a temporary fix.
  2. I am also getting this error from one of my drives while exporting. Was on Blake2 but recently switched to Blake3 with the same result. Have not tried the other methods. Crazy thing is, I have green checkmarks across the board but I got that fatal error on export. Would love to know what to tweak to fix the issue as well!
  3. I don't know what I have set but I'm still on version L2.32 and have normal MB temps and I also have Turbo Boost enabled. I did hit that temp issue once in the past but have not had it since. No errors in the logs either. I wish I could tell you what it is but when I got the board over a year ago all I did was clear cmos (with battery removed) updated the bios and enabled the iGPU...I have no idea why I'm having such luck. Anything extra you guys got going on that I may not be running/have set?
  4. Oh geez, I'm a dummy. I added the custom port the the vpn container but I completely forgot to add it to the VPN_Input_Ports variable. Ignore me haha!
  5. Hey there, I wanted to ask the question if anyone was able to get this docker running when piped through a container VPN. I'm not able to get to the interface if I have it running through binhex-DelugeVPN. Seems like the docker only works when it's in bridge mode?
  6. I've got a crazy scenario playing out after I updated to the latest version last night, 12.7.2021. I cannot reach the unraid GUI after a reboot if I'm on latest. I had to manually delete the plugin and roll back to version 12.6.2021. Best thing is, I cannot diagnose anything as it's not even outputting to syslogs. I get to the Unraid GUI select screen but then the system just hangs after running normally. I can get to the GUI if I boot into safemode aka no plugins loaded. Anyone else experiencing issues like this? I also rebuilt and checked/repaired the USB drive. The key element that keeps me from getting a clean boot with plugins loaded is the latest unassigned.devices after painfully going through each plugin 1 by 1
  7. Thanks for the reply! The case I'm trying to solve is secure user access for my family to NextCloud from locations outside the home network (Maybe sonarr and radarr down the line too). I don't think I want remote access to the server itself yet but if I do I'm going to set that up through wireguard vpn (is that correct?) What's pulling me to LDAP are the walkthroughs and videos I've been looking at. Most say that LDAP is the recommended way to setup? The last constraint I want to work around is to setup everything using the domain I own. No other paid services other than the domain registration. Let me know if I've answered your queries @mattz!
  8. After reading lots more tutorials and watching more YouTube videos, I think I'm going to setup Authelia with SWAG using this tutorial: https://blog.linuxserver.io/2020/08/26/setting-up-authelia/ I'd also like to setup LDAP but I'm finding it a bit complicated to setup/understand. Could anybody point me in the right direction for setting this up in a docker for unraid if you own your own domain? I believe I need OpenLDAP and LDAP Auth but I'm not sure how to set them up. I'll continue to read the projects documentation in the mean time and try out some configs this weekend! Thanks for reading!
  9. HA! Yup, checking the help it does say "using the 'sensors-detect' script". I didn't think it would be that easy! Thanks everyone and sorry for the beginner questions I'm still stumbling my way around unraid!
  10. This was happening to me too. Had to do a hard reset on the server and after that coretemp showed up for me. May I ask how you were able to run sensor-detect in terminal?
  11. I'm hoping this is in the right location. I've been doing lots of searching on the forums, googling and watching SpaceInvader One's videos for setting up reverse proxies and have successfully gotten things up and running but I need a bit of clarity on what is exposed to the internet. I've read that opening ports 80 and 443 from your router is not the best thing to do which swag requires. But on the other hand, I've read that it's ok if it's more isolated to individual docker containers. If this is not the best way to do this what would be? Please let me know if there is further documentation I could read about best ways to setup safe remote access. My overall goal is to setup NextCloud for home use but fear the risk of exposing too much to the internet. Thanks for reading and looking forward to learning more!
  12. Hey @eafx! Thanks for all the help. I'll grab some screenshots this week and update my post. Where I'm at now, everything is working and rebuilding correctly when the master container has an issue but I have noticed that the CPU pinning in the xml templates isn't getting applied when the in scope containers are rebuilt. I looked at ParseDockerTemplate.sh on GitHub and it's not grabbing the <CPUset>. Also, let me know if I should be making bugs on GitHub for this. I'm a bit new to the workflow. EDIT: Solved my issue by updating ParseDockerTemplate.sh with this code: add_cpuset(){ status=0 xmllint --noout --xpath "//CPUset/text()" $xmlFile > /dev/null 2>&1 status=$? if [[ $status == 0 ]]; then cpus=$(xmllint --xpath "//CPUset/text()" $xmlFile) docker_string+=" --cpuset-cpus=\"$cpus\"" [ "$verbose" = "1" ] && echo "Found CPU Pinning: $cpus" fi } Then altered the main call to add the function like so: #Main - Call each function #Each function adds to the 'docker run' argument #list, based on what is in the .xml file. docker_string="$docker" add_name add_net #Adding CPU Pinning Detection add_cpuset add_ip add_privileged add_envars add_timezone add_ports add_volumes add_extraparams add_repository
  13. Ok so I switched it out of using the VPN as its network mode and back to bridge. Now I get this error when the cron job runs. Maybe I didn't quite understand the readme and how to set this up. /usr/bin/docker: Error response from daemon: Container cannot be connected to network endpoints: container:binhex-delugevpn, none. I have each container setup with prerequisite #2. Can the network type not be set to "None"? "--net=container:master_container_name" Now I'm getting lots of orphaned containers upon Rebuild-DNDC running. Edit: Turns out it does not like prerequisite #2. Adding a custom network with the container name gives me no issues. I followed SpaceInvader's tutorial on using --net=container: and setting network type to none, maybe I made a mistake in here?
  14. Hi @eafx! Thanks for the reply. I ended up moving away from the NordVPN container and landed with binhex-delugeVPN. I got RebuildDNDC to sort of work now. As long as it creates the endpoints at first startup everything is good. BUT, if the EndpointID's don't match (ex: caused by a reboot) RebuildDNDC will start to repair the containers then just stop itself and never finish the rebuild. Last thing I see in the logs is this: D. PROCESSING: IN-SCOPE CONTAINERS ---------------------------- Stopping: Rebuild-DNDC ---------------------------- At part B, I don't think it's able to rebuild the VPN container either as the VPN's logs do not show a restart in the container. Not too sure what's going on at this point. Maybe a privilege issue that RebuildDNDC cannot kill and restart containers? Any thoughts would be greatly appreciated! Thanks so much for reading and your time!
  15. This may be a dumb question but using the wireguard option is there any way to get DelugeVPN to cycle through different endpoints? I've noticed that some trackers may not work with a selected endpoint (maybe ip ban?) but if I reconnect with another I pick back up. Would there be a way for a refresh or cycle of the endpoints? Reading the faq, the openVPN config may support this but only if the connection has trouble making the handshake?