Question regarding connect functionality

[emmcd 6]

Greetings MB3'ers!

 

Got a question. First off, love the new connect functionality! That being said, I can only get it to work when I'm on my home network connection. Do I need to get remote access functionality configured or open up a port to get it to work on outside networks? I can login and it shows the server name, but when I click on it, it shows the little processing graphic and then ends up staying on the same screen.

 

Any thoughts? Thanks in advance!

[Luke 42079]

in the dashboard go to server -> settings. you can configure the public port that is mapped to the local server port.

 

we try to automatically map it with port forwarding and upnp but this doesn't work with all routers. so in addition to reviewing the configuration, you may also need to configure your router.

[emmcd 6]

Works great now and can access via the ip address as well so ended up getting a bonus with it.  Thanks for your help!

[MSattler 390]

in the dashboard go to server -> settings. you can configure the public port that is mapped to the local server port.

 

we try to automatically map it with port forwarding and upnp but this doesn't work with all routers. so in addition to reviewing the configuration, you may also need to configure your router.

 

Luke,

 

The only issue I have with this, is that it exposes all accounts to the world if someone port scans you.  Browsing to my DDNS address on 8096, I can then see all of my accounts, including those with no password.  For obvious reasons I don't want my kids having to use a password at home.

 

Is it possible to force all outside webtraffic, not secured through app.mediabrowser.tv to be forced to use a password?

 

Is my only bet to hide each account, and set the client to automatically login?  I can do that, but then what do I do for a Roku that uses connect to login?  I still would have to expose that account, so the roku user can select that profile?

 

 

Thanks!

[Luke 42079]

The MBS api has strong authentication. There is very little that someone can do unless they have your MBS password. Viewing the list of public users is one of them. If you don't want that information available, then you should hide the users. The hiding occurs at the api level, so anyone issuing http requests won't be able to get them.