Proxy Error

 I have a similar problem when I restart the elogd daemon. To fix that, I usually also restart Apache.

> Having made one entry in the thread about message ID, I could neither edit the entry or add an additional reply
> without getting "Proxy Error" messages.  I've had this trouble on this forum before, a long time ago.  Perhaps
> it is connected with the html coding?
Hi Stefan,

I now cannot even reply to you in the message id thread; I keep getting:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /elogs/Forum/.

Reason: Error reading from remote server

Apache/2.2.3 (Scientific Linux) Server at midas.psi.ch Port 443

It is, I think, something to do with the html coding (as I normally use plain, I don't come across this as an issue).

However, in the cause of the experiment, I will submit this entry, then go back and edit it, and if I don't get
Proxy Error, then that certainly will be something to do with the html coding.

And this is an extra edited line - if you see this, I got past the proxy error issue this time.  But did you get two
emails?

> > Having made one entry in the thread about message ID, I could neither edit the entry or add an additional reply
> > without getting "Proxy Error" messages.  I've had this trouble on this forum before, a long time ago.  Perhaps
> > it is connected with the html coding?
> Hi Stefan,
> 
> I now cannot even reply to you in the message id thread; I keep getting:
> 
> Proxy Error
> 
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request POST /elogs/Forum/.
> 
> Reason: Error reading from remote server
> 
> Apache/2.2.3 (Scientific Linux) Server at midas.psi.ch Port 443
> 
> It is, I think, something to do with the html coding (as I normally use plain, I don't come across this as an issue).
> 
> However, in the cause of the experiment, I will submit this entry, then go back and edit it, and if I don't get
> Proxy Error, then that certainly will be something to do with the html coding.
> 
> And this is an extra edited line - if you see this, I got past the proxy error issue this time.  But did you get two
> emails?

That is interesting.  I can make 1 (one) submission to a thread which uses html coding, then I get hit by proxy errors. 
But I can edit, play around or whatever if it is in plain coding.  Yet to see how many emails were generated...

> > > Having made one entry in the thread about message ID, I could neither edit the entry or add an additional reply
> > > without getting "Proxy Error" messages.  I've had this trouble on this forum before, a long time ago.  Perhaps
> > > it is connected with the html coding?
> > Hi Stefan,
> > 
> > I now cannot even reply to you in the message id thread; I keep getting:
> > 
> > Proxy Error
> > 
> > The proxy server received an invalid response from an upstream server.
> > The proxy server could not handle the request POST /elogs/Forum/.
> > 
> > Reason: Error reading from remote server
> > 
> > Apache/2.2.3 (Scientific Linux) Server at midas.psi.ch Port 443
> > 
> > It is, I think, something to do with the html coding (as I normally use plain, I don't come across this as an issue).
> > 
> > However, in the cause of the experiment, I will submit this entry, then go back and edit it, and if I don't get
> > Proxy Error, then that certainly will be something to do with the html coding.
> > 
> > And this is an extra edited line - if you see this, I got past the proxy error issue this time.  But did you get two
> > emails?
> 
> That is interesting.  I can make 1 (one) submission to a thread which uses html coding, then I get hit by proxy errors. 
> But I can edit, play around or whatever if it is in plain coding.  Yet to see how many emails were generated...

Hi Stefan,

I only got one email in response to the second entry of this thread, no email was received after the edit of the entry.  The
next email received was due to the third entry of this thread.

> I only got one email in response to the second entry of this thread, no email was received after the edit of the entry.  The
> next email received was due to the third entry of this thread.

Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):

1st reply to your entry.

1st reply edited.

> > I only got one email in response to the second entry of this thread, no email was received after the edit of the entry.  The
> > next email received was due to the third entry of this thread.
> 
> Ok, let me try (sorry to all the users who subscribe to this forum for pestering you...):
> 
> 1st reply to your entry.
> 
> 1st reply edited.

I got two email notifications, the second one I attached as a screen shot. So I don't know what happened in your case. The problem 
with the proxy is sometimes related to slow internet connections. If the HTML code transported over the internet has some delay 
between packets, the proxy server sometimes drops the connection. I don't know how to fix that in my Apache. If you edit in HTML, 
your browser downloads the JavaScript code and icons for the edit window, which is a lot of data, so the dropping is much more 
likely.

 I am currently having a similar problem. I am migrating a few separate elogs to one new computer. I have three top groups set up with their own password files. If I log into top group A (TGA), and then try to go to top group B (TGB), I am presented with a "Create new user" screen for my login name for TGA. When I complete that form, I am taken to the user settings for top group A, rather than TGB. I can log out of TGA and then log into TGB fine, but if I try to switch between them without logging out, it freaks out.

There seems to be a problem with the cookies that keep me logged into the different top groups not recognizing that they are different entities. I'm running eLog 2.9.1 rev 436. Is it possible that this has been addressed in 2.9.2?

Thanks,

-t

Certainly 2.9.1 and 2.9.2 should behave similar in that respect. Have you tried to clear all cookies in your browser and try again?

/Stefan