DaddyNugget

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by DaddyNugget

  1. 15 hours ago, binhex said:

    ok so you have had a working incoming port assignment at some point then, yes?


    Correct, I wasn't trying to ask for help, I was trying to let the other user know that there may be an odd error here or there, but your overall instructions should work.  The only thing I needed to do outside of that was update pacman, which I mentioned previously.  This was just to help other people if they get stuck like I did.

    Sorry for the confusion.  At this time I'm all set.

  2. 2 hours ago, binhex said:

    perhaps the port was closed due to not refreshing every 60 seconds?


    No, actually in my case I eventually received an error stating "This gateway does not support NAT-PMP" a few times then the loop stopped working.  I simply started it again when I saw it, and it's been chugging along fine since.  My guess is that their server restarted, or docker updated or something.

  3. On 7/3/2023 at 5:06 PM, st34m said:
    using gateway: 172.17.0.1 

     

    That gateway looks like IVPN not ProtonVPN.  I'd double check to make sure everything is straightened out.  For what it's worth I also got an error message while requesting a port forward, but this was after several hours of success.

  4. Thank you so much for all that you do binhex! You've built so many amazing containers, and frankly I'd be lost without you.  

     

    On 6/30/2023 at 8:01 AM, binhex said:

    step 1. install natpmp by getting to the 'console' of the container then typing `pacman -S libnatpmp` confirm install, then issue the command `natpmpc` to ensure its installed.


    Just so you know, after this step I had to run 'pacman -Syu'.  Without this I either had out of date repositories or something.  I could see the package could be installed, but none of the repositories could give me the file.  After running the command I declined all of the available upgrades (I was unsure if I would break the container), but re-running 'pacman -S libnatpmp' was successful.

    Also, in case you already aren't aware, IVPN also announced that it would no longer offer port fowarding.  This will push many people to Proton VPN as it did myself.  Hopefully Proton will make it easier to retain a port forward, but until then hopefully we can figure out a workaround for PMP request.  I've seen some scripts online, but I'm unsure of the exact way to implement it with the current docker container.

    I've experimented with trying to change the port via the qBittorrent API, but that hasn't been successful for me.  The only other route I can think of is when a port change happens to shut down qBittorrent, update the config, spin it back up.  Either way seems rather cumbersome.

  5. On 7/19/2021 at 7:22 PM, bidmead said:

    My problem with calibre on UnRAID is that the webGUI is completely intractable when accessed from a phone. While the regular UnRAID webGUI can be zoomed and panned, calibre's simply fails to shift, making it impossible to access necessary parts of the screen.

     

    Has anyone found a workaround for this?

     

    -- 

    Chris

     

    On Android devices I use 'CalibreCompanion' or 'CCDemo' (trial/free version).  Super handy app that makes connecting to Calibre a breeze.

  6. On 4/19/2021 at 4:27 PM, Bleak said:

    Is is one of the config files that it comes with thr cloudflared config file is for DOH (DNS over https) and the stubby config file is for DOT (DNS over TLS). I am having issues eith DOH so I set The DOT as the first dns server. Since then no issues.


    Noted, thank you so much.  I'll look into it.  I have other issues with my network so I'm just gutting it and starting from scratch to remove a couple years of duct tape and quick fixes.  I will reference this when I redo it all.

  7. 5 hours ago, Bleak said:

    Can you try setting stubby(tls) as first and doh as second and see if your issues go away? I have too little knowledge to be certain but DOH seems to cause my issues.

    Bear with me as I'm not sure what Stubby is.  Unless it's already baked into the docker image.

    I had the setting working fine for over a month pointing to my router, then it failed 2 days ago.  I have tried setting it to the loopback addresses in the description of the image as a troubleshooting step to no avail.

  8. I am also having an issue with this container as of yesterday morning.

    -Using multiple VLANs on my network

    -One VLAN is using the piHole container for content filtering (kids network)
    -PiHole and pfSense are configured together to force all DNS queries on that VLAN to go through piHole then into pfSense.

     

    As of yesterday morning, with no visible changes, all DNS queries were lost on that VLAN.  I monkied around with it for a couple hours and got it going again.  This morning the same thing happened.  I suspect there is a cron job or something happening at night causing this but I am not certain yet.

     

    The three symptoms I see are A) the piHole DNS service is not running.  B) the docker is reported as 'unhealthy'.  C) running pihole -r shows that the pihole itself cannot obtain DNS entries at this point, and that there is a kernel update available.

     

    If anyone has any pointers please let me know.

  9. I will definitely take a look at nomachine, right now I am trying to find a good encrypted alternative to VNC, I have many linux hosts so RDP won't always work for me.

     

    But, after fiddling around with numerous settings I managed to fix my issues, thank you for pointing me in the right direction.  @Limy have a great weekend!

     

    As I was changing settings in my firewall, updating rules, etc.  I ran into another problem (which was entirely an oversight on my end, and managed to fix it).  As I was troubleshooting this problem, I reset the state table on my firewall, which caused the lockups in both a virtual terminal running 'ping' endlessly, and my noVNC connection into my WIndows host (which makes sense because I killed the connections, but was eerily similar to the hangups that happened every 10-30 seconds before).

     

    So, I think my issue was related to how I had unRAID interact with my VLANs.  I changed the IP address settings from 'Automatic' to 'None' on each VLAN.  I am assuming that I was causing broadcast storms and/or cross communication which was seriously impacting my network performance (At least on unRaid), which would be reflected with both the VNC connections and virtual terminal.  Since implementing this change (and others) I was able to completely eliminate my issues.

     

    **My only residual issue is trying to install Pop_OS! in a virtual machine.  With or without GPU passthrough, after installing the operating system w/encryption I reboot the VM.  I am presented with a lock screen, and after popping in the decrypt key, the machine hangs indefinitely.  If anyone has any ideas, I would greatly appreciate it.

     

    **I have every VM set up to CPU passthrough, not emulated.  I'm not sure if this is a pro or con.  [I understand the security risk involved of passing information between VMs, but I don't know of the CPU cost of emulating the processor, while searching for information I didn't find an answer].  I will be attempting to get the Pop VM set up today, so if I find a solution I will post here for posterity.

  10. @Limy  Much appreciated, I'm happy to have the help.  I changed some of my network settings, and I organized my pfSense rules to make changes a lot easier moving forward (assigned aliases, updates descriptions, etc.).  Although I do not see an improvement on the terminal or VNC client locking up, I do feel as though my setup is much cleaner.  I'm going to keep experimenting with the network settings, and see if I have to forward the VNC ports to my unRAID box or something to stop that from freezing.

     

    Thank you again for the information.

  11. Bump

     

    Although I've waited this long to post something, I've been dealing with more and more errors for the past 6 months and I just can't deal with it anymore.  In an effort to troubleshoot my Plex VM I have to restart the VNC client every 20 seconds or so.  If anyone can help me, I would greatly appreciate it.

  12. I would like to lead off with a thanks for reading, and I will do my best to give all the information possible.

     

    Hardware:

    unRAID Version: 6.5.3

    CPU: AMD 1700

    Motherboard: Asrock Taichi x370

    RAM: 2x16GB Dual-Channel Corsair LPX Vengence @3200mhz

    USB: Sandisk Cruzer 16GB, not sure how old (potentially the problem?)

    HDDs: Double Parity, 6x6 TB drives of mixed vendor/age.

    Cache: 256 GB Sandisk SSD

     

    Plugins:

    (All up to date as of 07/31/18)

    CA Auto Update Plugins

    CA Cleanup Appdata

    Community Applications

    Dynamix SSD TRIM

    Dynamix System Temperature

    Fix Common Problems

    Nerd Tools

    Speedtest Command Line Tool

    Statistics

    Unassigned Devices

    unBALANCE

    User Scripts

     

    Docker:

    (All up to date as of 07/31/18)

    Binhex-DelugeVPN

    CUPS

    SyncThing

    Unifi

     

    I have a few problems as of late that have made unRAID very difficult to use properly.

     

    1) Any VM that I use VNC to connect to will lose it's VNC connection after a period of 10-30 seconds.  I then have to manually disconnect and reconnect the connection before it freezes back up.  I primarily use this on a Windows 10 VM that runs my Plex Media Server / mcebuddy / comskip combination that I use as a DVR.  This happens when I use RealVNC AND when I use a different VNC client and connect to my server's IP:port assignment.

     

    My attempts at solutions:

    Try using another VNC client

    Change the VNC driver to every different setting

    Opening ports on my firewall to allow VNC on my server between VLANs.  (I can try this one again, I may have set it up wrong)

    Replace aging disks in the array

    Adding an SSD cache with an old SSD drive

     

    Note: I also get a locked screen when I access the web terminal from the GUI, or ssh from a terminal.  After a period of 10-30 seconds, the terminal hangs and I need to reboot it.  My CentOS VM that has a GPU passthrough does NOT hang during this time.

     

    2) When I install Pop!_OS into a virtual disk, I can get as far as encrypting the disk.  After the image reboots, I get a black screen that is indefinite.  I am unable to look at the specific logs for this VM.  Any pointers would be helpful.  (Happens with both a GPU passthrough or VNC).

     

    Other:  I had this CPU overclocked to 4.0GHz with 1.3v offset up to 1.37v for a period of about 3 months.  (Previously 3.6 at same voltage, but ran into thermal throttling.  After upgrading the case and installed a Corsair H110i brought the clocks up).  The temperature has stayed low this whole time and never got above 30-40C.  CPU utilization could max at most 4c/8t, and the other 4c/8t at approx 50%  I did this to improve the transcode times in my DVR VM, but have since set the BIOS to stock (except for changing the C6 state to disabled, and Virtualization to enabled, IOMMU enabled, as required for unRAID).  I ran a memtest for 2 passes (just 1 complete pass overnight, didn't want to leave it running forever) with no errors found.  The flash drive is a used drive from my collection, reformatted to use for unRAID about 3 years ago.

     

    I suspect the flash drive is the culprit because I have tried everything else that I could think of or google up myself.  If anyone has any pointers it would be greatly appreciated.

     

     

    nuggetunraid-diagnostics-20180731-2141.zip