Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    The problem seems to have been sorted, but will check in the next few days before I give an answer. What I did was the following, but I do not understand why this seems to have sorted the issue. I ssh'd to the machine ran this command sudo iptables -L and then sudo service iptables stop and then sudo service iptables start, when I ran sudo service iptables stop it flushed the iptables which I never used and all of a sudden the problem resolved. The iptables did not have information in. Do you know perhaps why this solved the problem Commented Apr 27, 2012 at 13:18
  • So there is a firewall :) It is probably enforcing session timeouts differently than the web server. Commented Apr 27, 2012 at 18:07
  • Am not sure .. i had the problem once ... after almost killing myself i just upgraded and everything worked fine .... This thing can be crazy you know .. Am Glad i was able to solve your problem Commented Apr 27, 2012 at 18:13
  • "The remote server has sent you a RST packet", how do you know? Commented May 3, 2012 at 22:26
  • 1
    @Baba - Thanks for the help, eventually what solved my problem was by implementing it on a different server and that somehow solved the problem, thanks for really going out of your way to help Commented May 24, 2012 at 20:10