Author Topic: An Error occured! Server error! (Bad Gateway)  (Read 14257 times)

Offline AndyInKent

  • Newbie
  • *
  • Posts: 4
An Error occured! Server error! (Bad Gateway)
« on: September 29, 2012, 05:26:34 PM »
Hi, been trying to get hmail & roundcube working on different computers.
I am now seeing the enclosed error, not showing any emails just an error :(

I have:
hmail on XP box
roundcube running on IIS Server 2003 R2

Logs in okay just this error

Offline AndyInKent

  • Newbie
  • *
  • Posts: 4
Re: An Error occured! Server error! (Bad Gateway)
« Reply #1 on: October 01, 2012, 04:25:38 AM »
Just to add to this, I have got another web based IMAP client working fine so my setup (backend) seems fine. I would like to use roundcube going forward but if I cant find a fix for this issue then I will drop roundcube and find another I like.

Offline alec

  • Hero Member
  • *****
  • Posts: 1,365
Re: An Error occured! Server error! (Bad Gateway)
« Reply #2 on: October 01, 2012, 05:10:40 AM »
"Bad gateway" sounds like an issue in your IIS Server. Check the logs.

Offline AndyInKent

  • Newbie
  • *
  • Posts: 4
Re: An Error occured! Server error! (Bad Gateway)
« Reply #3 on: October 01, 2012, 07:52:08 AM »
I have checked but cant see any issues, the only thing throwing errors is roundcube, all seems well with other webmail clients/apps.
Shame as I really like roundcube, looking like I will be going elsewhere though :(

Offline AndyInKent

  • Newbie
  • *
  • Posts: 4
Re: An Error occured! Server error! (Bad Gateway)
« Reply #4 on: October 02, 2012, 08:00:38 PM »
Weird thing is, I can see that its all working behind the scenes from the hmail log:



I just cant seem to work this out, I dont think the issue is on the IIS server as I have now got another web client (Afterlogic WebMail Lite) working on the same IIS server, but it isnt as good as RC and doesnt support sending via hmail.




Offline alec

  • Hero Member
  • *****
  • Posts: 1,365
Re: An Error occured! Server error! (Bad Gateway)
« Reply #5 on: October 03, 2012, 02:34:38 AM »
You have the error on ajax request for folder listing action (list), which is send just after displaying the UI. The log you provided doesn't contain any line related to this request, which means the server doesn't even start connection. So, it looks like http issue. Maybe some proxy is involved or IIS settings.

Offline JohnDoh

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2,855
Re: An Error occured! Server error! (Bad Gateway)
« Reply #6 on: October 03, 2012, 02:37:09 AM »
try looking in the roundcube error log.
Roundcube Plugins: Contextmenu, SpamAssassin Prefs, and moreā€¦

Offline henricds

  • Newbie
  • *
  • Posts: 3
Re: An Error occured! Server error! (Bad Gateway)
« Reply #7 on: November 13, 2012, 12:44:53 PM »
Hi,

It seems I have a very similar issue (except for the Bad Gateway part).
I upgraded from a perfectly working roundcube install to the latest 0.8.2 and now I can't even read my emails through roundcube (nor can I access the addressbook or calendar). I can receive and send emails normally through all email clients, so it's not likely a sudden issue just popped up with dovecot or postfix.
I'm running Debian Squeeze and there are no error messages in the logs which is making this impossible to debug. Anything I do through roundcube throws up the cryptic error message "An error occurred!  Server Error! (OK)"   ???

Anyone else having this issue with 0.8.2 ? Any ideas?

Thanks

Offline SKaero

  • Administrator
  • Hero Member
  • *****
  • Posts: 5,879
    • SKaero - Custom Roundcube development
Re: An Error occured! Server error! (Bad Gateway)
« Reply #8 on: November 13, 2012, 05:33:46 PM »
Whats in your error log? FWI the lastest version is 0.8.3.

Offline henricds

  • Newbie
  • *
  • Posts: 3
Re: An Error occured! Server error! (Bad Gateway)
« Reply #9 on: November 14, 2012, 11:56:38 AM »
Whats in your error log? FWI the lastest version is 0.8.3.
Thanks for replying. I just updated to 0.8.3 but the problem remains with the same Server Error! message described above.

My roundcube logs are showing everything's fine on roundcube's end (no errors whatsoever).
I did notice  that when I login now I seem to get stuck in an infinite loop where the error message keeps popping up continuously.
After further investigation, I notice my dovecot logs are showing that strangely roundcube keeps logging my user in and out every second.
This would suggest the problem lies with dovecot and/or apache, no?
The strange thing is that rouncube was working fine before the upgrade, so something broke with the update.


Mail logs (these keep repeating endlessly every second until I click logout in roundcube):

Nov 14 16:44:06 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=310/25559
Nov 14 16:44:07 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:07 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=44/790
Nov 14 16:44:07 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:07 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:07 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=379/1369
Nov 14 16:44:07 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=310/25559
Nov 14 16:44:07 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:07 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=44/790
Nov 14 16:44:08 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:08 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:08 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=379/1369
Nov 14 16:44:08 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=310/25559
Nov 14 16:44:08 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:08 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=44/790
Nov 14 16:44:08 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:08 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:08 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=82/860
Nov 14 16:44:08 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=310/25559
Nov 14 16:44:08 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:08 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=44/790
Nov 14 16:44:09 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:09 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:09 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=82/860
Nov 14 16:44:09 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=310/25559
Nov 14 16:44:09 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:09 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=44/790
Nov 14 16:44:09 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:09 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:09 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=82/860
Nov 14 16:44:10 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=310/25559
Nov 14 16:44:10 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:10 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=44/790
Nov 14 16:44:10 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:10 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:10 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=82/860
Nov 14 16:44:10 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=310/25559
Nov 14 16:44:10 pbx dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Nov 14 16:44:10 pbx dovecot: IMAP(testuser): Disconnected: Logged out bytes=44/790

Offline SKaero

  • Administrator
  • Hero Member
  • *****
  • Posts: 5,879
    • SKaero - Custom Roundcube development
Re: An Error occured! Server error! (Bad Gateway)
« Reply #10 on: November 14, 2012, 05:09:50 PM »
A server error will add a entry to <RC root>/logs/errors if the file doesn't exist make sure it is writable.

Offline alec

  • Hero Member
  • *****
  • Posts: 1,365
Re: An Error occured! Server error! (Bad Gateway)
« Reply #11 on: November 15, 2012, 02:34:54 AM »
Update to 0.8.4.

Offline henricds

  • Newbie
  • *
  • Posts: 3
Re: An Error occured! Server error! (Bad Gateway)
« Reply #12 on: November 15, 2012, 01:23:32 PM »
Well I have updated to 0.8.4 and the problem remains  :'(

I have turned all all logging capabilities and I can see IMAP logging in OK and pulling in the message headers, so I know that the issue is not with IMAP.

There are no errors in Roundcube log, nor in apache's log.

I'm pretty stumped as to what is going on. I imagine it's a simple misconfiguration somewhere but the lack of errors in the roundcube logs is frustrating.

Any more ideas?

Thanks

Offline berniel99

  • Newbie
  • *
  • Posts: 1
Re: An Error occured! Server error! (Bad Gateway)
« Reply #13 on: June 23, 2014, 08:43:02 PM »
Just for the record, I have just updated RC from 0.9.5 to 1.0.1 and am getting the same messages "Server Error. Bad Request", every 60 seconds.  I turned on all the debugging in Roundcube and looked at each of the individual logs created and there is no indication of an error occurring.

The system seems to work fine, reading all my mail and sending it.  It is just this message that comes up every minute that is the issue.  Was this ever resolved?