Advanced Hosting Settings

[dubs 1]

Not sure if this is the correct place to report this, but just had a slightly frustrating issue (amplified by the fact initially I thought it related to the current "update" issue where it is showing an update is available that doesn't exist, but nevermind ).

 

I've been running the server running on a separate port, changing the "Local http port number" under Advanced, Hosting settings. All fine. Today i was flicking through the settings, decided to update the other ports to all be the same port:

 

Local http port number

Public http port number

Local https port number

Public https port number

 

In hindsight, this was a mistake, even in standard web applications http and https do not run on the same port. What followed was frustrating. Starting the service reported a success. Running a service emby-server status reported everything was fine. Only some further digging revealed the issue:

 

 - The PID changed every time I ran service emby-server status

 - Looking in /var/log/syslog showed:

Mar  8 22:09:05 emby kernel: [  999.749357] init: emby-server main process ended, respawning

Mar  8 22:09:05 emby /proc/self/fd/9: DEBUG: IFS=' #011#012'#012OPTIND='1'#012PATH='/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin'#012PPID='1'#012PS1='# '#012PS2='> '#012PS4='+ '#012PWD='/'#012TERM='linux'#012UPSTART_INSTANCE=''#012UPSTART_JOB='emby-server'

Mar  8 22:09:08 emby kernel: [ 1002.875188] init: emby-server main process ended, respawning

Mar  8 22:09:08 emby /proc/self/fd/9: DEBUG: IFS=' #011#012'#012OPTIND='1'#012PATH='/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin'#012PPID='1'#012PS1='# '#012PS2='> '#012PS4='+ '#012PWD='/'#012TERM='linux'#012UPSTART_INSTANCE=''#012UPSTART_JOB='emby-server'

 

Finally, on a whim I looked in /var/lib/emby-server and found the logs folder and saw it spewing "server-#######.txt" files and "unhandled_##############,txt" files. The unhandled ones contained:

 

InnerException: System.Net.HttpListenerException

Prefix already in use.

 

This pointing me to the issue. Now, the point of this post is 2 fold. 

 

1. The fix - Edit /var/lib/emby-server/config/system.xml so the PublicPort, PublicHttpPort, HttpServerPortNumber, HttpsPortNumber are all different. I expect some can be the same, but this was the quickest option I set HttpServerPortNumber to be the standard port all my media PCs and such use.

2. A request - Since clearly this is an easy way to break the server, could some additional checking be added to the page? Detect for  a conflict and report an error rather than save the changes.

 

Apologies for the rather long winded post, but I tend to ramble when trying to be detailed

 

dubs

 

[Luke 42077]

Hi, yes we should add some checks to prevent you from being able to do that. Thanks.