Just wondering if this was being seen anywhere else and if anybody had some suggestions. I politely declined given the fact that I have multiple appliances running the. When I stated that these settings have been the same for years, I was told to reload the appliance. I opened a premium support ticket for the ToM appliance but was told it was QOS settings then the web cache module. The 16.3.2 appliances appear as if they are 'painting' the stats and modules. For network traffic, it comes to a crawl on large downloads or many clients.ġ) 16.3.2 - ToM appliance - 1 min, 38 sec to load the dashboard and 31.1 seconds each time I click on an app, etc.Ģ) 16.3.2 - JDB appliance - 1 min, 15 sec to load the dashboard and 17.36 seconds each time I click on an app, etc.ģ) 16.3.2 - SPD appliance - 1 min, 20 sec to load the dashboard and 55.69 seconds each time I click on an app, etc.Ĥ) 15.1.2 - INP appliance - 23.35 seconds to load the dashboard and 05.00 seconds each time I click an app, etc.ĥ) 16.3.0 - CNO appliance - 22.1 seconds to load the dashboard and 04.69 seconds each time I click an app, etc.

I mean I can open a session, walk away to do some tasks, come back and still wait for the modules to load. The 16.3.2 appliances are slow, very very slow, when loading in Untangle Command Center via remote access and when under moderate (like in the yellow on CPU) load. It offers fiber connectivity for increased performance and security. The z12 is best suited to deliver NG firewall features to mid to large size offices. The remaining two appliances are 15.1.2 and 16.3. Untangle z12 Firewall Appliance ConnectDS provide Resell and Managed Untangle Firewall Services.

Two of those upgraded to 16.3.2 and one is a fresh install yesterday. I have five appliances in Untangle Command Center.

Untangle firewall appliance