• Resolved interconnect

    (@interconnect)


    I get this error when trying to logout of WordPress 3.0.1 & 3.0.2:

    "This webpage is not available. The webpage at https://my.site.com/wp-login.php?action=logout&_wpnonce=12c23f0af8 might be temporarily down or it may have moved permanently to a new web address."

    and

    "Error 101 (net::ERR_CONNECTION_RESET): Unknown error."

    in Google Chrome and

    "The connection was reset"

    in Firefox. Both browsers running on Windows XP SP3. I tested this on another computer running Windows XP SP3 (different ISP) and got the same error in Firefox.

    Strangely, I do not get these errors at all on my Mac, in both Chrome and Firefox; they both logout correctly. It also works correctly on my iPhone.

    I’ve tried cleaning cache and cookies in both browsers, reseting my sub-domain in my host’s control panel, changing to the default theme; none of which worked at all.

    Anyone have an ideas? I’ve seen other posts regarding similar issues but with no resolution.

Viewing 15 replies - 46 through 60 (of 75 total)
  • This was a recent chat with FatCow Support.
    ==================================================
    Scott Morris: Hi Matt, my name is Scott. How are you today?
    Matt: Well, you?
    Scott Morris: How can I help you today?
    Scott Morris: I’m great, thank you.
    Matt: I currently have 4 WordPress sites hosted with FatCow and all 4 are having the same issue. When I log out of a site I am taken to a page that says: The connection was reset The connection to the server was reset while the page was loading. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer’s network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
    Matt: I did some research on www.ads-software.com forums and found that I am not the only one having this issue. Most people who are experiencing this issue report that they are with FatCow.
    Scott Morris: I apologize for any inconvenience this has caused you.
    Scott Morris: Could you please provide me with the exact URL of the web page in which you are receiving the error?
    Matt: I could give you a temporary sign on to one of my sites if you would like to test it.
    Scott Morris: Yes, please,
    Matt: Did you change something? …this issue has been happening for months…and now all of a sudden it is working normally.
    Scott Morris: I have not made any changes.
    Matt: nevermind…it’s doing it again
    Matt: https://mattandelise.com/wp-login.php?action=logout&redirect_to=http%3A%2F%2Fmattandelise.com%2F&_wpnonce=1ca59d517f
    Matt: site url is: https://www.mattandelise.com
    Scott Morris: Please provide me with the login
    Matt: temporary username and pasword are:
    Matt: u: xxxxxxxxx
    Matt: p: xxxxxxxxx
    Scott Morris: I have just logged into the WordPress Dashboard and then logged out but was unable to duplicate your issue,
    Matt: It did it to me again
    Matt: https://mattandelise.com/wp-login.php?action=logout&_wpnonce=1ca59d517f
    Matt: https://www.ads-software.com/support/topic/error-when-trying-to-logout?replies=46
    Scott Morris: Once I logged out from the WordPress Dashboard, I was redirected to the page at https://mattandelise.com/wp-login.php?loggedout=true
    Matt: that is a link to the WordPress forum where everyone is posting about the issue.
    Matt: what browser are you using?
    Scott Morris: I’m using Firefox version 4.0/
    Matt: same here
    Matt: I have been able to duplicate the issue in IE, Firefox, Opera, Safari and Chrome
    Scott Morris: Could you please clear the browser cache and cookies and then try to access it?
    Matt: trying now…
    Scott Morris: Okay,
    Matt: nope…still doing it
    Matt: I tried it on 3 of my 4 sites
    Matt: two different 3 different browsers
    Matt: *sorry 3 different browswers
    Scott Morris: Okay.
    Scott Morris: I have tried to log in and log out from different browsers from my end and was unable to duplicate the issue,
    Scott Morris: Could you please restart your local computer and then check this?
    Matt: No, I have been working on this issue for literally months now…I reboot my computer every day.
    Scott Morris: OKay.
    Scott Morris: Your website is working file and I can log in and log out to the Dashboard without any error.
    Scott Morris: Unfortunately we do not provide support for the WordPress application beyond assistance with the initial installation through “SimpleScripts”. We would recommend that you contact the WordPress support community found here:
    Scott Morris: https://www.ads-software.com/support/
    Matt: This is the same canned answer that everyone keeps getting from FatCow… is there not a way to escalate the issue?
    Matt: WordPress developers have also been working on the issue…which is more than we can say for FatCow.
    Matt: They are at least trying….
    Matt: I could understand if it was just me having this issue….but it’s clearly not.
    Scott Morris: Unfortunately, we have no access to isolate this from from our end and this is the reason we are diverting you to WordPress support/
    Scott Morris: I can understand your concern.
    Matt: Is there not a 2nd level support there?
    Scott Morris: Yes. we have./
    Matt: Can you not escalate the issue to them?
    Scott Morris: There is no use.
    Matt: Wow…
    Scott Morris: Our specialists also do not have access to the tools to fix the issue which is related to WordPress application,
    Matt: Thanks for nothing….
    Scott Morris: I apologize for any inconvenience this has caused you.
    Matt: yep

    Hey Matt,

    I know how you feel, I had almost the same support ticket trail, I had some customers complain so I moved off their websites to another server and guess what not one log out error!!!!! I am not sure why they can’t reproduce the fault? We all can . . . . .

    Cautiously Optimistic….

    Okay, here is what I have tried and so far it appears to be working…

    I modified my php.ini file in the following ways:

    1. Set the max script execution time to 90 seconds. ( It was 300 ).
    2. Set the php memory limit to 128m. ( It was 32m ).
    3. Verified that the session.save_path was pointed to the appropriate location. ( Mine, according to FatCow [for whatever that is worth] was correct ).
    4. Enabled (turned on) zlib.output_compression

    ***PROCESS***
    1. Log into your FatCow control panel and click “Scripting and Add-Ons” from the main menu.
    2. Click “CGI and Scripted Language Support”.
    3. Click “PHP Scripting”.
    4. Near the bottom of the page you will see an area highlighted in orange saying “Edit your php.ini file for PHP”
    5. I copied the entire text from the PHP.ini file into a blank text file so I had a handy backup.
    6. I then pasted that same text into Notepad++ which is a handy free code editor
    7. I then changed line 244 to: max_execution_time = 90
    8. I then changed line 246 to: memory_limit = 128M
    9. I then verified that line 881 was correct: session.save_path = /home/users/web/b318/moo.mysitecom/cgi-bin/tmp
    10. Finally, I changed line 126 to: zlib.output_compression = On

    ***Note – The line numbers I am referencing above are coming from Notepad++ not the PHP.ini file.

    I am going to try this for a week or so [fingers crossed]…

    ^
    Worked like a charm. Thanks Matt.

    Update: This is still working. The only thing I have noticed is a slight conflict with the W3 Total Cache plugin. It doesn’t seem to like the zlib.output_compression being enabled.

    Hey Matt,
    Glad the php.ini mods worked for you, my websites are all working fine now with no issues at this stage.

    Just to let you all know the edits for the PHP.ini file worked for me too. Thanks!

    Thanks squishy79!!! I tried each of your suggested php.ini changes individually, and the only one I needed was:

    zlib.output_compression = On

    FYI: This issue is not related just to FatCow – I use StartLogic and had the same issue. Interestingly, StartLogic also uses “SimpleScripts” to support their installs…

    Andrew

    (@andrewmartins)

    Squishy79 is my savior! This was driving me absolutely insane!

    Thanks squishy79!!! I tried each of your suggested php.ini changes individually, and the only one I needed was:

    zlib.output_compression = On

    FYI: This issue is not related just to FatCow – I use StartLogic and had the same issue. Interestingly, StartLogic also uses “SimpleScripts” to support their installs…

    I just want to share that my client has two sites both hosted at Ipowerweb
    and I am experiencing the same issue with the logout.

    I am about to apply the zlib.output_compression=on

    I wanted to share they use simple scripts as well.

    ***update****

    zlib.output_compression=on ….did the trick..

    I guess I will have to find a seo plugin that will work with this setting

    Since nobody else noticed, just to point out that this issue is actually related to one provider that has different brands. FatCow, iPower, StartLogic, they are all brands of Endurance International Group.

    I just want to say a massive THANK YOU for this help squishy79

    I am using startlogic and when testing my site, I could not log out as an admin or test subscriber, it was driving me mental!

    Followed your instructions (they work even via StartLogic)

    The only one I needed to change was: zlib.output_compression = On

    Thanks again!

    Hey folks, it is not a hosting issue. I have Dot5hosting and I get the same problem. I only get it with Firefox. When I use IE I get no errors. And when I contacted Dot5hosting support, they tried to duplicate the error using Firefox with no problems. So it has to be a bug in Firefox. I read many of your comments and it seems that you are using Firefox 3.1 and newer. Perhaps there is a bug in Firefox.

    I am going to check with Firefox and see where the error may be.

    Just to clarify… I had the issue on multiple browsers, not just Firefox.
    1. Firefox
    2. IE (7,8 and 9)
    3. Opera
    4. Chrome
    5. Safari

Viewing 15 replies - 46 through 60 (of 75 total)
  • The topic ‘Error when trying to logout’ is closed to new replies.