SABnzbget+sickbeard+couchpotato reverse proxy https-http

all that stuff sounds way too complicated...


why don't you simply port map the programs you want in your router then add the ports to your url

- SABnzb is running on port 8080 HTTPS

https://bartek.com:8080/sabnzbd/

- SickBeard is running on port 8081 HTTP no SSL support

http://bartek.com:8081/sickbeard/

- CouchPotato is running on port 5000 HTTP no SSL support

http://bartek.com:5000/couchpotato/

TeknoJnky wrote:
why don't you simply port map the programs you want in your router then add the ports to your url

Go back to the original post - it relates to forcing an HTTPS connection which you can't do purely via port forwarding

sphardy wrote:

Unfortunately not all web apps work well with reverse proxying. There's some more info here that might help: http://wiki.slimdevices.com/index.php/C ... cumentRoot Else - try setting up a subdomain and redirecting that to SBS as I know this works. eg if you setup the subdomain sbs.mydomain.com - your setup becomes: <VirtualHost *:80> ServerName sbs.mydomain.com ProxyPass / http://localhost:9000/ ProxyPassReverse / http://localhost:9000/ SSLEngine Off </VirtualHost>

What wonders me if this is problem of http to https redirection. Like I mentioned above I'm redirecting all traffic from 80 WAN to 443 Nas on router. Do I need to use mod_rewrite in that case if so, how it should be configured?

sphardy wrote:
TeknoJnky wrote: why don't you simply port map the programs you want in your router then add the ports to your url Go back to the original post - it relates to forcing an HTTPS connection which you can't do purely via port forwarding

And also restrictions @work

I really don't know - but you appear to be redirecting from HTTP to HTTPS and then back to HTTP. It's very possible you could hit issues.

Well not really. Router makes whole job right. No matter if you choose http or https you will land on 443. Then I'm going https to http (SBS). Correct me if I'm wrong. So in that case do I need mod_rewrite, since it's not Apache taking care of translating https to http and back?

have you tried enabling http on the nas? just because you have all traffic (http and https) going to to 443, may not mean that http should be disabled.

That's where things get confusing and I simply don't know.

For example if I enter the following address in my browser:

http://mynas:443/admin

I get this error

Bad Request Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please.

So I'm simply unsure what the limitations of redirecting HTTP traffic to a HTTPS port (or vice versa) are

@TeknoJnky - yes, right now I'm accessing it via http and it's not loading
@sphardy - ok but your example is clear as http defines you what port you will be using. Let's maybe focus on proxy alone, if I get this thing to work then I will try SSL.
The article you linked above is great, actually something I'm looking for the "problem" is that it hast to be old. There are files named HTTP.pm but none of them is even near SBS.

An update for those who are into this.
Current configuration:

Services on Nas:
- http - disabled
- https: enabled

Router settings:

- external 80 forward Nas 443
- external 443 forward Nas 443

Domain settings:

- nas.mydomain.com
- SSL certificate installed on nas for domain above

Running apps and configs:

- sabnzbd (localhost:2708) http
- couchpotato (localhost:5000) http
- sickbeard (coming soon)

Apache config:

<Location /sabznbd>
ProxyPass http://localhost:2708/sabnzbd
ProxyPassReverse http://localhost:2708/sabnzbd
</Location>

<Location /couchpotato>
ProxyPass http://localhost:5000
ProxyPassReverse http://localhost:5000
</Location>

Reverse proxy working like a charm redirecting any http request to https. No matter that if I go nas.mydomain.com or nas.mydomain.com/sabnzbd
Which leads to conclusion that SBS has some issues but I will work on it. It maybe be issue with javascripts and statics links but on Debian it's working. I haven't found module HTTPUrlMap in Apache or is it included in other module. Apparently Apache on Debian has this module separate.

EDIT:

SickBeard working too :)