Opened 14 years ago
Closed 11 years ago
#15674 closed defect (bug) (invalid)
Error when trying to logout
Reported by: | interconnect | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.0.2 |
Component: | General | Keywords: | reporter-feedback |
Focuses: | Cc: |
Description
I get this error when trying to logout of WordPress 3.0.1 & 3.0.2:
"This webpage is not available. The webpage at http://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. Must be some kind of bug, lots of reports about this in the forums.
See thread here: http://wordpress.org/support/topic/error-when-trying-to-logout?replies=9
Change History (6)
#2
@
13 years ago
- Keywords reporter-feedback removed
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
Reading though the support thread and it seems like it's a server issue.
this issue is actually related to one provider that has different brands. FatCow, iPower, StartLogic, they are all brands of Endurance International Group.
See also http://wordpress.org/support/topic/error-when-trying-to-logout/page/2?replies=9#post-2043606
#3
@
13 years ago
- Milestone set to Awaiting Review
- Resolution invalid deleted
- Status changed from closed to reopened
Hmm. Wondering if we can at least figure out what is going on.
Looking at the support forum thread, this appears to apply to some specific hosting configurations. I've left a comment on the thread waiting for someone with an affected host to get back to me with a test install/test account.