Control 1.1r Released! (cloud & on-premises)

This release enhances visibility and site management with WAN status and integrated speed testing, site location and mapping support, and an expanded set of client device icons, along with performance and telemetry optimizations and fixes to backup restoration.

  • Route10: Add WAN Status to Dashboard, include Speed Test.
  • Add Site Location to Dashboard.
  • Add Site Map to Site Manager.
  • Add many more Client Device Icons.
  • Improve performance and telemetry handling.
  • Resolve issues with backups since 1.1p not restoring.

This update is being rolled out now. You can manually initiate the upgrade if you’d like, or it will automatically update overnight. Here is the full running changelog:

If you have any questions let us know, and as usual if you notice anything please feel free to reply here, or create a new topic, including the details of the issue encountered. Thanks!

2 Likes

Seeing an APIKey error in the main dashboard for site location:

Also the text on this error is nearly invisible unless highlighted as it’s white text on light gray background.

Updated my local hardware controller this morning. No issues.

1 Like

We aren’t seeing any AuthFailure issues in our testing. Can you grab the console output (F12, then Console)?

Issue looks like this breaks if running this behind a Reverse Proxy or on alternate DNS:

If you’re going to offer the ability to run this on custom DNS like this, the Maps API key should be configured to work with that as well.

Was a Device icon for ALTA CONTROL included?

We will need to add a Google Maps API key setting, along with instructions on how to obtain a key, to the settings to support reverse-proxy installs.

2 Likes

Just spotted this in the controller interface today, although this may only be in the cloud controller based on today’s release notes :slight_smile:

2 Likes

That would be great! I have the same issue and am using Nginx Proxy Manager.

Updated my local hardware controller this morning. No issues.

Me too, but if I lose internet access, the local controller goes blank.

Why won’t the local CONTROL work without the internet?

This is expected behavior, and is well documented that Internet access is generally required to use the controller. It is possible to run the controller isolated, and we are working on a KB article that should hopefully get published very soon. This is to provide the high level of security that Alta users expect. You will never see a broken lock when accessing your Alta controller settings, and this is a side-effect of that.

Controller updates are still not updating core ubuntu packages, whether they are in use or not. This has become a manual effort each and every update. When will this be corrected?

For example:

root@Control:~# systemctl status ssh.service
â—Ź ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2026-03-20 15:47:39 UTC; 1h 30min ago
Docs: man:sshd(8)
man:sshd_config(5)
Main PID: 1610 (sshd)
Tasks: 1 (limit: 2152)
Memory: 6.3M
CPU: 100ms
CGroup: /system.slice/ssh.service

root@Control:~# dpkg -S /lib/systemd/system/ssh.service;
openssh-server: /lib/systemd/system/ssh.service

Otherwise, the update went through without any real issues.

This is intentional, as we only apply security updates automatically. Applying non-security updates potentially requires manual intervention, with no security benefit. You are, of course, free to update all of the other packages as desired, on your own.