NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NZBGet 17.1-1 App build available (Work In Progress)
I didn't want to take the tread from the manual install guide. There is good info in there and might have questions related to it. There were some issues that were reported with the inital 17.1-0 bu...
Another issue I noticed.
Click to update Nzbget from settings:
Currently installed: 17.1
Check failed. Please try again later.
I came out with one more package and I think I will send this to Netgear next week:
https://github.com/Mhynlo/nzbget/releases/tag/17.1-2
There is an update to the Debian package to make sure that it does not overwrite the NZBGet configuration file. That should help the users that are using NZBGet and want to update; they should not have to reconfigure everything again.
jhagg wrote:Does your package use the official repo and will updates work within the app?
Most of the package that I pulled together from various parts.
1) The main NZBGet repo was forked and I am managing the ReadyNAS packaging in a different branch. I don't touch the code, but this for will make it easy to update my repo when the time comes.
2) Since ReadyNAS is based on debian and debian packages; I pulled a bit of the debian repo's packages for the build process. (I am still learning and different tools to make packages easier.)
bobaloca wrote:Can you build it with OpenSSL?
The current implementation was mentioned from the NZBGet guide:
https://github.com/nzbget/nzbget/wiki/NZBGet-behind-other-web-server
The configuration is set to allow https connections since it is an apache proxy connection.
bobaloca wrote:
Check failed. Please try again later.
I have seen this issue, but it seems like something that is closer to the NZBGet side.
I filed an issue in my repo for better tracking so I can see if there is something in the config that I am missing, or if there is something more genaric.
https://github.com/Mhynlo/nzbget/issues/3
Mhynlo wrote:I came out with one more package and I think I will send this to Netgear next week:
https://github.com/Mhynlo/nzbget/releases/tag/17.1-2
There is an update to the Debian package to make sure that it does not overwrite the NZBGet configuration file. That should help the users that are using NZBGet and want to update; they should not have to reconfigure everything again.
Unfortunately, I'm having to reconfigure. No big deal though -- appreciate your work here!
bobaloca wrote:Can you build it with OpenSSL?
The current implementation was mentioned from the NZBGet guide:
https://github.com/nzbget/nzbget/wiki/NZBGet-behind-other-web-server
The configuration is set to allow https connections since it is an apache proxy connection.
The reason I was hoping for this was because I wanted to connect to my newsserver securely. (Basically, set the servers.encryption to Yes under News-Servers)
Thansk for your work on this!
p.s.
Under "Extension Scripts" there appear to be a bunch of duplicate settings that are already in "Categories". This causes the .conf file to have duplicate entries and an error to be thrown in the log.
I installed 17.1.1 and was getting the error 'TLS handshake failed: Error in the system's randomness device.' when testing my news server.
Then I tried 17.1.2 and I'm still having the same problem.
This is exacly the issue I'm having. Getting the error "TLS handshake failed: Error in the system's randomness device." When I go back to port 119 and turn off encription then it connects to the news server. But When I'm on port 563 with Encription turned on, I get this error. It worked just fine on a older version of NGBGet I had been using and looks like I'll have to go back to it. So I hope this bug can be fixed.
Also loading in the config file from the older version will cause problems with this new version, so it looks like I'll have to do everything manually. Until this issue it fixed, I have to go back to the old version where Encription works problem free.
I looked into the TLS issue and it was dirrectly tied to the OpenSSL bit. There were some other areas that needed the OpenSSL support (Update Check).
https://github.com/Mhynlo/nzbget/releases/tag/v17.1-4
It looks like I might need to look into newgroups to better test this myself for future releases.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
