Hi all,
Just trying TrueNAS Connect for the first time. Registration all OK and status is heathy from the TrueNAS console but it’s presenting a connection error. I’ve noticed that the URL it’s using contains my local LAN IP address which I’ve no idea is correct or not.
In short, I’m getting
Connection Error
Max retries exceeded
Connection lost unexpectedly - Check network connectivity
Any ideas?
Sean
Have you changed the WebUI port for your Truenas?
Connect only connects via https, so port 443 and nothing else.
As an aside to that, if you do not know the IP of your truenas, then how are you connecting to it?
TrueNAS is using 443 with HTTPS redirect. I’m using my own cert.
I do know the IP address of my TrueNAS. I noticed that the URL that fails to connect to the TrueNAS contains the loca\l\LAN IP address of the TrueNAS and not the external IP address.
I wondered if TrueNAS Connect is mistaklingly registering the LAN address in its central database\registration rather than the WAN address?
Hhhmm, I think I may have misunderstood how this works. I thought that it allowed me to manage my NAS externally but it appears that this isn’t the case.
Ah well, that’s that disabled then.
That’s correct, you need a way to access the system. TrueNAS Connect does not remove the need to use a VPN service or equivalent.
Ahhh this was my issue haha. Was going to create a thread asking if this was the case. 
The documentation isn’t overly clear. From what I can gather it makes managing multiple TrueNAS systems easier from the single interface but provides no real advantage for managing a single NAS.
That is correct. TN Connect was designed with security first, the TN Connect server has no knowledge of your authentication tokens nor does it have direct access to your TN systems.
The browser connects directly to your TN systems, so it needs to be able to do such. TN authentication is stored in a local to the browser encrypted Keyring. TN Connect is not a remote management tool, but a tool for monitoring multiple TrueNAS systems (and via API calls, can do some management such as restarting or updating Apps).
You still need to provide your own security for remote management.
I use Proxmox on my remote backup location to get into the system
I have a dynamic DNS registration.
My remote backup server runs Proxmox, and there are 3 VMs in it:
SO I only have to open the 8006 port on the router to be able to log in into the Proxmox WebUI with https.
Then from there I can use the console windows of all 3 VMs.
And from the console, I am inside the local network.
Is Proxmox hardened enough to be exposed directly to the WWW?
That seems like an unnecessary risk.
I wouldn’t (and don’t); that’s what VPNs are for.
Yeah…
VPN, Bluetooth and WiFi are my arch enemies. 
They NEVER work for me, does not matter how much time I spend on making them work.
This solution is up for me for like 2+ years now.
So, I agree that it is not the best solution, but it works and it is safe enough for me.
That dataset is my georedundant backup.
