Jump to content

Recommended Posts

Posted

Title says it all. Anyone accomplished? It feels that there is a setting missing in MBS for me to set the path?

Posted

Looked through the old forums and it appears that this may not be possible yet. Would love to log this as a feature request. Thanks in advance!

Posted

This would  be an excellent feature for management as I'd like to run the server on port 80 alongside the other things I have running via a reverse proxy in Apache.

Posted

Thanks for sharing. Sabnzbd, SB, CP, headphones, XBMC and basically everything else can be run over reverse proxy. I believe it takes the developers to add a "path" and then it works? Not sure though, but would be great to look into it. This would allow me to only open one port to the outside world.

 

Thanks a ton for looking into this!

Posted

Let me bump this one up. Asssume this may be a very easy "fix" for the developers to do and great benefit for those of us who don't want to open many different ports...

  • 7 months later...
Posted

Using Nginx as my reverse proxy, I have successfully set up the MB3 behind it. Here is how:

 

Add the following lines into your nginx config server block:

        location /mediabrowser/ {
                proxy_pass http://YOUR_MB3_SERVER:8096;
                include proxy_params;
        }
 
And then just reload the nginx:
>> sudo service nginx reload
 
Hope this helps.
  • Like 1
sydlexius
Posted

I can confirm that I am now able to get reverse proxy working with Apache Win32 2.4.x with the following settings:

 

<Location /mediabrowser>
order deny,allow
deny from all
allow from all
ProxyPass http://htpc:8096/mediabrowser
ProxyPassReverse http://htpc:8096/mediabrowser
</Location>

sydlexius
Posted

So after further testing, running through Apache isn't quite ready for primetime yet (at least, with the rule I created).  A number of items on the dashboard are missing, and Chrome gripes about running scripts from "unathenticated sources."  For purposes of playback and metadata management, it's still pretty useful.

  • 6 months later...
Posted

I just read through this thread. 

Sry to bump this but I see the problem with the setup in the past post right away. 

Reverse proxies are not meant to pass a directory along with the host and port and also must end with a /.

 

 

 
ProxyPass http://htpc:8096/
ProxyPassReverse http://htpc:8096/

 

Then access the apache server with a trailing /mediabrowser/ .

 

That should get you up and running. 

Now is it possible to get clients to support access to mediabrowser via SSL?

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...