Jump to content

Custom Setup (IIS7)


Rowlett

Recommended Posts

Hi Guys,

 

i was wondering i have a website (www.domain.com) hosted with IIS7 and at the min mb3 works flawlessly on (www.domain.com:8080/mediabrowser, i was wondering is there anyway i could make MB3 available on (www.domain.com/mb3) i assume i'd need to config something within IIS and i've been trying to find info on google to no avail, just wondered if this could be possible or is it more trouble than it's worth? btw i dont mean just redirect to www.domain.com:8080/mediabrowser i mean so it hosts mediabrowser on www.domain.com/mb3 so no port needs to be specified.

 

thanks

Edited by Rowlett
Link to comment
Share on other sites

Good day,

 

Yes you can, from the IIS management, I think it in binding for the default site to edit (port) you can change that for whatever port/address you like to be as the main site for your domain.

 

Sorry, did not use IIS for some times now.

 

My best

Link to comment
Share on other sites

Beardyname

I think he means that he wants his standard server on domain.com and then it would only access mediabrowser if you added /mb3 or similar.

 

However i don't think this is possible since i would guess mb3 uses it's own webserver, if you only wanted what abobader was talking about though that is totally possible.

 

If I'm wrong please tell me as this would indeed be awesome ^^ but for now I'm gonna leave it as it is (8096)

Link to comment
Share on other sites

Good day,

 

Sorry I did not read it well.

 

In that case, see if your router can do that, that the only way.

 

My best

Link to comment
Share on other sites

Koleckai Silvestri

You don't really need to do anything fancy. You can install URL Rewrite in IIS and then use a web.config file to redirect all requests to the mb3 directory to the Media Browser server and port.

 

Something like:

 

<rewrite>
  <rules>
    <rule name="your name here" stopProcessing="true">
      <match url="^mb3/(.*)$" ignoreCase="false" />
      <action type="Redirect" redirectType="Permanent" url="http://yourmediabrowserIP:8096/mediabrowser" />
    </rule>
  </rules>
</rewrite>
</rewrite>

 

I do something very similar to redirect a subdomain on my VPS in Texas to my computer in California. Or instead of URL Rewrite you could use HTML, Javascript, Visual Basic or PHP to do the redirection as well.

  • Like 2
Link to comment
Share on other sites

The clients all assume that you are connecting on /mediabrowser, though, so they will likely not connect via the external address if you use something else.

Link to comment
Share on other sites

just use a framed page. but, fwiw, i think you're barking up the wrong tree in trying to do this in it's entirety

Edited by jcain
Link to comment
Share on other sites

thanks for all the responses guys! definitely different ways to approach this as you've all outlined, i really wanted to avoid the need to "input" the port and make it easier to remember the address and so if i changed the port internally it wouldn't affect the address. 

 

@wayne so from redirect you've post if i were to type: www.domain.com/mb3 it would then just redirect to www.domain.com:port/mediabrowser? 

 

also a dumb question would the web config of the default site need to be changed or a new one created within the mb3 server directory? really new to IIS7 :-)

Link to comment
Share on other sites

when i try the rewrite no matter what i put it says "doesn't match pattern" and tbf it will still need to display the port etc so might just leave it but thanks for all your help!

Link to comment
Share on other sites

Koleckai Silvestri

Hmmm.. I copied that off of stackoverflow to be honest. Should work. I will have to look at it more.  You can use an HTML meta refresh as well.

 

I set up something similar on my VPS to redirect the web client. For your handheld clients you'll probably want to use the IP as they can remember it. I don't put much effort in remembering my local IP so I put in the redirect. For local usage, I just bookmarked it. If I want to access from a friends house or something, I use the URL that I set up which is just a media.domain.tld setup and then an .htaccess file to redirect any request to my server inside the WAN.

Link to comment
Share on other sites

Thanks for info - in an ideal world it wud be nice to have it work on port 80 so u dnt have to specify the port on a web browser but i know this wud cause so many conflicts i was looking it to http headers n i know there's free redirect services i cud setup to make it easier. Might jst stick with the setup ive got, keep it simple:

 

https://domain.com = server essentials web access

http://domain.com:8080/mediabrowser = mb3

 

Reason i use 8080 is port 8096 is blocked at work by the firewall :-) n didnt really think it wud be suitable to submit an RFC to get it opened lol

Edited by Rowlett
Link to comment
Share on other sites

  • 2 weeks later...
Rowlett

just to update - i've managed to get http://domain.com/ to work as norm but if i go to http://domain.com/mediabrowser goes straight to MB3!! no need to specify port anymore! and MB3 is running fine on port 80 but IIS is still listening on port 80 too without conflicts so everything else on http://domain.com/subdirectory1,2,3 etc still goes to IIS... for added sec i was going to get mb3 running back on a custom random port and us ARR and url rewrite within IIS so that MB3 runs on say port 8881 but when browsing to http://domain.com/mediabrowser it goes to MB3 as expected but without it physically redirecting to :8881 address (so internal redirect) didn't want to risk it just yet as i've got it working and didn't know if it cud potentially effect streaming performance and logging etc...

Link to comment
Share on other sites

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...