Hijacking this. Seeing this error too. I am using NGINX with https letsencrypt certs. It complains about mixed content not being loaded for security. When I disable security for my site and allow it to load the JS scripts, creating the first user also gives me that Object Object error.
No logs in emoncms.log or NGINX but the web console is screaming. Sorry for the messages in French, this is where i currently am. Though error messages should be straight forward. This is on Firefox.
L’utilisation d’XMLHttpRequest de façon synchrone sur le fil d’exécution principal est obsolète à cause de son impact négatif sur la navigation de l’utilisateur final. Consulter http://xhr.spec.whatwg.org/ pour plus d’informations.
jquery-1.11.3.min.js:5:25377
Chargement du contenu mixte actif « http://xxx/user/register.json » (non sécurisé) sur une page sécurisée[En savoir plus]
login:1:778
Blocage d’une requête multiorigines (Cross-Origin Request) : la politique « Same Origin » ne permet pas de consulter la ressource distante située sur http://xxxx/user/register.json. Raison : l’en-tête CORS « Access- Control-Allow-Origin » est manquant.
Got curious, tried with Chrome and also got Object Object with the following message in the web console:
jquery-1.11.3.min.js:5 Mixed Content: The page at 'https://xxxx/user/login#' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://xxxx/user/register.json'. This content should also be served over HTTPS.
Disabling https still has problems, when trying to create the new user, I get:
[Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ jquery-1.11.3.min.js:5
ajax @ jquery-1.11.3.min.js:5
register @ user.js?v=1:29
register @ login:259
(anonymous) @ login:214
dispatch @ jquery-1.11.3.min.js:4
r.handle @ jquery-1.11.3.min.js:4
I tried that script, i got an output of a change it made to the database, when I run it again nothing happens so I guess it worked.
It does however not solve my problems.
When I try to log in, it loads to the login prompt again, no errors anywhere.
Could you try updating emoncms again (master branch) and retry? There has been some new code merged today that might fix this, you may need to clear the browser cache too.
I tried the upgrade procedure. But it did not work.
I deleted all previous installation, and installed again, but still presenting the error in the login:
[object Object]
I also performed the procedure:
5.1) If you can not login
If you can not login, use the authentication bypass to run the updater.
Add the following line to the bottom of settings.php to enable special database update only, be sure to remove this line from settings.php once complete:
$ updatelogin = true;
In your internet browser open the admin / db page to launch the database update script.
Looking into this, the only way I can reproduce the error is if I disable Apache modrewrite, which results in the login screen not being able to find the user/login api end point.
I have now added further error catching to the login screen to display a more useful message:
It either displays a 404 error with a suggestion to check modrewrite or it prints the status code and error message if the error is not a 404.
@dmudo can you check that modrewrite is configured on your system?