# Repeatedly getting Server disconnected message

**URL:** <https://community.sonatype.com/t/repeatedly-getting-server-disconnected-message/4743>\
**Category:** Sonatype Nexus Repository\
**Created:** [August 13, 2020, 2:11pm UTC](https://community.sonatype.com/t/repeatedly-getting-server-disconnected-message/4743 "2020-08-13T14:11:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chris.krull](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/chris.krull/32/1411_2.png) [@chris.krull](https://community.sonatype.com/u/chris.krull)\
**Post date:** [August 13, 2020, 2:11pm UTC](https://community.sonatype.com/t/repeatedly-getting-server-disconnected-message/4743/1 "2020-08-13T14:11:44Z")

</div>

Each time this url is requested - “[http://ourfakenexuserserver.com/service/extdirect/poll/rapture\_State\_get](http://ourfakenexuserserver.com/service/extdirect/poll/rapture_State_get)” I get a server disconnected toast in the upper right hand corner. The response is: ERR\_CONNECTION\_RESET.

[https://issues.sonatype.org/browse/NEXUS-22760](https://issues.sonatype.org/browse/NEXUS-22760) looks similar and we were on 3.20 when we noticed the problem yesterday. Updated to 3.26 and still seeing the problem. NEXUS-22760 notes the issue as Resolved in 3.22.

I don’t see anything in the logs that is meaningful to me and I could really use some help.

---

<div class="post-metadata">

**Author:** ![mpiggott](https://avatars.discourse-cdn.com/v4/letter/m/f0a364/32.png) [@mpiggott](https://community.sonatype.com/u/mpiggott)\
**Post date:** [August 13, 2020, 5:50pm UTC](https://community.sonatype.com/t/repeatedly-getting-server-disconnected-message/4743/2 "2020-08-13T17:50:50Z")

</div>

The issue fixed in 22760 was a performance issue where very large instances could have problems. You could check your request log to see if poll requests are taking a large amount of time.

If they are not timing out, you should check proxies, reverse proxies, adblockers, anti-virus, etc.

If they are timing out, you could try using jstack to capture what is taking time. If you have a support contract you could file a ticket for help.
