TIA

I think it will be a good improvement of quality of life to have some kind of shortcuts on the items in a farm to clone the item into another farm.

Always I must create them on the HTTPS farm and on the HTTP farm

So, every time I create a new website I create it on the HTTPS, and a redirection to this item in the HTTP.

So, a shortcut inside the item that allows you to duplicate it would be good

If it’s a redirection, duplicate it as it is.

If it’s a host, have 2 options duplicate as is, or duplicate as a redirection to the original copied item

Today I had to create 1 website and 15 redirections to different URIs in the main website, so I had to do it 32 times and it’s a time-consuming process.

Something that will be especially useful for users that have a lot of websites on the same farm is the ability to create groups / projects / blocks.

for example, in the farm i have einatec.com, einatec.es, support.einatec.com, etc. Some are websites and other are redirections. 

Or I have a client with 3 or 4 websites, to be able to group them and move them as a block will be visually pleasant, 

This will be good to keep the farm clean, right now I am over fifty entries but if I can group them i will have around twelve.

Thanks

Is it possible to enable HSTS on the web UI (default port 444)? Our Nessus scanner is flagging the WebUI for not having HSTS and I have not found an option to enforce it. I suspect I could to it directly from Debian, but I wanted to check here first in case the direct method breaks things. 

Thanks,

I have a working skudonet cluster with node 1 (eth0) using 192.168.1.71, node 2 (eth0) using 192.168.1.72 and the VIP node 1 / node 2  (eth0.1) using 192.168.1.90. When node 1 (.71) goes down, node 2  (.72) takes over and the VIP (.90) and all services on it move to node 2. So as far as I can tell my setup is correct. 

My issue is that my UniFi Network Application (a separate product I use to manage some of my network) periodically reports a duplicate IP address for 192.168.1.90. Interestingly, it does not only happen when one of the skudonet nodes go down, it also happens at least once a day by whenever the skudonet cluster is operational. My questions are the following:

1. Does the cluster test itself once a day or do something else that would cause the VIP to switch nodes even if there is no reason for it to move?

2. Is it possible to have the virtual interface MAC addresses for node 1 and node 2 to be the same so it won't trigger duplicate IP

3. Is this not expected and perhaps the result of something in my cluster configuration that is good enough to make the cluster work, but not quite perfect?

Thank you in advance for any assistance you can provide.

Just did a fresh install with skudonet CE.

I'm able to configre the first NIC with IP 10.10.xx.110

But when I edit the second NIC and what to add 10.10.xx.111

it complains that this is already configured on ETH0?

I download, install and configured skudonet community edition, and after, i bought the Subscription Plan.

Is it necessary to migrate from one version to the other one? I think both of them are almost the same, but there are little differences, right? Is there any guide for doing that migration?

Thanks!

I can't really find much on using websockets over this particular proxy. I've had good luck with HAProxy, but I'm trying to move AWAY from HAProxy :)