Login at Kodi Home

**N3MIS15** · 2011-06-20, 05:01

After having installed a fresh copy of xbmc I was unable to start http server due to sickbeard running on port 80. I had to shut down sickbeard, enable xbmc http server and change port, then restart sickbeard. I think it would be better if the port was changeable before starting the server.

isamu.dragon · 2011-06-20, 05:56

Settings\Network\Services

Allow Control Via HTTP

Change port.

Also I recommend that you change sickbeard.

My Personal Port Settings are:

Quote:XBMC
8080
Sickbeard
8081
CouchPotato
8082

remember when you connect to something that is running on a different port than 80
you need to add the port number to the ip address

Quote:http://192.168.1.101:8080

**N3MIS15** · 2011-06-20, 06:21

I know where the port settings are, the problem is they are greyed out until http server is enabled, you cannot change it until any other service using that port is stopped.

**ronie** · 2011-06-20, 12:47

are you using dharma?
nightly builds shouldn't have this issue, it was fixed 3 weeks ago:
https://github.com/xbmc/xbmc/commit/4fbc...9176c6a07c

isamu.dragon · 2011-06-20, 13:26

stop sickbeard (temporary), change the settings in XBMC, start sickbeard again.
don't really see any problem.

or if you like, change the port in sickbeard, and not change a thing in XBMC

darkscout · 2011-06-20, 17:10

isamu.dragon Wrote:stop sickbeard (temporary), change the settings in XBMC, start sickbeard again.
don't really see any problem.

or if you like, change the port in sickbeard, and not change a thing in XBMC

It's an extra step and confusing for people that may not be smart enough to realize what i going on. "Why the heck won't web services start".

It's also a Bug.

**N3MIS15** · (This post was last modified: 2011-06-21, 02:03 by N3MIS15.)

I was using pvr odk40 when I come across this (30th of may)

**Montellese** · 2011-06-21, 02:12

darkscout Wrote:It's an extra step and confusing for people that may not be smart enough to realize what i going on. "Why the heck won't web services start".

It's also a Bug.

IMO it's the job of the user to make sure that a TCP port is not used twice by different applications. So this is not a bug.

But I agree that users should be able to change the port before enabling the webserver because otherwise you are bound to stop the other application which already uses XBMCs default webserver port. But as ronie already mentioned this has been fixed/re-introduced on June 1st.