# Moving from Ubiquiti to Alta world **URL:** \ **Category:** Stories\ **Created:** [January 31, 2025, 11:11am UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512 "2025-01-31T11:11:05Z")\ **Posts on this page:** 12\ **Page:** 2
**Author:** ![rafal.jachym](https://forum.alta.inc/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@rafal.jachym](https://forum.alta.inc/u/rafal.jachym)\ **Post date:** [February 4, 2025, 10:49pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/21 "2025-02-04T22:49:05Z")
> [@Alta-Josh](#): > > The goal would be to check connectivity from the Route10 out to other network destinations. Pings, traceroutes, iperf3 tests, etc. ok, my family went to bed so I had a moment to act: 1. I managed to connect Route10 to the controller after changing the address from my domain to [local.XXXXXXX.ddns.manage.inc](http://local.XXXXXXX.ddns.manage.inc), here I must point out that during the first configuration it did not want to connect to [local.XXXXXXX.ddns.manage.inc](http://local.XXXXXXX.ddns.manage.inc) for anything. 2. It worked but not completely, some services seemed to be cut off by the firewall - I assume so, maybe it’s a port issue, but I assume that if the panel allows you to set the port range, then this is a working forwarding, e.g. 192.168.150.29:20050-20058? 2.1 I lost the connection of Ubiquiti devices to their panel (also local). I could log in to the panel itself but all devices were offline. 3. As I mentioned, I configured static addresses on Route10 for individual servers, but for some reason they did not appear in the designated VLANS, only in e.g. 3 or 7 (I do not have such VLANS, the only VLANS I set were 10,100,150), but when I started to delete these static settings, I suddenly lost access to the controller and the Internet in general… I was most surprised by the lack of Internet… ---
**Author:** ![Alta-Josh](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-josh/32/2466_2.png) [@Alta-Josh](https://forum.alta.inc/u/Alta-Josh)\ **Post date:** [February 4, 2025, 10:54pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/22 "2025-02-04T22:54:33Z")
Can you minimize your network complexity to reproduce the issue? You have too many moving parts to diagnose. ---
**Author:** ![rafal.jachym](https://forum.alta.inc/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@rafal.jachym](https://forum.alta.inc/u/rafal.jachym)\ **Post date:** [February 4, 2025, 11:05pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/23 "2025-02-04T23:05:17Z")
> [@Alta-Josh](#): > > Can you minimize your network complexity to reproduce the issue? You have too many moving parts to diagnose. ok, my biggest problem: why after connecting route10 on the main link it connects to the controller only after setting the domain to [local.xxxxxxx.ddns.manage.inc](http://local.xxxxxxx.ddns.manage.inc)? Where at the same time other devices behind route10 i.e. S8 and Access points connect without a problem through my domain as well as through [local.xxxxxxx.ddns.manage.inc](http://local.xxxxxxx.ddns.manage.inc) to the controller. ---
**Author:** ![Alta-Josh](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-josh/32/2466_2.png) [@Alta-Josh](https://forum.alta.inc/u/Alta-Josh)\ **Post date:** [February 4, 2025, 11:09pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/24 "2025-02-04T23:09:31Z")
We need to reproduce the issue from first steps. On a factory reset Route10, when you configure it at `192.168.1.1`, what do you do in order to arrive at a disconnected Route10? At this stage, what connectivity remains and what connectivity is lost? Build a new, empty, blank site on the cloud platform. Can you reproduce the connectivity issue there? Then try again in your local controller. ---
**Author:** ![rafal.jachym](https://forum.alta.inc/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@rafal.jachym](https://forum.alta.inc/u/rafal.jachym)\ **Post date:** [February 5, 2025, 2:03pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/25 "2025-02-05T14:03:21Z")
> [@Alta-Josh](#): > > Build a new, empty, blank site on the cloud platform. Can you reproduce the connectivity issue there? Then try again in your local controller. On the cloud, the connection process works fine, no issues there. The problem arises when someone who buys the Route10 already has an existing network and cannot connect to the controller if their network is different from 192.168.1.1/24, because there is no option to define an initial network configuration. I cannot reproduce the problem in the cloud because when connecting to the cloud it does not matter what is inside the local network. But let’s leave all that aside, I got around the problem by using WAN2, I added Route10 to my local controller and I could configure it, but only by giving Route10 my address, entering the address local\*\*\*\*\*\*\*\*\*\*\*\* did not appear in the controller at all. After proper configuration, setting all the necessary VLANs and everything else, after specifying Route10 in my network, it communicates with the controller only through the local\*\*\*\*\*\*\*\*\*\*\*\*\*\* address, not mine. Which is quite strange, both point to the same server. ---
**Author:** ![Beaker](https://forum.alta.inc/user_avatar/forum.alta.inc/beaker/32/3062_2.png) [@Beaker](https://forum.alta.inc/u/Beaker)\ **Post date:** [February 5, 2025, 3:13pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/26 "2025-02-05T15:13:14Z")
I have my reservations about the first-time setup as it relates to brownfield or locally managed deployments. It seems to be tailored more for both greenfield cloud and local deployments. I started a post which never got traction. Maybe this will encourage the Alta folks to provide a much more flexible first time set up for locally managed networks. > [@First-time Setup Enhancements](https://forum.alta.inc/t/first-time-setup-enhancements/4321): > > Migrated this over to the Feature Request section. Possible enhancements for first-time setups not being performed via BT. These ideas are being presented at the basic level for all users to understand and chime in on. The objective is to collectively aid Alta with ideas and opinions to further enhance the new user experience. Ability to view an actively connected Alta “Control” device, along with other Alta devices on the splash page during the first-time setup of the Route10. This concept c… ---
**Author:** ![Alta-Josh](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-josh/32/2466_2.png) [@Alta-Josh](https://forum.alta.inc/u/Alta-Josh)\ **Post date:** [February 5, 2025, 7:12pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/27 "2025-02-05T19:12:32Z")
I think the difficulty to understand your issue is going to revolve around the address you keep describing. What is that domain, where is it defined, and what do you expect it to do? Is there only an issue with that in place? Can you please provide exact steps to reproduce on a minimal network from a factory default Route10 and a blank new site? ---
**Author:** ![Alta-Josh](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-josh/32/2466_2.png) [@Alta-Josh](https://forum.alta.inc/u/Alta-Josh)\ **Post date:** [February 6, 2025, 2:38pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/28 "2025-02-06T14:38:59Z")
Have you also configured the setting in this screenshot for your domain? It is related to using a custom domain but I’m not sure if you mentioned this. ![satty-2025-02-06_08:37:57](https://forum.alta.inc/uploads/default/original/2X/e/e28106474f864bb4c04be3ebefcb1a4e239ff0ed.png) ---
**Author:** ![rafal.jachym](https://forum.alta.inc/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@rafal.jachym](https://forum.alta.inc/u/rafal.jachym)\ **Post date:** [February 6, 2025, 4:38pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/29 "2025-02-06T16:38:10Z")
I understand. my English is not my native language, maybe I have gaps in English 🙂 Ok, I will point out that I will not reproduce the problem if I use the controller in the cloud, here it does not matter whether it is a connection via PPPoe or DHCP everything works perfectly, it connects immediately after configuring the WAN port. By the way, I am shocked at how fast it works. Great job. My and probably not only mine, the problem is when I want to replace my main router with Route10 where the controller is in a local network other than 192.168.1.1. When setting up the controller locally, I noticed that it created some long domain local.xxxxxxx.ddns… I configure services if I need them on my domains, e.g. [route10.mydomain.com](http://route10.mydomain.com), I have a public IP address that the domains point to, I found the option that you marked on the attached graphic and I use it, thanks to it I am able to log in to the controller from the outside, of course after configuring NGINX-PM. It works great, for the test I changed the addresses of AP6, AP6 PRO and S8 from the local.xxxxxx… domain to [route10.mydomain.com](http://route10.mydomain.com), all devices connect to the controller without any problems. (Still on Mikrotik) As for a Route10 (in my case), to fit it into my network, I have to configure it earlier. Thanks to the fact that I have an LTE modem, I can connect it to WAN2, set DHCP and add it to the local controller by connecting to the LAN port of Route10, entering the address 192.168.1.1 and then entering the address [route10.mydomain.com](http://route10.mydomain.com), I do the entire configuration. I change Mikrotik to Route10, the entered configuration works but what happens is that other devices connect to the controller without a problem, I remind you that they have the address [route10.mydomain.com](http://route10.mydomain.com) set, and Route10 connects only when via ssh I change its address for connection to local.xxxxxxx.ddns… I think it would be a good idea to add the possibility of at least partial configuration, such as setting the addressing for the network. Ideally, I would see a local panel on Route10, which we enter by entering the Route10 IP and as an option to connect to the cloud or local controller. I hope the problem with domains has been explained. ---
**Author:** ![Alta-Josh](https://forum.alta.inc/user_avatar/forum.alta.inc/alta-josh/32/2466_2.png) [@Alta-Josh](https://forum.alta.inc/u/Alta-Josh)\ **Post date:** [February 7, 2025, 10:07pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/30 "2025-02-07T22:07:31Z")
> [@rafal.jachym](#): > > I think it would be a good idea to add the possibility of at least partial configuration, such as setting the addressing for the network. Ideally, I would see a local panel on Route10, which we enter by entering the Route10 IP I am equally interested in seeing these options made locally available when a controller connection cannot be established. > [@rafal.jachym](#): > > Route10 connects only when via ssh I change its address for connection to local.xxxxxxx.ddns… I would like to again ask how you have configured this external domain. I shared a screenshot above that could be relevant, but you did not confirm for me yet. > [@Alta-Josh](#): > > What is that domain, where is it defined, and what do you expect it to do? Is there only an issue with that in place? This is the key info I’ve been looking for. ---
**Author:** ![rafal.jachym](https://forum.alta.inc/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@rafal.jachym](https://forum.alta.inc/u/rafal.jachym)\ **Post date:** [February 7, 2025, 11:58pm UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/31 "2025-02-07T23:58:18Z")
> [@Alta-Josh](#): > > I am interested in seeing these options available when a controller connection cannot be established. It cannot be established becouse Route10 search controler in own network wich is by default 192.168.1.1/24. Mine controller is in 192.168.150.8 (vlan150). > [@Alta-Josh](#): > > I would like to again ask how you have configured this external domain. I shared a screenshot above that could be relevant, but you did not confirm for me yet. Yes, I did, > [@rafal.jachym](#): > > I found the option that you marked on the attached graphic and I use it, the local.xxxxxx.ddns… domain was created automatically when creating the local controller. I created my domain myself and entered it into the controller in the place you indicated. ![image](https://forum.alta.inc/uploads/default/original/2X/7/7dd9a9b500e255d9315195a30e7086b6b11c411c.png) > [@Alta-Josh](#): > > This is the key info I’ve been looking for. the domain is defined on an external server where the main domain is parked > [@rafal.jachym](#): > > e.g. [route10.mydomain.com](http://route10.mydomain.com), I have a public IP address that the domains point to this is my domain to login in to controller from outside. And it does. The other Alta devices connect to the controller through my domain regardless of whether Mikrotik is the main router or Route10. This setting for Alta devices was implemented for testing purposes only. What Route10 does not do is connect through this domain when it is the main router, unlike the other Alta devices. good day to all ---
**Author:** ![system](https://forum.alta.inc/uploads/default/original/1X/087669c3d7c0a6495087b41d6f385a6771f2231c.png) [@system](https://forum.alta.inc/u/system)\ **Post date:** [June 11, 2026, 6:25am UTC](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512/32 "2026-06-11T06:25:20Z")
[Previous page](https://forum.alta.inc/t/moving-from-ubiquiti-to-alta-world/4512.md?page=1)