very bad things
because that cost a couple of hours and still has me scratching my head, doubting my creds.
- with the client webpage endlessly spinning and not getting into setup,
- I open a new tab. I’m not avoiding whatever the installer got stuck on anyway.
- With a new tab open I head to my trusty
http://127.0.0.1:32400/web - or I hop on another LAN host and use
http://192.168.1.42:32400/web - Great success! I get a server setup screen, nearly instantly, like I would expect!
- Add a library? I love it. More success!!
- Mini cataloged the whole library before I could click through to done!!!
- I can see the new server in my
Authorized Devices!! - So now I’m in I’m in!!! I CaN sEe PlEx!
- No I am not.
- It turns out I’m given access to play things, to see things, but not to administer the server in any way, through secure https or not, on any app on any computer, on various operating systems from Linux to Unix.
- and that’s what got to me. It was really late at night and I never had control. I didn’t want to fight through what the browser might be doing. I wanted to try the terminal because Safari versus Opera versus Firefox was about to send me. As far as I was concerned, this route was broken too but was intertwined with the spinning tab.
- I get the exact same result if I start over fresh and close the spinning tab before I open the trusty url.
That’s when I went to the terminal, and used a brilliant solution from @ChuckPA, which was the website claim url + a curl on the server.
