BBoYTuRBo

Members
  • Posts

    55
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

BBoYTuRBo's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. I didn't see any changes to the permissions of anything in my ~/.ssh folder/files, but after removing the plugin and rebooting I am able to connect with my SSH keys again.
  2. 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?
  3. 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?
  4. Sorry, I usually run the latest 'next' version and am severely sleep deprived at the moment and just posted here without thinking. I would consider it a bug in how unRAID handles BTRFS pools, since BTRFS itself handled it correctly. But, please move this wherever is appropriate and thanks for cleaning up my mistakes!
  5. I am running unRAID 6.11.5 I just replaced the mobo/cpu in my server, and while I was at it, I switched an M2 drive that I had connected to a BTRFS cache pool via a USB enclosure directly to an M2 port. In doing so, the ID of the disk changed, and unRAID won't recognize it as part of the cache pool. When I do a `btrfs fi show` on the other disk in the pool, BTRFS correctly recognizes the disk that now has a new ID (while unRAID does not). When I try to switch the disk under the new ID into the cache pool from the unRAID web UI, it gives a red X and says "Wrong". If I start the array up in this state, will it treat the disk as a new disk and wipe it out? Update: I went ahead and started the array. It shows the disk as "New", and is going through the rebuild process as if it was a new disk. No data was lost since it was set up as RAID1. So, just a waste of time/processing power.
  6. I also came here to ask for Fish shell. And thanks for all your work on the plugin!
  7. 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!
  8. Thanks for your work! For farmOS, does the template create the database as well? Or do I need to setup up a separate container containing the DB and link them?
  9. 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:/#
  10. Changed Status to Solved Changed Priority to Annoyance
  11. So I just updated to 6.8.0 RC1. I have a bunch of scripts stored at /boot/scripts After booting up, I tried to run a script, and it said permission denied. I looked, and all my scripts are set to -rw------- permissions, and I cannot change them. When I try executing chmod, it doesn't give an error, but it doesn't do anything either. Chown throws an "operation not permitted" error.
  12. I'd like to request an UNRAID docker template for IVRE. It's basically a one-click install if you're using Vagrant, and they have all the instructions for installing/running it with only Docker, but I can't seem to get it to work properly on UNRAID. https://github.com/cea-sec/ivre/blob/master/doc/DOCKER.md
  13. None on my servers either. I've been tailing dmesg on a terminal screen. There are no apparent errors when the system hangs. It just stop responding to input and does not output anything more to the screen.
  14. I've been having this issue on my dad's server for months. I finally ended up building an entirely new system and moving all my disks over.... and it's still happening! I think it is an issue with Docker. I had Docker disabled, and the system was up for 4 days with no issues. I enabled Docker (with only 1 container, Emby), and now the system is unresponsive again (it responds to pings, nothing else) after a day. I've created a new docker.img file, but that didn't help. I have no idea what else to try at this point. Meanwhile, on my server, I'm running Docker with about 15 containers and the system never freezes (although it loses WAN connection after a while, and the only way to restore it is with a reboot. LAN connections are unaffected).
  15. Sorry to revive a zombie thread... but did anyone have any luck with this? I found a soulseek and a nicotine docker that used vnc to allow access, but they're not working correctly.