Port Issue Since Update

[arche 176]

I am still using port 80 on the latest dev version, is there any other settings you have active in the advanced settings?

[Rowlett 9]

log from official release (working) version:

 

http://paste2.org/5gzEBUKW

 

@ no nothing else in advanced settings apart from run server at startup. i do however under server have: Enable automatic port mapping enabled (although i have got port 80 manually forwarded on router anyway) and external ddns set to hostname 

Edited August 12, 2014 by Rowlett

[arche 176]

This will only pertain to my setup, but I have port 80 specified but have "Enable automatic port mapping" disabled. I have nothing entered into "External DDNS". I am using a thirdparty DNS service to forward my domain to my IP. Not ideal, but has been working for me. Maybe you can try it and see if it helps. Also check with http://www.canyouseeme.org/ and make sure you can been seen from outside with port 80 open.

[Rowlett 9]

tried changing the settings to match but still the same (on beta version) :-( i did just check canyouseeme.org and port 80 is open :-) and not blocked by ISP (obviously lol!)

[arche 176]

Sent you a pm with a question.

[Rowlett 9]

i assume it's this?

 

2014-08-13 00:31:49.9968 Error - ServerManager: An attempt was made to access a socket in a way forbidden by its access permissions

System.Net.Sockets.SocketException

[Rowlett 9]

Hi All,

 

been running so awesome i haven't posted in so long!!! Since upnp was introduced i've been happily using port 80 and it's been a breeze but since recent dev/beta releases i now get "Service Unavailable http 503" when using port 80.

 

Currently on latest dev Version 3.0.5337.24489

 

It also happens in latest Beta Version currently available

 

but official release STILL works. reason i need to use port 80 or 443 is every other port is blocked where i tend to use MB3.

 

it did still work with previous Beta too (sorry i can't remember the rev :-( )

 

is there a way it could still work with port 80 or is that a thing of the past?

 

btw it does work using default 8096 on all revisions :-) somethings changed in the way it binds the port i assume?

 

Log from dev Version 3.0.5337.24489:  http://paste2.org/Z3jtbWmd

 

i'm happy to use official release version of course but concerned going forward official release will stop working too which is why i've posted :-)

Edited August 12, 2014 by Rowlett

[Rowlett 9]

any ideas anyone? :-(

[Rowlett 9]

i found a workaround kind of until i can use port 80 again, setup an IIS url rewrite rule {PATH_INFO} matches pattern /mediabrowser/? and if it matches rewrite to:

 

http://SERVERNAME:8096/{R:1}

 

not ideal and probably going to get a performance hit. can't get it to rewrite from http either for some reason lol so:

 

https://domainname/mediabrowser works but http://domainname/mediabrowser doesn't

 

also things are broke like system paths and links on dashboard aren't displayed :-(

 

really could do with help getting it back on port 80

[Rowlett 9]

ok luke thanks for the update :-)

[Luke 37251]

it is being bound differently, although in your case, it will be resolved when the current beta goes stable. all servers are currently being bound in a compatible way rather than an operating-system specific way. it was left in by mistake and there are no issues with it other than this.

 

having said that, it sounds as if you are currently relying on unsupported and undocumented behavior so no promises are made to it's future support. I may very well decide at some point that handling every operating system the same way is the best route to take. If that happens then what you're doing will just break again.

 

your url rewrite is the better approach if you want to avoid future disruption.