Jump to content

BBoYTuRBo

Members
  • Posts

    55
  • Joined

  • Last visited

Posts posted by BBoYTuRBo

  1. 14 minutes ago, JorgeB said:

    Do you have the parity check tuning plugin?

    I do. And it looks like it was updated 02/08, which would be around the time my problems started.

    I guess I'll try removing it and rebooting?

  2. Okay, I am completely baffled. Everything was working fine until a few days ago. I'm not aware of anything I changed on the server. No added plugins or anything, no updates. But now whenever I try to connect from anywhere with my SSH key, it fails and asks for a password. At this point I'd be fine with wiping out my configuration and generating new keys if it would get things working (which I tried, unsuccessfully).

     

    I manage 2 unRAID servers, and this happened on both of them, and it happens from any client I try to connect with, and also happens trying to connect from unRAID server 1 to server 2 (and vice versa).

     

    Here is the output from an ssh -v attempt:

     

    OpenSSH_9.1p1, OpenSSL 1.1.1s  1 Nov 2022
    debug1: Reading configuration data /root/.ssh/config
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
    debug1: Connecting to remote-server [remote-server] port 22.
    debug1: Connection established.
    debug1: identity file /root/.ssh/id_rsa type 0
    debug1: identity file /root/.ssh/id_rsa-cert type -1
    debug1: identity file /root/.ssh/id_ecdsa type -1
    debug1: identity file /root/.ssh/id_ecdsa-cert type -1
    debug1: identity file /root/.ssh/id_ecdsa_sk type -1
    debug1: identity file /root/.ssh/id_ecdsa_sk-cert type -1
    debug1: identity file /root/.ssh/id_ed25519 type -1
    debug1: identity file /root/.ssh/id_ed25519-cert type -1
    debug1: identity file /root/.ssh/id_ed25519_sk type -1
    debug1: identity file /root/.ssh/id_ed25519_sk-cert type -1
    debug1: identity file /root/.ssh/id_xmss type -1
    debug1: identity file /root/.ssh/id_xmss-cert type -1
    debug1: identity file /root/.ssh/id_dsa type -1
    debug1: identity file /root/.ssh/id_dsa-cert type -1
    debug1: Local version string SSH-2.0-OpenSSH_9.1
    debug1: Remote protocol version 2.0, remote software version OpenSSH_9.1
    debug1: compat_banner: match: OpenSSH_9.1 pat OpenSSH* compat 0x04000000
    debug1: Authenticating to remote-server:22 as 'root'
    debug1: load_hostkeys: fopen /root/.ssh/known_hosts2: No such file or directory
    debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
    debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: algorithm: [email protected]
    debug1: kex: host key algorithm: ssh-ed25519
    debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
    debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
    debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
    debug1: SSH2_MSG_KEX_ECDH_REPLY received
    debug1: Server host key: ssh-ed25519 SHA256:vxx/X/xxxxxXXX#xXXX#xxxxxxxxxxxxxxxxxxxxxxx
    debug1: load_hostkeys: fopen /root/.ssh/known_hosts2: No such file or directory
    debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
    debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
    debug1: Host 'remote-server' is known and matches the ED25519 host key.
    debug1: Found key in /root/.ssh/known_hosts:14
    debug1: rekey out after 134217728 blocks
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: rekey in after 134217728 blocks
    debug1: Will attempt key: /root/.ssh/id_rsa RSA SHA256:xx/X/xxxxxXXX#xXXX#xxxxxxxxxxxxxxxxxxxxxxx
    debug1: Will attempt key: /root/.ssh/id_ecdsa 
    debug1: Will attempt key: /root/.ssh/id_ecdsa_sk 
    debug1: Will attempt key: /root/.ssh/id_ed25519 
    debug1: Will attempt key: /root/.ssh/id_ed25519_sk 
    debug1: Will attempt key: /root/.ssh/id_xmss 
    debug1: Will attempt key: /root/.ssh/id_dsa 
    debug1: SSH2_MSG_EXT_INFO received
    debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,[email protected],ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected]>
    debug1: kex_input_ext_info: [email protected]=<0>
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue: publickey,password,keyboard-interactive
    debug1: Next authentication method: publickey
    debug1: Offering public key: /root/.ssh/id_rsa RSA SHA256:vxx/X/xxxxxXXX#xXXX#xxxxxxxxxxxxxxxxxxxxxxx
    debug1: Authentications that can continue: publickey,password,keyboard-interactive
    debug1: Trying private key: /root/.ssh/id_ecdsa
    debug1: Trying private key: /root/.ssh/id_ecdsa_sk
    debug1: Trying private key: /root/.ssh/id_ed25519
    debug1: Trying private key: /root/.ssh/id_ed25519_sk
    debug1: Trying private key: /root/.ssh/id_xmss
    debug1: Trying private key: /root/.ssh/id_dsa
    debug1: Next authentication method: keyboard-interactive
    (root@remote-server) Password:


    Could someone list the steps for the current unRAID version, 6.11.5, to set up passwordless SSH key access from scratch, including the key generation command?

  3. 15 hours ago, C4ArtZ said:

    The template does not create a database. You can either create a database in a seperate container or use the internal sqlite database. During the first time setup farmOS will ask you what you prefer.

     

    Ah, thanks! I didn't realize scripts were being blocked when I opened the config page and the database setup options were all garbled. I'll be able to get it up and running now!

  4. The docker image seems to be broken now.

    I didn't change any configurations or anything on my end, but as soon as I start it now, it just stops right away.

     

    Edit: Same thing is happening with my Sonarr container as well now

     

    Solution: I am an idiot. My cache drive got filled up with gigantic log files and that was why my containers wouldn't run. So the problem was all my fault, nothing to see here.

     

    root@Server-Biggie:/# docker logs -f --tail 100 qbittorrentvpn
    Created by...
    ___.   .__       .__
    \_ |__ |__| ____ |  |__   ____ ___  ___
     | __ \|  |/    \|  |  \_/ __ \\  \/  /
     | \_\ \  |   |  \   Y  \  ___/ >    <
     |___  /__|___|  /___|  /\___  >__/\_ \
         \/        \/     \/     \/      \/
       https://hub.docker.com/u/binhex/
    
    Created by...
    ___.   .__       .__
    \_ |__ |__| ____ |  |__   ____ ___  ___
     | __ \|  |/    \|  |  \_/ __ \\  \/  /
     | \_\ \  |   |  \   Y  \  ___/ >    <
     |___  /__|___|  /___|  /\___  >__/\_ \
         \/        \/     \/     \/      \/
       https://hub.docker.com/u/binhex/
    
    Created by...
    ___.   .__       .__
    \_ |__ |__| ____ |  |__   ____ ___  ___
     | __ \|  |/    \|  |  \_/ __ \\  \/  /
     | \_\ \  |   |  \   Y  \  ___/ >    <
     |___  /__|___|  /___|  /\___  >__/\_ \
         \/        \/     \/     \/      \/
       https://hub.docker.com/u/binhex/
    
    Created by...
    ___.   .__       .__
    \_ |__ |__| ____ |  |__   ____ ___  ___
     | __ \|  |/    \|  |  \_/ __ \\  \/  /
     | \_\ \  |   |  \   Y  \  ___/ >    <
     |___  /__|___|  /___|  /\___  >__/\_ \
         \/        \/     \/     \/      \/
       https://hub.docker.com/u/binhex/
    
    root@Server-Biggie:/#
    

     

  5. My dad's server crashes every 1 or 2 days. Usually it just locks up. No errors on the console, it just becomes totally unresponsive. Lose access by SSH and samba, but can sometimes type something into the terminal, but then it freezes completely when entering the command.

     

    It's been doing this for a while. I even replaced the MoBo, RAM, CPU, and a couple disks (and ran RAM tests, with no errors). Same thing. If I can ever see some sort of error or anything useful in a log, I'll post it.

  6. I'm having a strange issue. I just switched over to the unified version of this docker on my own server, and now I have everything working great.

     

    However, I tried to do the same on my dad's unRAID server, and I've encountered a problem. I ended up removing the container and data, and downloading everything again, and started with a new blank /data directory. I can connect via the web UI or VNC client, but then it ends up just freezing. Something about an EQ overflow having to do with Xvnc.

     

    I've attached my logs. Any help would be greatly appreciated!

     

    Edit: So it seems to be working somewhat now. I set up the UI on my desktop to connect to the Crashplan service on the server, and it will connect, but has a lot of issues with freezing up. Also, now I am finally able to connect via the Web UI and VNC, but sometimes it complains about not being able to connect to the CrashPlan engine, or just getting disconnected or freezing.

    unraid-crashplan-crashlog.txt

  7. i am running openvpn on my unraid machine and it works great. but i also want to owncloud in either a vm or docker but i can't get all the port forwarding right with my von provider (PIA).

     

    so my question is, if there is a way to exclude a specific docker container or vm from openvpn so it would be assigned my "normal" public ip? 

    This! Or in my case, a way to ONLY send specific docker containers through the VPN connection would be preferred. I managed to get Deluge running through a dockerized OpenVPN connection, but then I need to use a reverse proxy docker to access the webUI, and even then, I can't access the daemon anymore.

    I know that using Pipework you can assign a docker container its own IP address and specifcy a network interface to use, but I'm not sure how to use it properly.

  8. I am having a most perplexing problem. I have the plugin working fine on my dad's unRAID box. I have the EXACT SAME configuration on my box, and I can't get the plugin to work.

     

    Everything is configured correctly, but whenever I hit start from the web interface, I get this error in the log:

     

    Options error: You must define TUN/TAP device (--dev)
    Use --help for more information.

     

    The problem is, I do have "dev tun" in my ovpn file, but every time I hit start, it deletes that line from the ovpn file. I tried removing write permissions from the ovpn file, but it still deletes that line every time and fails to start. I'm completely at a loss as to how to remedy this.

     

    Edit:

    I just tried running the start command manually

    /usr/sbin/openvpn --writepid /var/run/openvpn/openvpn.pid --config /boot/openvpn/gw1.iad1.slickvpn.com.ovpn /dev/null

     

    It works! So I guess the problem is with the start button on the OpenVPN Client settings page....

×
×
  • Create New...