Setting up Miva on nginx: unable to load configuration file

[ILoveHostasaurus]

I believe a symlink should work.

Try changing the password value to this ancient format hash: 11Z84oYEV4Jxk

That should result in your password being: changeit

Once you change the password it should go back to a normal pbkdf2/sha256

[Mike521w]

That password worked, I'm in!!!!!!!!!!!!!!!!!!!!!! Of course now I'm getting dozens of errors about cross origin problems even though I changed my hosts file. That's weird, all requests in Chrome's developer tools are going to the same domain.

For example:

Uncaught DOMException: Blocked a frame with origin "https://www.example.com" from accessing a cross-origin frame.
    at frameDocument (https://www.example.com/mm5/clientside.mvc?T=78b9d0fe&Filename=admin/ui.js:2414:32)
    at MMScreen.Scrape (https://www.example.com/mm5/clientside.mvc?T=78b9d0fe&Filename=admin/mmscreen.js:1427:14)
    at MMScreen.Event_FrameLoad (https://www.example.com/mm5/clientside.mvc?T=78b9d0fe&Filename=admin/mmscreen.js:3992:7)
    at HTMLIFrameElement.<anonymous> (https://www.example.com/mm5/clientside.mvc?T=78b9d0fe&Filename=admin/mmscreen.js:191:80)

I'll tinker with it some more on Monday, getting too late in the day to concentrate :)

[Mike521w]

Just wanted to update this thread for anyone who reads it in the future - the cross origin problems seemed to be due to the dev server's hosts file needing to also be modified to point to the dev IP address. Once that was done the cross origin errors stopped. Also see this thread for another correction I had to make to the conf file.