SOLVED Replication (Pull) Core-to-Scale Connection Refused

[emsicz]

I'm probably doing something wrong here, but can't figure it out.

• Remote box is running TrueNAS Core 13.0-U3.1
• Remote box is sitting on a connection with public IP and behind a double NAT.
• Remote internet-facing router has port-forward set up from outside port 888 to inside port 888 directed at IP of internal router.
• Remote internal router has port-forward set up from outside port 888 to inside port 22 directed at IP of TrueNAS box.
• So remote call ssh://public_ip:888 should go to the TrueNAS box.
• Local box is running TrueNAS-SCALE-22.02.4
• Local box is sitting on a connection with public IP and behind a single NAT.

I want to set up local box to pull data from remote box using replication task. I have done the following:

• On remote box, I have created SSH keypair.
• On local box, I have created SSH keypair and imported the public/private key into it.
• On local box, I try to create SSH connection using the abovementioned SSH keypair. Here is where I am facing trouble.
  • The UI expects me to input the "TrueNAS URL", not an SSH target and requires either http or https. My remote box does not have internet-facing TrueNAS UI. So if I try to input http://public_ip:888, I get "Connection refused" error message.

I do not have control over the remote network architecture. I would like to avoid convincing the remote party to create or join VPNs, I would just like to set up the replication task and forward appropriate ports. Is this doable?

 

[emsicz]

Just to clarify - I'm asking if there is a bug in the UI or if I'm missing something. This is definitely not the first time this has been asked and I'm not looking to be told to connect the box to the internet. I'm quite confident that there is a way to do this with port forwarding, but somehow I'm missing it.

What are my options for connecting two machines for remote replication?

I've tried googling and searching these forums to find a guide or something covering the basic necessities to get something like this to work, but due to my lack of experience in this subject, I'm a bit lost. Specifically regarding "over the internet" communications in general (SSH, VPNs, etc)...

www.truenas.com

Besides telling the asker they are dumb, someone reiterates that replication through port forwarding works just fine, but that part is exactly what I can't seem to get to work.

Unable to access server via SSH or remotely to WebGUI

Hello everyone, I recently made the switch from Ubuntu to FreeNAS on my media server at home. I am running FreeNAS 8.3 and have installed the plug-ins from the Source Forge page, Transmission, FireFly and MiniDLNA. My server is up and running and all my folder permissions etc. are working...

www.truenas.com

This unanswered thread says OP "enabled SSH access locally," which made me think that there is a setting somewhere in Core that I need to flip in order to enable SSH without UI login? Will test when I get a chance.

[How-To] How to Access Your FreeNAS Server Remotely (and Securely)

After I set up FreeNAS and got comfortable with it, I began to explore accessing it remotely over the internet. Not being a computer professional, I was surprised to find out how often people were sniffing around trying to get in. If you want to see for yourself, just give yourself a...

www.truenas.com

And this says there is indeed such setting and it explains how to use it.

 

[emsicz]

OK - got it. It's not a bug, but... this is what the UI to create SSH connection looks like:

When the setup method drop down is clicked:

On a 4K screen, the option Manual just looks like it's the title of the value being edited. I simply did not see that option mentally. When selected, the UI changes so that it expects just IP address, port, and SSH key which was already imported prior. It works as expected.

Additionally, even though an SSH keypair is created on the TrueNAS Core system, it's public key needs to be assigned to the user that is used for the replication process. When setting up SSH in Services, there is a link in tooltip that was probably meant to tell this to the user:

When this link is clicked, this is where it leads:

Surely you must understand I am not an ape for missing all this, this is annoying UX issue. Is this just me or should I create some low prio usability ticket somewhere?