daneren2005 wrote:Set the http port to 0. Subsonic doens't run correctly if either http or https isn't set to 0, and https is set to 0 by default.
Depends on how you define "runs correctly". If both http and https are configured, Subsonic automatically redirects all requests using http to https.
wezman2k wrote:So...my work uses a websense filtering program to block the subsonic.org address.
I have found that if I use port 8080 without ssl i am able to access my server just fine. however, if i attempt to use port 8080 for https it doesn't work. i've tried changing the http port to 80, 8081 and several others. It's like 2 ports are needed for subsonic to work properly. one for http as well as one for https.
The questions are (1) should you try to bypass a policy set by your company? (2) what are the technical means used to enforce the policy? You must be aware that use of https makes it hard to impossible for the company to enforce a policy as one can also use https to tunnel any traffic and without terminating https traffic (possible, but few products, imho illegal without telling employees and disallowing private use of the internet).Thus it is possible that your company just blocks https, and then the automatic redirect above will prevent Subsonic to work unless you disable https.
However this is just speculation, you should probably just contact your IT and ask what the policy is and whether or how you can continue to use Subsonic without risking non compliance.
Best regards, jol
Subsonic 4.7 running on Acer H340 with LDAP authentication / Windows Home Server 2011 - Android client (3.5)