Author Topic: [Solved] Zentyal WEB UI crashes when logging in  (Read 1389 times)

MOSEK

  • Zen Apprentice
  • *
  • Posts: 14
  • Karma: +1/-0
    • View Profile
[Solved] Zentyal WEB UI crashes when logging in
« on: January 22, 2015, 11:00:46 am »
Hey guys

I have had this problem for a month now, and I'm out of ideas on how to solve it.

When I connect to the web ui, of my zentyal server, I get the login screen as expected, but when I type in my credentials it just loads for a bit, and when gives me "504 Gateway Time-out". But I can still go back to the login screen no problem.

When the problem started I could refresh the page a couple of times, and then it would show the dashboard as it should, but now it won't let me through at all

Any of you who have experienced the same, and have a solution?


Here's my access.log:

Code: [Select]
127.0.0.1 - - [22/Jan/2015:11:08:33 +0100] "GET /favicon.ico HTTP/1.1" 200 1462 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36"
172.16.0.179 - - [22/Jan/2015:11:09:55 +0100] "GET /robots.txt HTTP/1.1" 504 176 "-" "Mozilla/5.0 (compatible; LinkChecker/8.6; +http://wummel.github.io/linkchecker/)"
172.16.0.179 - - [22/Jan/2015:11:12:47 +0100] "GET /Login/Index HTTP/1.1" 200 1125 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36"
127.0.0.1 - - [22/Jan/2015:11:13:08 +0100] "POST /Login/Index HTTP/1.1" 302 72 "https://nyborg/Login/Index" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36"
127.0.0.1 - - [22/Jan/2015:11:14:08 +0100] "GET /Dashboard/Index HTTP/1.1" 504 578 "https://nyborg/Login/Index" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36"
« Last Edit: January 27, 2015, 08:26:38 am by MOSEK »

MOSEK

  • Zen Apprentice
  • *
  • Posts: 14
  • Karma: +1/-0
    • View Profile
Re: Zentyal WEB UI crashes when logging in
« Reply #1 on: January 27, 2015, 08:26:08 am »
I figured out that a reboot solved the problem