start.local is only available during initial setup, and if the Embassy has gone into diagnostics mode. Unless you did some specific network setup, the IP address is dynamically assigned by your router, and may change.
Ideally, you should be connecting to your server’s unique-name.local address. Otherwise, you can look in your router’s list of connected devices to find the current IP address of your server. The one you mentioned, “start” should be it. But the information might be old. Try restarting your router. You can also scan your network with something like Angry IP Scanner.
I made an edit above. Please restart your router, to make sure the info is current. Then check to see if the IP address is the same. That IP should work. Please tell us about the device that you are trying to connect to your server from.
I see that you have an IP address reserved for your server, so it shouldn’t change. But being unfamiliar with your router, I don’t know if we are looking at an active device, or just a reservation for a device. Do you see any indication in the router that the device is actually active?
I’m not quite ready to say you need to reflash your server, but we may be heading in this direction. There may also be a hardware issue. But there is a tree of troubleshooting steps that would be appropriate to go through first. This forum may not be the best place to have this conversation. You may want to come see us at start9.me for live support, which you are eligible for using the redemption code on your Embassy.
It looks like your server may be in diagnostics mode. I’d like to know if the Mac you mention above was the same machine that you just ran the Angry IP scan with. If so, try using Safari, and type start.local in the address bar. If that doesn’t work, I’d like to know the error message. You might also try specifically http://start.local, or http://10.0.0.208. Again, I’d like to know the exact error messages.
Since we can’t get it to respond at all, I do think at this point you’re going to need to re-flash your server. Your SD card may be failing, so I’d recommend re-flashing to a new SD card. If your server is an SD card only model, you can attempt to transfer the service containers during the setup process, using an SD to USB adapter. If your server has an sd+ssd drive setup, you’ll simply choose “Use Existing Drive” during the setup to restore your server back to as it was.
Thanks. I re-flashed the micro SD card. I re-booted the device and heard the beep! I found the device via Chrome and Safari (not Firefox) via start.local . I have initialized Start OS with my old Samsung 1TB drive.
