Unable to connect from multiple devices (previously fine)

Hi guys, I have followed every step in the FAQs and am at the point where it says ‘if cycling the servers power does not work please contact support’

Im running an Intel NUC i5 with StartOS and it has been running fine for about 3 months. I was able to connect from 2 phones and my windows desktop using the two word login and have been using the Services just fine

The NUC is on wired network and so is my desktop, both my phones are obviously wireless, and all have been able to connect fine.

Today I opened my browser and it shows a DNS_PROBE_ error on all devices.

Ive been through each of the troubleshooting steps, including reinstaling bonjour, attempting to connect to the servers ip address(unsuccessful)

I have finally rebooted the server manually power cycling it, but am still not able to login remotely. I have also tried start.local incase its in diagnostic mode but nothing.

The machine is on and showing CPU lights and fans whirring away - I guess i could do with some advice on whats next please? how can i be sure the server is on and running the OS and services to connect to?

No VPN, nothing changed from my devices side… any help please?

Update - I decided to plug a monitor into the NUC and it boots to

Then just a blank screen (waitid 10m to be sure)

I then attempted to boot into recovery mode and was presented with this screen

(will post in next reply due to limit of 1 photo per post)

And upon pressing enter, i just get a blank screen again.

Fubar’d? do i need to reinstall StartOS? or is this likely a failed disk?

Hi Elixir,

The DNS error typically means the server is at a different IP address than it was before, and that your client devices aren’t able to resolve the .local. As you saw in the documentation, for Windows, Bonjour is often the issue, but on most client devices, restarting them often seems to help.

The other thing mentioned in the documentation, which is suggested to do before trying kiosk mode, is to go into your router and look at connected devices. There you’ll find the IP address of the server and will be able to access the server directly that way and begin to work out what the issue is.

Kiosk mode sometimes fails with proprietary hardware… but really shouldn’t in your case, and I’m not seeing what the problem is there.

I’d turn off the machine unplug the monitor, turn on and look for the IP on the router. But you might find that by now the .local works.

Thanks stuart, I did reinstall bonjour, but this was happening on all devices including phones, so i wasnt expecting that to help, and it didnt.

As mentioned I did attempt to connect via the IP address that the router supplied, and was unable to connect, just got an unreachable error.

I rebooted the machine and the router and the same thing is happening, IP address appearing on router, unable to connect to it directly.

Whats concerning me is that (and i appreciate you guys say dont use kiosk mode, but i at least need to see whats happening upon boot) and it boots through bios, and then it starts to boot StartOS(as per pics above) but the screen goes blank - if i cannot connect remotely, and see nothing on the kiiosk view, how can i be sure that startOS is actually there and able to be connected to, and not just a failed image/disk.

Ive resigned myself to reflashing the image. If the disk if fubar at least ill know.

No dice…

Reflasing the image is not as big of a deal as you might think. Just use the “Use Existing Drive” recovery option.

https://docs.start9.com/0.3.5.x/misc-guides/attach-drive

Thank you Rexter, I will give this ago next weekend.

1 Like