Syncthing Gui via https in TrueNas Core

Apps and Virtualization
,
1

I just tried to install Syncthing on my TrueNas Core system (13.3). That works and I can access Syncthing via HTTP (using the default settings).

However that is IMHO a NO GO. So I tried to switch to HTTPS. In Syncthing under advanced settings there is a switch “Use TLS” (reads like use https).

Switching that on => exit interface also after refresh and restart Syncthing.

I searched the internet for a solution and tried some suggestions … but none did work!

Does any one know it it is possible to use HTTPS!? And if so how !!??

2

Certainly the question isn’t of such urgency that the over-punctuation is called for. The most straightforward way to expose any app via HTTPS is to use a reverse proxy. If you want to stick with apps TrueNAS provides, I think Nginx Proxy Manager is the only available option.

3

I do not like app’s up to now. Is it an option to install Syncting in a VM and access some datasets from there!?

4

You can, of course, install anything you like in a VM. Data can be shared with that VM using any file-sharing protocol you like; NFS is probably simplest.

5

Curiously enough we are in the CORE category, ambassador :slight_smile:

So any reverse proxy can be installed in that (I assume) jail.

@louis How did you install Syncthing exactly?

6

Indeed. Though I have always been here, it appears I’ve become somewhat inattentive.

But in that case, this really isn’t a TrueNAS question at all–unless OP used a plugin, which is always a bad idea.

7

The easy way. Just go to apps choose syncthing. Install it the without advanced options. Naming the jail also Syncthing that is it. I did suppose that would do :slight_smile:

8

There isn’t any place on CORE called “apps.” Did you use a plugin? If so, delete it, and look for some other way to install it.

9

Sorry the name in no apps but plugins you are right

10

Yeah, plugins are long since dead, and iX recommends against their use (though it’s a fair question why the product still includes them in that case). If you want something like plugins, you should really be using SCALE.

Otherwise, you can create a jail, and then install whatever you like (including syncthing) inside it, sharing any of your data with it directly. Or do as you suggested and create a VM, though sharing data with a VM isn’t quite as direct.

11

I have two NAS systems my old one (core) and my new one (scale). Using the old one as a backup for the new one.

In my innocence I did expect that it was as easy as described …
I doubt if it is worth the effort to create my own syncthing vm (that is the way I would go). Hopefully it is implemented on scale in a IMHO better way

12

I think it is, but it’s still going to require use of a reverse proxy to get HTTPS.

13

Stupid! IMHO that is so basic!

14

I think it’s pretty much the norm in the Docker world to push TLS termination off onto a reverse proxy–Traefik seems most common, but Caddy, NPM, Apache, and others are options. Of course, Syncthing’s own communications are still TLS-encrypted regardless of whether you’re using HTTP or HTTPS.

15

Up to now I am only using TrueNas as NAS and as VM platform. I think I stick with that

16

Up to you. A VM will migrate mostly-seamlessly to SCALE if/when you migrate that system. A jail will give you a more lightweight installation of FreeBSD with much easier access to data on your main system. If I wanted to install Syncthing on CORE, it’d be in a jail.

1 Like
17

Syncthing is incredibly easy to install on core. A simple pkg install syncthing is all that’s needed in a jail.

I’d add it to my repo if it weren’t so easy to install.

18

Can anyone verify if this works (seems very simple)?
syncthing - FreeBSD Wiki

19

I just installed via pkg. I actually changed the address from 127.0.0.1 to 0.0.0.0 so I could access it on the port it runs on. This allows me to bypass the nginx part.

I’d use caddy anyway…

1 Like
20

I one’s long ago tried Treafik, but there is another problem. I am using vlans.

And I insist that traffic arriving via vlan-A is returned via vlan-A. Which is NOT the way TrueNas standard bahaves :cold_face:

I did manage to create such routing on Scale, not sure if it is possible on core, and I am almost sure it does not work with a solution like Treafik. So for me thats a NO GO