admin_web - Won't login

[Mark Benson]

I installed the admin_web module from the modules repo on the development system I set up originally and it  worked okay. I just installed it on the production machine (same setup, different hostname) and it won't login at all, every attempt just dumps me back at the log on screen, even with a known good admin user. I checked and there is no difference in setup between them aside from the domain.

Anyone else had issues with this?

-- 

Mark

[Mark Benson]

I installed the admin_web module from the modules repo on the development system I set up originally and it  worked okay. I just installed it on the production machine (same setup, different hostname) and it won't login at all, every attempt just dumps me back at the log on screen, even with a known good admin user. I checked and there is no difference in setup between them aside from the domain.

Anyone else had issues with this?

Just adding a debug log from login process:

Jan 27 13:22:53 socket  debug   server.lua: accepted new client connection from 192.168.10.100:52656 to 5280

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/css/bootstrap-1.4.0.min.css

Jan 27 13:22:53 socket  debug   server.lua: accepted new client connection from 192.168.10.100:52657 to 5280

Jan 27 13:22:53 socket  debug   server.lua: accepted new client connection from 192.168.10.100:52658 to 5280

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/js/strophe.min.js

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/css/style.css

Jan 27 13:22:53 socket  debug   server.lua: accepted new client connection from 192.168.10.100:52659 to 5280

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/js/jquery-1.10.2.min.js

Jan 27 13:22:53 socket  debug   server.lua: accepted new client connection from 192.168.10.100:52660 to 5280

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/js/adhoc.js

Jan 27 13:22:53 socket  debug   server.lua: accepted new client connection from 192.168.10.100:52661 to 5280

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/js/main.js

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/images/prosody.png

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/js/strophe.min.js

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/js/adhoc.js

Jan 27 13:22:53 http.server     debug   Firing event: GET server.hidden/admin/images/blue_orange.png

Jan 27 13:22:59 socket  debug   server.lua: client 192.168.10.100:52661 read error: closed

Jan 27 13:22:59 socket  debug   server.lua: closed client handler and removed socket from list

Jan 27 13:23:31 http.server     debug   Firing event: GET server.hidden/admin/css/bootstrap-1.4.0.min.css

Jan 27 13:23:31 http.server     debug   Firing event: GET server.hidden/admin/js/jquery-1.10.2.min.js

Jan 27 13:23:31 http.server     debug   Firing event: GET server.hidden/admin/js/strophe.min.js

Jan 27 13:23:31 http.server     debug   Firing event: GET server.hidden/admin/js/adhoc.js

Jan 27 13:23:31 http.server     debug   Firing event: GET server.hidden/admin/js/strophe.min.js

Jan 27 13:23:31 http.server     debug   Firing event: GET server.hidden/admin/js/adhoc.js

-- 

Mark

[Kim Alvefur]

Hi,

This sounds like how it behaves if the JavaScript and other resources
have not been fetched, so make sure you run the get_deps.sh script first.

--
Kim "Zash" Alvefur

[Mark Benson]

Thanks. I knew I'd missed something stupidly simple ^_^.

-- 

Mark