Help! Lost mini server network connection and can't get access to alter settings.

[Simon Still]

I've spent the day trying to change my router and wifi access points (to a Ubiquiti Unifi Cloud Gateway Ultra and wifi points) ahead of moving to a fibre connection. 

I'd previously got some devices on static IPs including the mini server, intercom video and intercom SIP.   The plan was to switch those all to DHCP, let them get IP addresses from my new router and then work on making them static and sorting out any bits of config that needed altering afterwards. 

(Side issue that may be related,  In theory I should be using my existing ADSL router in bridge mode with DHCP turned off, but I couldn't get that to work.  What I've got working for the rest of the network is 

TP LInk router serving DHCP on 192.168.0.x range

connected ONLY to my Unifi router on it's WAN port which is serving 168.1.x IPs. )

The mini server and intercom video haven't appeared on the new network (168.1.x range) BUT they don't seem to appear on the old fixed address either.  

I've tried 

- a search from config on the new network 

- connecting my laptop to the TPLink router so it's gets an 'old' ip address and searching there

- using a back up card in my minserver (surely the ip config is part of the OS on the card?) and connecting it directly to my laptop 

- isolating my old router from the new network, connecting my laptop and mini server directly to it, booting from a back up card that should have the old config (and networking details?)

None of it has worked yet.    The next step was going to be to reset the miniserver to factory settings using a spare card, but you don't seem to be able to create an 'empty' config and format it to a card unless you can connect to the mini server....

I'm out of ideas...

[Simon Still]

and I try again and I'm in... (connected directly to my old router) 168.0.ms

[.............So it's still on a fixed IP address on there.  but giving a message in red saying 'ip address invalid or not with in the standard gateway's network range.  Please sells an address outside your networks DHCP range to avoid conflicts'

If I try to change the IP address to the 168.1.anything (and also to change the primary dns to be 168.1.1  that red message stays up and it won't even let me hit 'send'. ................]

I seem to have finally got it to 'take', 

Tried again to change to DHCP,  then rebooted and quickly switched the cables between routers.  I

not really any the wiser as to how it's working now but I wonder if it was turning off 'external access' - when logging in locally it does seem to often go to the external route before local.  likewise had to add a new ms via search in my iPhone app even if it was connected to the local network 

[Simon Still]

Other weirdness.  

I don't seem to be able to log into the 192.68.xx.xx/admin page  despite being an admin account in the permissions.  Get a" Your user is not authorized to use the admin interface. You must have administration rights" message.  The account works fine to log in via the web for the UI, just not the admin page. 

[duncan]

Simon

if you change your ubiquiti router network setting to a netmask of /23 or 255.255.254.0, your range of IP addresses extends from 192.168.0.1 to 192.168.1.254 and you should be able to find any old or new addresses easily, but would need to change the tplink router to a different network range eg 192.168.0.3

then hopefully the ubiquiti controller will show all devices on your network or you should be able to use any network scanner, and then you can configure things properly - ive given up trying to use fixed ip in the devices and just use dchp and dhcp reservations in the ubiquiti controller to assign fixed ip addresses.

[Jonathan Dixon]

On Thu, 2 Apr 2026 at 11:42, duncan <joanne...@gmail.com> wrote:

Simon

if you change your ubiquiti router network setting to a netmask of /23 or 255.255.254.0, your range of IP addresses extends from 192.168.0.1 to 192.168.1.254 and you should be able to find any old or new addresses easily, but would need to change the tplink router to a different network range eg 192.168.0.3

Just note that doing this risks losing the use of the otherwise quite useful Unifi "Teleport" VPN. It's hard-coded to take over the  192.168.2.0/24 address range and won't budge itself to another adderss if you've (quite legitimately) used this for of your own LAN.

Having said that, 192.168.0.1/23 should just avoid conflict. But it's worth being aware of anyway. In my naivety (in fact, on an old USG prior to Teleport even existed) I setup a 192.168.0.0/20 for my LAN and now... no Teleport for me. But no matter, manual Wireguard setup is not so bad. I definitely CNBA to move my LAN to a new address range, for all the reasons listed in this thread, multiplied by a hundred other devices too 😅

then hopefully the ubiquiti controller will show all devices on your network or you should be able to use any network scanner, and then you can configure things properly - ive given up trying to use fixed ip in the devices and just use dchp and dhcp reservations in the ubiquiti controller to assign fixed ip addresses.

+1 .... although for robustness I've actually given the Miniserver an IP reservation outside of the Unifi "dynamic" allocation range, but then ALSO configured the miniserver to use this as its static IP. This way it's address is invariant whether using DHCP or not. And also still available for a few devices to connect direct to even if boots up when the USG is temporarily unavailable - e.g after a grid failure.

On Thursday, 2 April 2026 at 10:48:38 UTC+1 Simon Still wrote:

Other weirdness.  

I don't seem to be able to log into the 192.68.xx.xx/admin page  despite being an admin account in the permissions.  Get a" Your user is not authorized to use the admin interface. You must have administration rights" message.  The account works fine to log in via the web for the UI, just not the admin page. 

On Wednesday, 1 April 2026 at 19:07:57 UTC+1 Simon Still wrote:

and I try again and I'm in... (connected directly to my old router) 168.0.ms

[.............So it's still on a fixed IP address on there.  but giving a message in red saying 'ip address invalid or not with in the standard gateway's network range.  Please sells an address outside your networks DHCP range to avoid conflicts'

If I try to change the IP address to the 168.1.anything (and also to change the primary dns to be 168.1.1  that red message stays up and it won't even let me hit 'send'. ................]

I seem to have finally got it to 'take', 

Tried again to change to DHCP,  then rebooted and quickly switched the cables between routers.  I

not really any the wiser as to how it's working now but I wonder if it was turning off 'external access' - when logging in locally it does seem to often go to the external route before local.  likewise had to add a new ms via search in my iPhone app even if it was connected to the local network 

On Wednesday, 1 April 2026 at 18:43:14 UTC+1 Simon Still wrote:

I've spent the day trying to change my router and wifi access points (to a Ubiquiti Unifi Cloud Gateway Ultra and wifi points) ahead of moving to a fibre connection. 

I'd previously got some devices on static IPs including the mini server, intercom video and intercom SIP.   The plan was to switch those all to DHCP, let them get IP addresses from my new router and then work on making them static and sorting out any bits of config that needed altering afterwards. 

(Side issue that may be related,  In theory I should be using my existing ADSL router in bridge mode with DHCP turned off, but I couldn't get that to work.  What I've got working for the rest of the network is 

TP LInk router serving DHCP on 192.168.0.x range

connected ONLY to my Unifi router on it's WAN port which is serving 168.1.x IPs. )

The mini server and intercom video haven't appeared on the new network (168.1.x range) BUT they don't seem to appear on the old fixed address either.  

I've tried 

- a search from config on the new network 

- connecting my laptop to the TPLink router so it's gets an 'old' ip address and searching there

- using a back up card in my minserver (surely the ip config is part of the OS on the card?) and connecting it directly to my laptop 

- isolating my old router from the new network, connecting my laptop and mini server directly to it, booting from a back up card that should have the old config (and networking details?)

None of it has worked yet.    The next step was going to be to reset the miniserver to factory settings using a spare card, but you don't seem to be able to create an 'empty' config and format it to a card unless you can connect to the mini server....

I'm out of ideas...

--
You received this message because you are subscribed to the Google Groups "Loxone English" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loxone-englis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/loxone-english/29492c9d-3f06-4372-a49e-83d3e2fccb07n%40googlegroups.com.

[duncan]

it will work, you just have to avoid conflicts -  i have my subnet as /21 in ubiquiti, with reserved ip addresses up to 192.168.1.254, dhcp handed out from 192.168.3.0 onwards, teleport still works on the 192.168.2.1 range but i just dont use any of these 192.168.2.x range for any of my internal network devices. openvpn is set to 192.168.10.x 

[Jonathan Dixon]

Oh my goodness thank you duncan!  Lost count of how many times I tried that before without success.

Perhaps this has actually been improved since I tried: I was watching the overarching thread request to allow changing teleport address completely - which still isn't support.

Anyway yes just tried it again and seems to work fine. Just a wee trip wire to step around.... but the upside of using a /20 LAN is it's much easier to allow for carve-outs like this.

Cheers

To view this discussion visit https://groups.google.com/d/msgid/loxone-english/c75db4ac-126d-438d-8ab4-c951e9859518n%40googlegroups.com.

[Simon Still]

Thanks.  I think I've managed to find all the fixed IP devices and now have them with reserved IP's outside the range in CGU. Also taken my shelly plugs (actually shelly relays inside another smart plug casing) apart to connect a switch so I could get them back in setup mode!

I think I've kept it simple - 

Gateway is on 192.168.1.1

DHCP range is 192.168.1.50-254  and I'm using 2-50 for reserved clients. 

I've not changed the subnets.  Any issue with that?  

Outstanding issues - 

1) that weirdness of not being able to log into miniserverip/admin  despite my account having admin privileges 

2) I've got double NAT so none of my external access is working.   My TPLink Archer is connected to my Now VDSL broadband and still handing out DHCP on 192.168.0.xxx range.  Ideally I'd be running it in bridge mode but I can't find clear info on how to do it. 

Given I'm switching to FTTH with Plusnet in 10 days I shouldn't spend any time on it but it bugging me.  all I have to do in the TPlink is pick 'sky adsl' from a dropdown list of isps and it works.  no credentials, no Mac spoofing - none of the stuff that online forums seem to suggest other people require.