Skynergy

I am trying to connect to a Hetzner Storage box using: ssh -p23 [email protected] (obviously where uXXXXX is my correct username) but get an error ssh: connect to host [email protected] port 23: Network is unreachable. On the same LAN using my Fedora workstation I am able to connect successfully to the storage box. Thus it is possible to connect to the external storage box from my network and the login is successful. The issue must be with Unraid's outgoing port 23? In Unraid Settings, Management Access, Telnet is set to No. I also have the same issue on port 22 when I try sftp -P 22 [email protected], it works on my Fedora workstation but not from the Unraid terminal. I have also tried connecting using only the IPv4 address of uXXXXX.your-storagebox.de but get the same message of Network unreachable. If I ping 1.1.1.1 from the Unraid terminal it returns results successfully as expected. I'm not running any VPN in Unraid VPN Manager but have Tailscale set up. Could it be that? Any ideas what is blocking the outgoing the ssh and sftp connections from Unraid? Thank you in advance.

I'm going to return it tomorrow. The guy said its a good brand but I'm also unfamiliar with that brand. Think he was trying to make a quick sale.

Thanks for your reply. It's a Netac NVMe M.2 SSD PCIe Gen3x4 2280 1TB drive. I took my motherboard user guide with to the shop and they assured me it would be fine.

I replaced a SSD drive in the cache pool with a brand new 1tb NVMe. Once Unraid and the array started the NVMe was visible. I assigned it to the cache pool. Checked the box to format the unassigned drive which then displays "formatting". But if I try and go to any other Unraid menu the UI is completely frozen. And when refreshing the web url it just says: ip_address is unreachable. Any ideas or insights will be greatly appreciated. Let me know if you need more details. I managed to see this in the log before the terminal window also became unresponsive: Nov 26 15:15:23 Proactive kernel: mdcmd (36): nocheck pause Nov 26 15:15:24 Proactive emhttpd: creating volume: cache (btrfs) Nov 26 15:15:24 Proactive emhttpd: writing MBR on device (nvme0n1) with partition 1 offset 2048 Nov 26 15:15:24 Proactive emhttpd: shcmd (270): sfdisk --quiet --label dos /dev/nvme0n1 <<< 'start=2048' Nov 26 15:15:24 Proactive kernel: nvme0n1: p1 Nov 26 15:15:24 Proactive kernel: nvme0n1: p1 Nov 26 15:15:24 Proactive emhttpd: shcmd (271): udevadm settle Nov 26 15:15:24 Proactive emhttpd: shcmd (272): /sbin/wipefs -af --lock /dev/nvme0n1p1 Nov 26 15:15:24 Proactive emhttpd: shcmd (273): /sbin/blkdiscard /dev/nvme0n1p1 Nov 26 15:15:55 Proactive kernel: nvme nvme0: I/O tag 64 (5040) opcode 0x9 (I/O Cmd) QID 1 timeout, aborting req_op:DISCARD(3) size:4294966784 Nov 26 15:15:55 Proactive kernel: nvme nvme0: I/O tag 65 (2041) opcode 0x9 (I/O Cmd) QID 1 timeout, aborting req_op:DISCARD(3) size:4294966784 Nov 26 15:15:55 Proactive kernel: nvme nvme0: I/O tag 66 (1042) opcode 0x9 (I/O Cmd) QID 1 timeout, aborting req_op:DISCARD(3) size:4294966784 Nov 26 15:16:25 Proactive kernel: nvme nvme0: I/O tag 10 (c00a) opcode 0xa (Admin Cmd) QID 0 timeout, reset controller Nov 26 15:19:35 Proactive kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Nov 26 15:19:35 Proactive kernel: nvme nvme0: Abort status: 0x371 Nov 26 15:19:35 Proactive kernel: nvme nvme0: Abort status: 0x371 Nov 26 15:19:35 Proactive kernel: nvme nvme0: Abort status: 0x371