MikeTech 0 Posted May 25, 2017 Share Posted May 25, 2017 (edited) Managed to trash my server somehow in one move, made one setting change (public https port number) in the process of setting up https in advanced, saved setting, clicked restart, and it hung there without restarting. Did system reboot, etc. all the standard stuff, app would seem to run, but refused to stay open when attempting to open dashboard, could see it drop out of processes in Activity Monitor when accessed. Tried reinstall of latest package, still no joy. The only thing I could think of as a factor is the machine OS was recently updated to 10.12.5, but emby seemed to be working fine after that update until I tried the config change/restart. Tried restoring emby app and emby-server files in ~/.config using Time Machine backup from yesterday, no dice. On the theory of it being an issue with 10.12.5, I did a complete system restore from yesterday prior to the update to bring it back to 10/12.4, and that didn't work either. So, I trashed the app file and the emby-server config file again, and started an install from scratch. That seems to be working just fine, but it's going to take me several hours to get back to where I was, and will have lost track of a bunch off-air recording data, etc. What is going on here that I'm missing in terms of where files are located? And why is this config so difficult to restore from a backup? Edited May 25, 2017 by MikeTech Link to comment Share on other sites More sharing options...
MikeTech 0 Posted May 25, 2017 Author Share Posted May 25, 2017 Figured it out. Jumped back and restored the later version of the backup, then only replaced the users folder and the system.xml in the ~/.config manually from the older backup, all better now. Time Machine isn't always so good at replacing hidden files, even when the flag is set to make them visible, manual method works. I restored the whole emby-server folder to the desktop, then moved the files one at a time manually. Link to comment Share on other sites More sharing options...
Luke 36992 Posted May 25, 2017 Share Posted May 25, 2017 Thanks for the feedback. I'm surprised changing that setting caused an issue. I'll do some testing. thanks ! Link to comment Share on other sites More sharing options...
MikeTech 0 Posted May 25, 2017 Author Share Posted May 25, 2017 It may have been more than one factor, I could PM you copies of the "bad" system.xml file and/or the users file if they are any use, not files I'd want to post publicly. Link to comment Share on other sites More sharing options...
Luke 36992 Posted May 25, 2017 Share Posted May 25, 2017 If you could just let me know what settings you changed that's more than enough, thanks. Link to comment Share on other sites More sharing options...
MikeTech 0 Posted May 25, 2017 Author Share Posted May 25, 2017 (edited) Already sent. Trash 'em if you like. What I changed was https server and public port to 443. At least according to system.xml that I just read. Edited May 25, 2017 by MikeTech Link to comment Share on other sites More sharing options...
Luke 36992 Posted May 25, 2017 Share Posted May 25, 2017 Thanks for the info. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now