- Joined
- Nov 5, 2020
- Messages
- 11
- Reaction score
- 1
Hello, we have a locally hosted 3cx server.. Everything seems to be almost completely fine except for the web client/browser extension keeps disconnecting ("Disconnected. Waiting for network.") every ~2.5-~10 mins causing the browser extension/plugin(? I'm going to keep calling it a browser extension) to close out and then reopen a few seconds later, which forces the current focus onto that extension window, dragging me out of what I'm currently working on.
I've pulled up the chrome dev tools and watched the network tab. It seems to be the web client switching/upgrading protocols(http status code: 101). In the console when this happens it's printing a "CloseEvent" with a JSON object of accompanying information:
I've redacted or closed some elements to cut off circular references.
From this I'd assume there is an issue maintaining the web-socket connection. But both my machine and the server are on the same local network. 3cx is hosted on a windows server on a Hyper-V VM in our it office on ethernet and my machine is also connected to the network via ethernet.
On top of this I've noticed my handset(cisco SPA 508g, I know it's a legacy device but I'm trying my best to maintain the ability to use these.
) looses it's registration and takes a few minuets to re-register. But this happens much less than the web-client disconnecting. I've also completely taken the handset offline to see if multiple devices trying to use one pbx extension was the issue.. Unfortunately nothing changed on the web-client. 
Has anyone also experienced this issue before? What should I check to try and correct this? Any help is highly appreciated.
I've pulled up the chrome dev tools and watched the network tab. It seems to be the web client switching/upgrading protocols(http status code: 101). In the console when this happens it's printing a "CloseEvent" with a JSON object of accompanying information:
JSON:
{
bubbles: false,
cancelBubbles: false,
cancelable: false,
code: 1006,
composed: false,
currentTarget: WebSocket {__zone_symbol__openfalse: Array(1), __zone_symbol__messagefalse: Array(1), __zone_symbol__ON_PROPERTYopen: ƒ, __zone_symbol__ON_PROPERTYmessage: ƒ, __zone_symbol__ON_PROPERTYclose: ƒ, …},
defaultPrevented: false,
eventPhase: 0,
isTrusted: true,
path: [],
reason: "",
returnValue: true,
srcElement: WebSocket {__zone_symbol__openfalse: Array(1), __zone_symbol__messagefalse: Array(1), __zone_symbol__ON_PROPERTYopen: ƒ, __zone_symbol__ON_PROPERTYmessage: ƒ, __zone_symbol__ON_PROPERTYclose: ƒ, …},
target: WebSocket {__zone_symbol__openfalse: Array(1), __zone_symbol__messagefalse: Array(1), __zone_symbol__ON_PROPERTYopen: ƒ, __zone_symbol__ON_PROPERTYmessage: ƒ, __zone_symbol__ON_PROPERTYclose: ƒ, …},
timeStamp: 730226.3550000062,
type: "close",
wasClean: false,
}From this I'd assume there is an issue maintaining the web-socket connection. But both my machine and the server are on the same local network. 3cx is hosted on a windows server on a Hyper-V VM in our it office on ethernet and my machine is also connected to the network via ethernet.
On top of this I've noticed my handset(cisco SPA 508g, I know it's a legacy device but I'm trying my best to maintain the ability to use these.
) looses it's registration and takes a few minuets to re-register. But this happens much less than the web-client disconnecting. I've also completely taken the handset offline to see if multiple devices trying to use one pbx extension was the issue.. Unfortunately nothing changed on the web-client. Has anyone also experienced this issue before? What should I check to try and correct this? Any help is highly appreciated.
Last edited:
