Does not appear to be able to connect to plex servers behind reverse proxies

[Rhainland]

When adding a server thats behind a reverse proxy, plexripper indicate it cant create SSL handshake, it then attempts to add a DNS entry for some IP:443, which also fails.

E.g if the plex server is behind an nginx reverse proxy and remote access is disabled, thus the server exposes itself via plex on https://somerandomdomain.com - Plexripper is unable to connect

If i in plexripper DB change the following values;
PlexServers
address -> https://somedomain.com
host -> somedomain.com

Then go to UI, pick the server and click "check server status" then plexripper indicate it successfully connects;
Request to https://somedomain/identity?X-Plex-Token=TOKEN was successful!

However since the server wasnt added through the "normal" process in plexripper, no libraries are detected or shown.

[JasonLandbridge]

Thank you very much for this! Auto detecting this might be a bit difficult in the short term but I could add an option to manually add a reverse proxy domain to a server and then PlexRipper will use that to establish a connection.

On your last point, you can refresh accessible servers and libraries by going here:

Not sure if it works but otherwise I will fix it in a near update.

[Rhainland]

Thank you very much for this! Auto detecting this might be a bit difficult in the short term but I could add an option to manually add a reverse proxy domain to a server and then PlexRipper will use that to establish a connection.

On your last point, you can refresh accessible servers and libraries by going here:

Not sure if it works but otherwise I will fix it in a near update.

Thanks for your reply!.

Unfortunately refreshing doesnt work, that attempts to establish connection similar to first time you add the server, meaning it will replace the reverse proxy url that i manually added via db, with the attempted DNS fix(in this case ip:443 which will fail)

And so it just breaks the entire connection trying to do that.

Looking forward to your fix in the future, im excited to try this application out!

[JasonLandbridge]

No problem, any chance this server happens to be your own and you could invite me for testing a fix? I will have a dummy account which you can kick off after I have fixed this issue. No problem if you would rather not.

[Rhainland]

No problem, any chance this server happens to be your own and you could invite me for testing a fix? I will have a dummy account which you can kick off after I have fixed this issue. No problem if you would rather not.

It is not my own, so i cannot invite :(

[JasonLandbridge]

Okay no problem, this might sound a bit petty but I don't mean it like that at all. But I do need a server which has this configured to find and test a fix. I can maybe set one up myself, but that takes, I'm afraid, quite a bit of time. So I will keep my eyes open and I might be able to find a similar one.

If this server happens to be open for registration then please send an e-mail to PlexRipper@protonmail.com with details on this server. Then I can request access as well and investigate that way.

Thanks!

[Rhainland]

Okay no problem, this might sound a bit petty but I don't mean it like that at all. But I do need a server which has this configured to find and test a fix. I can maybe set one up myself, but that takes, I'm afraid, quite a bit of time. So I will keep my eyes open and I might be able to find a similar one.

If this server happens to be open for registration then please send an e-mail to PlexRipper@protonmail.com with details on this server. Then I can request access as well and investigate that way.

Thanks!

I have sent an invite to PlexRipper@protonmail.com now to a server thats behidn a reverse proxy

[JasonLandbridge]

Thank you very much! I am currently rewriting the download process code and resolving several issues with that. I hope with this I can also resolve the reverse proxy. If all goes well I should have a new update by the end of this week!

[Rhainland]

Thanks! Looking forward to it!

[Rhainland]

Any news on this one @JasonLandbridge ?

[JasonLandbridge]

@Rhainland , I wish I could give you some good news but next to my full-time job I have little time. On top of that, I am still working on the rewriting of the download process, which you can follow here: #90

I honestly did not expect it to be this much work, I have written 10000 lines of code so I must be doing something but I'm also breaking many things. From the 1st of November I'm taking a week off to renovate my house and any spare time in between I will spent working on PlexRipper.

I can't say how long it will take but I can guarantee that I am still working on PlexRipper!

[JasonLandbridge]

Okay that took way longer that I would have liked, this might be related to #108 , I will fix that one first and then check if that also solves the reverse proxy issue

[JasonLandbridge]

I think I have finally fixed this issue, with the new release you can now select which connection you would like to use in the server settings. This connection will then always be used when downloading.

A new release (0.10.0-RC-1) is available now on both the latest and dev docker channels, which contains all the changes/fixes from the past several months. Let me know if this fixes the issues.