Unifi has built its reputation on flexibility and ease of management for network devices. From access points to switches and security gateways, their products have long allowed network professionals to remotely manage and troubleshoot using familiar tools—SSH being one of the most trusted among them. That’s why the recent introduction of the USW-Ultra series—specifically the USW-Ultra-60w and USW-Ultra-210w— has raised some eyebrows in the community. One notable omission is the ability to SSH directly into these switches. In this post, we’ll dive into what this means, why it matters, and what workarounds exist.

What’s Changed?

When setting up many Unifi devices, one of the first steps after powering up the hardware is adoption. Traditionally, if a device doesn’t automatically discover your controller (or if you need to override its inform URL), you could log in via SSH using the default credentials (ubnt/ubnt) and run the set-inform command:

set-inform http://unifi.mycontroller.com:8080/inform
    

This simple command has long been a staple for network administrators managing devices in varied environments. However, with the new USW-Ultra switches, SSH access is no longer available. This isn’t just a cosmetic change; it directly impacts how you can adopt these devices into your Unifi network if they don’t automatically receive the correct inform URL via DHCP.

Why SSH Matters in Your Deployment

For many installations, especially those in remote sites or where network infrastructure is limited, relying on DHCP options (like DHCP Option 43) to push the inform URL isn’t always practical. Consider the following scenarios:

• Remote Sites with Limited DHCP Control: In many installations—especially those using ISP-provided routers or modems—there may be no ability to configure DHCP options.
• Ad-hoc Deployments: When you’re not physically on-site with the device, a remote SSH session has been a reliable fallback. Using tools like PuTTY or TeamViewer (to access a LAN PC), you could quickly log in, scan for the device’s IP, and run the necessary commands.

Without SSH, network administrators lose a key tool for troubleshooting and device adoption when the default DHCP method isn’t available. This is particularly frustrating when you consider that other Unifi devices— the USW-Flex, USW-24-POE, and even the UXG-Pro—continue to offer full SSH functionality.

Community Reactions and Workarounds

Since the issue first emerged about a year ago in the UI Community forums, several users have shared their experiences and creative workarounds:

1. Local Controller Spin-Up

One common workaround is to set up a temporary Unifi controller on a laptop:

1. Step 1: Connect a laptop to the same LAN as the USW-Ultra switch.
2. Step 2: Spin up a local controller and adopt the switch.
3. Step 3: Once adopted, change the “inform override” field in the controller settings to point to your primary (offsite or cloud) controller.
4. Step 4: The switch then shows up as “managed by other” in the correct controller, at which point you can use the SSH credentials provided by the local controller to finalize adoption.

While this process is a bit convoluted, it has been reported to work for those without DHCP Option 43 capabilities.

2. Mobile Adoption via the UniFi App

Another workaround that some users have found successful involves the Unifi mobile app:

1. Step 1: Ensure your smartphone is connected to the same network as the switch.
2. Step 2: Add your self-hosted controller’s account to the Unifi app.
3. Step 3: Use the app’s “devices” section to remotely adopt the switch.

This method is helpful for sites where a temporary local controller isn’t an option. However, it still requires you to be on the same LAN or VLAN as the switch, limiting its use in truly remote scenarios.

3. DNS CNAME Record

Another strategy is to add a CNAME record in your DNS server so that devices looking for unifi will resolve to your external controller’s address. For example:

unifi   CNAME   unifi.yourcontroller.com
    

If the Unifi device attempts to contact “unifi” on the local network, it will instead reach your external controller through that DNS record. This can be a straightforward solution if you have full control over your DNS server.

4. The Incomplete Documentation

A recurring theme in community posts is the frustration over the lack of documentation. The removal of SSH access isn’t clearly documented in the product literature, leaving many network professionals surprised and scrambling for workarounds. As one forum user noted, the ability to SSH into other Unifi devices has always been a reliable fallback. The sudden omission in the USW-Ultra series, therefore, feels like an oversight for those who deploy Unifi products in environments where DHCP option configuration is not possible.

What Does This Mean for Your Network?

If you’re planning a deployment using the USW-Ultra series, consider the following:

• Evaluate Your DHCP Capabilities: Can your current DHCP server (or your edge device) support the option to push the correct set-inform URL? If not, you may need to consider either a temporary controller or a different Unifi switch that supports SSH.
• Plan for Remote Management: For sites you cannot physically access, SSH has been indispensable. The lack of SSH in the USW-Ultra means that if your remote site doesn’t have a DHCP server with the required options, adoption could become a significant hurdle.
• Feedback to Ubiquiti: The community is vocal about this limitation, and user feedback is essential. If you find yourself affected by this change, consider providing direct feedback to Ubiquiti. Greater transparency and documentation could help avoid deployment headaches in the future.

Final Thoughts

The USW-Ultra series brings many of the strengths you expect from Unifi—robust hardware, attractive design, and high performance. However, the removal of SSH access represents a significant shift in how these devices can be adopted and managed, particularly in environments where DHCP options cannot be easily configured.

For network administrators who have long relied on SSH for the flexibility it provides, this change is more than a minor inconvenience; it’s a challenge that requires new processes and workarounds. Hopefully, future firmware updates or documentation revisions will address these concerns. In the meantime, being aware of the limitations and planning for alternative adoption methods is key to maintaining smooth network operations.

Have you encountered similar challenges with the USW-Ultra switches? Share your experiences and any additional workarounds in the comments below.