is there a way to redirect freenas's address to a plugin's web?

[okitai]

Hi,

I want a user to type
'freenas.local/nextcloud' and get the nextcloud (installed plugin) web
'freenas.local/transmission' and get the transmission (installed plugin) web console
and so on...

(All this plugins are installed on that server)
Each plugin has its own address on the network (not a freenas's NAT addresses)


Is there a way to get this done, or do I need a separate/spacial (internal to the network) DNS server?


Thanks and good health to all of you...

 

[SweetAndLow]

Reverse proxy is probably the solution you want. You can't do this with freenas. each jails acts as it's own different system. If you remove the vnet feature you can use the freenas ip to access the jails with different port numbers but that doesn't do what you are asking.

 

[StoreMore]

I am not sure what the real end goal is, accessing it only internal or external?

If the goal includes external you could buy a domain or reuse an existing domain along with several A records pointed to your server. Ex: nextcloud.MYNASDOMAIN.com or transmission.MYNASDOMAIN.COM. The A records would point to your external IP address you'd need to configure port forwarding on your router to allow these ports through your firewall and point them to your device.

If internal only is your goal, you could modify your host record on each machine. to add the freenas.local bit.

 

[winnielinnie]

Since each jail is technically its own system / host, I cannot conceive of any way to accomplish what you're trying to do. Here's why:

Your Transmission jail is assigned an IP address of 192.168.0.100 by your DHCP server.
Your Nextcloud jail is assigned an IP address of 192.168.0.101 by your DHCP server.

Does freenas.local translate to 192.168.0.100? 192.168.0.101? It cannot be both at the same time.

An alternative approach, which I currently use successfully is with the following format:

qBittorrent: qbittorrent.freenas
Nextcloud: nextcloud.freenas
Plex: plex.freenas

It's not exactly the same format as you're trying to achieve, but it works well enough where you can still use friendly names to access the GUIs and web portals for your different plugins.

* Keep in mind that it also depends on the web browser you are using to access the plugins. Firefox tends to play nice, where you don't need to prepend http://, yet Google Chrome only works if I prepend http:// in front of the address, otherwise it will do a Google search for "qbittorrent.freenas".