Get help, report and discuss bugs.
-
GravityMan
- Posts: 7
- Joined: 20 Feb 2014, 07:14
Post
by GravityMan » 07 Mar 2014, 09:04
Is there anyway to mitigate or completely stop the web page timeouts I frequently get? The status bars will frequently stop changing with a 'Communication Error' and it takes an F5 hit to get everything back to normal.
Also, thanks hugbug for your awesome support BTW!
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 07 Mar 2014, 10:08
Is NZBGet on local network?
When you get errors, do you access the web-interface via HTTP or HTTPS?
-
GravityMan
- Posts: 7
- Joined: 20 Feb 2014, 07:14
Post
by GravityMan » 07 Mar 2014, 11:36
Usually HTTP I would think since its literally just IP:Port and no http/https in front.
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 07 Mar 2014, 12:02
So you have errors even in local network? Just leaving the browser open causes communication errors after certain amount of time? How long it lasts?
There is actually a code for such cases. If a communication error occurs, it retires several times before stopping with an error.
-
GravityMan
- Posts: 7
- Joined: 20 Feb 2014, 07:14
Post
by GravityMan » 07 Mar 2014, 12:13
I usually leave the browser open w/ NZBGet for extended amounts of time, so that may be it. It usually takes 1-3 reloads to get it to refresh properly or closing/re-opening another tab works. Yes, it does happen within my local network, although I'm just not on the time it takes before it becomes 'frozen'.
Who is online
Users browsing this forum: No registered users and 57 guests