Get help, report and discuss bugs.
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 03 Sep 2017, 14:47
-
Tundor
- Posts: 10
- Joined: 02 Sep 2017, 08:42
Post
by Tundor » 03 Sep 2017, 15:18
Just did the first test on the local machine and it works fine, after picking up the IPV6 address from the logfile.
Thank you so much.
*edit*
Accessing the webinterface via
http://localhost/6789 works as well, i just need to add "::" to the AuthorizedIP to get this running.
-
Tundor
- Posts: 10
- Joined: 02 Sep 2017, 08:42
Post
by Tundor » 03 Sep 2017, 15:35
It seems like my connection via HTTPS is not working anymore (i'm using it for accessing it remotely). HTTP works. Can that somehow be related to the changes?
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 03 Sep 2017, 17:52
The change affects displaying of IP (in a warning) and how AuthorizedIP checks the IP. The connection should work the same.
However in this latest version the build system was changed in order to provide 64 bit build. In particular OpenSSL was upgraded and is now linked statically. Although HTTPS should work as before everything is possible. At best install the version you were using before and test SSL. At best make a backup of QueueDir before downgrading.
-
Tundor
- Posts: 10
- Joined: 02 Sep 2017, 08:42
Post
by Tundor » 03 Sep 2017, 18:49
I reinstalled the latest stable release for testing purposes. The https connection is working directly. Back on
nzbget-20.0-testing-r2092M Version my chrome ist telling me "ERR_CONNECTION_RESET" when trying to open the interface with https on port 6791.
I'll stick with the testing build for now though, since the AuthorizedIP thingy is currently more important to me.
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 03 Sep 2017, 19:19
SSL should be working now:
https://drive.google.com/file/d/0BwVEk7 ... sp=sharing
Tundor wrote: ↑03 Sep 2017, 15:18
Just did the first test on the local machine and it works fine, after picking up the IPV6 address from the logfile.
Can you post an example of what the reported IP looks like?
-
Tundor
- Posts: 10
- Joined: 02 Sep 2017, 08:42
Post
by Tundor » 03 Sep 2017, 19:32
Can you post an example of what the reported IP looks like?
Just samples, I changed some random numbers, but those are the patterns:
::3a02:3450:202a:5c4:12db:2d15 <-- When accessing it via IPV6 address in the browser
0:0:ab80::b1a0:bde4 <-- When accessing it via dns from the local machine (
http://pc-name:6791)
:: <-- When accessing via localhost:6791
HTTPS seems to work again now, thanks for the fix.
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 03 Sep 2017, 19:37
Thanks for testing.
I'm glad you tested this before I published a testing release.
-
Tundor
- Posts: 10
- Joined: 02 Sep 2017, 08:42
Post
by Tundor » 03 Sep 2017, 20:12
Happy to do so
. Thanks for the great support!
Who is online
Users browsing this forum: No registered users and 64 guests