Cannot connect to start.local, possible BIOS looping

StartOS Support
1

Hello,
Before I start, I have read and googled everything I could find about the issue i am having to help me solve my problem.

I recently purchased a Start9 Server One. It came yesterday and I am having a bit of trouble getting it up and running. I pretty much got as far as opening it and getting the ethernet and power cord hooked up. I did not hear the “beep” and “chime” noises at all. I can’t connect to start.local to save my life.

I went into kiosk mode and basically all I saw was the BIOS menu with a handful of options. I am at a complete loss on what to do. I tried restarting it, unplugging it, letting it chill for 10-15 mins, and plugging it back in. Nothing is happening.

Any help and or feedback would be greatly appreciated.

EDIT: I made progress. I had to flash StartOS onto a USB and run it on the node. I have successfully connected it to the internet, but I am still running it in kiosk mode. I can access everything via kiosk mode, but cannot connect to the node though my desktop.

2

Just in case you missed it… when you made your order, right after you were invited to join the private support server. It’s there if you want it.

–

  1. The going to BIOS is suspicious, and may actually be related to it going unplugged for so long. I’d like to see you shut down the server, unplug it for some time as you did before, plug it back in and see if BIOS comes up again. If so, I’ll explain what this is and what steps we need to take.

  2. While the OS is flashed and running, so long as it is connected to the router, you should be able to reach it from anywhere. Remember, initial setup is as start.local, post setup you are given a unique .local to use instead. You also need to be on the same network as your other computers, and your network has to be configured to allow devices to connect to each other. Your desktop has to not be actively blocking access to your network with things like badly configured VPN clients. All common issues.

1 Like
3

Thank you for your reply!

I overlooked the unique .local address. I have successfully logged in on my desktop. And thank you again for reminding me about the private support server. I will keep that in mind for future reference.

Again, thank you very much! I believed my issues have been solved. :slight_smile: