fritolays

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by fritolays

  1. On 9/23/2022 at 1:37 PM, flyize said:

    Is there a way to run this script in the background, without having to keep the tab open? A quick Google says I need NerdPack to install screen, which is no longer supported. So I'd like to make sure this continues without my input and/or laptop being connected to the Unraid server.

     

    Check out tmux as an alternative to screen.

    Its available to install via the Nerd Pack plugin.

    Github - tmux wiki

    tmux cheat sheet

     

    Create new named session
      tmux new -s sessionname
    
    Close current session (same as exit command)
      Ctrl+D
    
    Detach from current session (run in background)
      Ctrl+B then D
    
    List current sessions
      tmux ls
    
    Attach to last session
      tmux a
    
    Attach to specific session
      tmux a -t sessionname

     

  2. On 5/25/2021 at 3:35 PM, fritolays said:

    So I am not able to get torguard working via wireguard.

    I have generated a known good config that works on my phone via lte and on my desktop.

     

    It does not work with this docker however.

    Watching the log in debug mode it reads "Having issues resolving name 'www.google.com'"

    Keeps trying for x times then just fails.

    Connecting to the console of this docker, I cannot ping the dns and thus cant get any name resolution.

    At this point it attempts to get the vpn public IP but fails as it can resolve any address.

     

    Thus far I've completely removed docker and reinstalled it, completely removed deluge and reinstalled it...

    Any ideas of what I can try?

     

    Ok so I figured this out....

    If you happen to connect via the official TorGuard desktop app it seems to change how TorGuard generates wireguard configs.

     

    Specifically the allowedips line in wg0.conf, TorGuard may generate:

    AllowedIPs = 0.0.0.0/1, 128.0.0.0/1

    While binhex seems to only want:

    AllowedIPs = 0.0.0.0/0

     

    After correcting this I was able to once again connect without issue. I also switched to the official wireguard desktop app and that does not seem to cause config generator issues anymore.

  3. So I am not able to get torguard working via wireguard.

    I have generated a known good config that works on my phone via lte and on my desktop.

     

    It does not work with this docker however.

    Watching the log in debug mode it reads "Having issues resolving name 'www.google.com'"

    Keeps trying for x times then just fails.

    Connecting to the console of this docker, I cannot ping the dns and thus cant get any name resolution.

    At this point it attempts to get the vpn public IP but fails as it can resolve any address.

     

    Thus far I've completely removed docker and reinstalled it, completely removed deluge and reinstalled it...

    Any ideas of what I can try?

  4. So I've been trying to get a fivem server up using your docker.

    It installs and boots fine, but if I attempt to add any resource assets I get a could not make hard link error.

    The odd thing is that I am able to connect to the docker and make said link manually, but fivem doesnt see it?

    Anyone else have any idea how to fix this?

    A quick google seems to show that I'm not the only one out there with beef.