I’m never able to log into the UI as it never passes the login screen. My time is synced and it is up to date, just in case you think the issue may be the difference between the time on my client and the server.
Moving the login.js file from app in /usr/lib/one/sunstone/public to dist does not fix the issue. Though I would no longer see a 401 for login.js. Here is the version of the code I’m using:
I guess this was something new introduced just recently? Never had to do this before. I have a build from June which works without these steps. I’ll try these and see if everything works.
Anton, thanks for the reply. I always create the one_auth file for the one admin user before installation and DB initialization. This would afford me the definite ability to set the one admin password before. Does the install no longer post attention to the one_auth file created in the .one directory for the oneadmin user?
Will this be required in future builds, or should I go with RPMs from Epel for now? I only ask because, I’ve had issues in the past with RPMs and it seemed to me at the time when I first installed OpenNebula from source, the install was more straight forward and stable. It seems with this minified (I think this fixed was introduced due to an issue in Debian) process dependency, the installation is more complex and prone to errors. Is this something the Devs are in the process of cleaning up to make the install simpler, or this is just the norm if you are building from source from now and into the future?
Also for those of you who want to also do this please install nodejs and npm on CentOS by running the following: