Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] nzbget from LinuxServer

Featured Replies

Hi there

So I recently configured nzbget with sonarr and set it up to run. I went to check it this morning in Sonarr and noticed only 10% of the file had downloaded. When I went to the log files in nzbget, i see that i'm getting a bunch of errors and warnings. They keep piling up and a quick google search of the error codes did not help. Any suggestions?

 

here are the screenshots to see the logs:

http://i.imgur.com/e04rD7W.png

 

http://i.imgur.com/Ngoosg9.png

Screen_Shot_2015-09-28_at_12_56.59_PM.png.10af240e5ee8de8de453c0ecb43561cb.png

Screen_Shot_2015-09-28_at_12_56.59_PM.png.1894cdd719139780eb8e1e0289bcd193.png

  • 2 weeks later...

Just did an update on my container to the latest update and it broke the web interface.  I can't get into it no matter what.  I've tried restarting the docker multiple times and I've tried deleting the entire docker container and image and then re-adding it to no avail.

 

Suggestions?

Just did an update on my container to the latest update and it broke the web interface.  I can't get into it no matter what.  I've tried restarting the docker multiple times and I've tried deleting the entire docker container and image and then re-adding it to no avail.

 

Suggestions?

 

I'm having the same problem

Just did an update on my container to the latest update and it broke the web interface.  I can't get into it no matter what.  I've tried restarting the docker multiple times and I've tried deleting the entire docker container and image and then re-adding it to no avail.

 

Suggestions?

 

I'm also seeing the same thing. Here is what my log says currently:

 

-----------------------------------
GID/UID
-----------------------------------
User uid: 99
User gid: 100
-----------------------------------

Useing STABLE branch:
Not up-to-date\Installed
Checking som config options
Oct 13 10:58:28 36631ad01c85 syslog-ng[50]: syslog-ng starting up; version='3.5.3'

 

Looking at the Github repository, it looks like there were a handful of syntax changes this morning, so I'm wondering if one of them caused this to start.

Having the same issue...cannot start the container...

Just did an update on my container to the latest update and it broke the web interface.  I can't get into it no matter what.  I've tried restarting the docker multiple times and I've tried deleting the entire docker container and image and then re-adding it to no avail.

 

Suggestions?

Just did an update on my container to the latest update and it broke the web interface.  I can't get into it no matter what.  I've tried restarting the docker multiple times and I've tried deleting the entire docker container and image and then re-adding it to no avail.

 

Suggestions?

 

I'm having the same problem

Just did an update on my container to the latest update and it broke the web interface.  I can't get into it no matter what.  I've tried restarting the docker multiple times and I've tried deleting the entire docker container and image and then re-adding it to no avail.

 

Suggestions?

 

I'm also seeing the same thing. Here is what my log says currently:

 

-----------------------------------
GID/UID
-----------------------------------
User uid: 99
User gid: 100
-----------------------------------

Useing STABLE branch:
Not up-to-date\Installed
Checking som config options
Oct 13 10:58:28 36631ad01c85 syslog-ng[50]: syslog-ng starting up; version='3.5.3'

 

Looking at the Github repository, it looks like there were a handful of syntax changes this morning, so I'm wondering if one of them caused this to start.

Having the same issue...cannot start the container...

 

Im so sorry guys, the problem has been found, but now dockerhub does not wanna update at the moment, will let you know as soon as dockerhub starts behaveing. (or #linuxserver.io@freenode for live update)

Im so sorry guys, the problem has been found, but now dockerhub does not wanna update at the moment, will let you know as soon as dockerhub starts behaveing. (or #linuxserver.io@freenode for live update)

 

Thanks for the update, glad you're aware of it.  Hopefully this gets resolved soon.

Im so sorry guys, the problem has been found, but now dockerhub does not wanna update at the moment, will let you know as soon as dockerhub starts behaveing. (or #linuxserver.io@freenode for live update)

 

Thanks for the update, glad you're aware of it.  Hopefully this gets resolved soon.

 

Ubuntu fixed there mirrors which was causing an apt-get command to fail.  Updated and working for me now :)

Ubuntu fixed there mirrors which was causing an apt-get command to fail.  Updated and working for me now :)

 

Thanks.  I can confirm this is working after the latest update just now.

Latest update is working fine when I navigate to the internal ip website, eg, 192.168.1.5:6789 

 

But if I navigate to external website using apache proxy, it does not allow me to log in.

Latest update is working fine when I navigate to the internal ip website, eg, 192.168.1.5:6789 

 

But if I navigate to external website using apache proxy, it does not allow me to log in.

 

I had the same problem. I think its an NZBGet 16 issue.  I disabled the .htaccess on NZBGet in my apache proxy and used the built in one in NZBGet

Latest update is working fine when I navigate to the internal ip website, eg, 192.168.1.5:6789 

 

But if I navigate to external website using apache proxy, it does not allow me to log in.

 

I had the same problem. I think its an NZBGet 16 issue.  I disabled the .htaccess on NZBGet in my apache proxy and used the built in one in NZBGet

How exactly did you do that?

Latest update is working fine when I navigate to the internal ip website, eg, 192.168.1.5:6789 

 

But if I navigate to external website using apache proxy, it does not allow me to log in.

 

I had the same problem. I think its an NZBGet 16 issue.  I disabled the .htaccess on NZBGet in my apache proxy and used the built in one in NZBGet

How exactly did you do that?

 

In my proxy-config I changed it from

 

	
<Location /nzbget>
ProxyPass http://10.10.10.12:6789
ProxyPassReverse http://10.10.10.12:6789
AuthUserFile /config/.htpasswd
AuthType Basic
AuthName "NZBGet - Proxy"
Require user admin
</Location>

 

to

 

<Location /nzbget>
ProxyPass http://10.10.10.12:6789
ProxyPassReverse http://10.10.10.12:6789
</Location>

 

In NZBGet. Settings - Security  and add a "Control Username and Control password"

Latest update is working fine when I navigate to the internal ip website, eg, 192.168.1.5:6789 

 

But if I navigate to external website using apache proxy, it does not allow me to log in.

 

I had the same problem. I think its an NZBGet 16 issue.  I disabled the .htaccess on NZBGet in my apache proxy and used the built in one in NZBGet

How exactly did you do that?

 

In my proxy-config I changed it from

 

	
<Location /nzbget>
ProxyPass http://10.10.10.12:6789
ProxyPassReverse http://10.10.10.12:6789
AuthUserFile /config/.htpasswd
AuthType Basic
AuthName "NZBGet - Proxy"
Require user admin
</Location>

 

to

 

<Location /nzbget>
ProxyPass http://10.10.10.12:6789
ProxyPassReverse http://10.10.10.12:6789
</Location>

 

In NZBGet. Settings - Security  and add a "Control Username and Control password"

 

Awesome!  That was an easy fix.  Thanks Sean!

First off I just want to say thank you for such a great docker!

 

Secondly, this is what has brought me to the support forum.

 

After the most recent update I seem to be unable to unpack any files.

 

Is anyone else having a similar issue?

 

I noticed in the changelog that the unrar versions was updated to the latest version, wasn't sure if that was related.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.