Reverse proxy URLs not handling correctly about chrome-deluge-remote HOT 4 CLOSED

If you're using https, then Nginx is probably configured to listen on 443. Try using port 443 in the extension options.

from chrome-deluge-remote.

I'm also using a reverse proxy for this. Instead of using the deluge port, it should work if you use the port number that your proxy is configured to listen on.

from chrome-deluge-remote.

I have opened the deluge port, just in case that may have been causing issues and set it up the way you have described as well. Here is my current setup using Nginx, and here is how I set it up in the extension options. I can access it normally by going to https://domain.com/deluge with my current setup, but I'm not for sure if the extension requires a port number to be passed through it. I currently use delugesiphon, which just requires a raw URL to be passed through it, instead of individual fields for a port and handle.

I get the same error when trying it with the port number included: "Unable to connect.."

from chrome-deluge-remote.

Seems like that solved the issue for me. Was not aware it would need the https selection on top of the 443 port. Thanks for the help!

from chrome-deluge-remote.