After installing, updating to a unique .local url and running without issue for months, I can’t access my Start9 (Server Pure 2023 model 4TB) locally or through Tor from my macOS machine using Firefox using standard, non-private mode.
It appears to power on, but based on what I’ve tried below does not appear to produce an IP visible to the local network.
I believe it started after we lost power briefly.
I’ve tried manually restarting.
I’ve confirmed through the mac System Preferences that Firefox has local access and cleared the cache. Browser message: ‘Hmm. We’re having trouble reaching that site’
Tor: I cleared the cache. Browser message: ‘Onion site not found’.
I also scanned all local IP addresses on the network using Angry IP with the Start9 server powered on and connected to the local network. Then unplugged and disconnected the Start9 and rescanned. And then powered on/connected the Start9 and rescanned. The scanner produced the same list of IP addresses each of the 3 times before, during and after disconnecting the Start9, so the Start9 does not appear to produce a detectable IP.
After a restart and waiting some time, does the server make bep when it is trying to connect and then a chime when it connects. If it does chime that means it is connected. You might try hooking a monitor up to it to see what is going on.
You can also open a terminal and try to ping it with ping -c 4 adjective-noun.local
Thanks for the help Rick. I wasn’t able to get a response using the terminal ping.
But was able to see what was happening when I connected a monitor and keyboard locally, then restarted.
I noticed errors in the cli log sequence including:
‘failed to read boot sector’
‘failed to recognize exfat type’
‘device has more than 2^32 sectors’
Then a long line of errors:
‘firmware: failed to load .ucode’
During startup, the system beeped 3 times, then after a minute or so, beeped 2 times then after another pause beeped 2 times, then after another minute or so beeped 2 times with the second tone sustained (doo-doooooo) and then redirected to the login page.
After logging in locally, I saw a system error showing and yellow banner with a ‘Clock Sync failure’ message.
I saw there was a related thread on this.
I haven’t made any changes on the router before or since on settings.
Unfortunately, the home router is managed by the service provider so I don’t have access – before I call and ask if they are blocking NTP, do you think there is something else wrong given all the errors during startup?
If you’re able to login with a monitor and keyboard, then the server is working. The issue seems to be that it is unable to connect to your network. If the server can’t connect to the network/router, this would explain the clock sync failure.
Did you poke around further? Under System → About you should see an IP address.
If you open certain services, so they show errors because they can’t connect to the internet?
You mention that you don’t have access to or control over your own router (equivalent to your ISP having a door key and your daily schedule) and that’s something you should probably resolve.