port conflict

[James.W@AST]

the default port of this package is the same as boxee, therefore, you will not be able to see it if you have boxee installed...

[JohnnyFive]

Thanks James,

Have fixed the issue, and changed the port to 8080. As far as I could find no pkg's did use this port yet.

[ddaniel51]

Thanks James,

Have fixed the issue, and changed the port to 8080. As far as I could find no pkg's did use this port yet.

Look here: http://www.speedguide.net/port.php?port=8080

[JohnnyFive]

euh, malware is not the same as a pkg running on the asustore

[ddaniel51]

euh, malware is not the same as a pkg running on the asustore

If you bothered to look there were a few linux apps, port fowards, http, and proxy uses on the page also.

[JohnnyFive]

i did bother to look. And the page is mainly focussed on malware.

Just got feedback the tomcat package is also using port 8080, so i'm now a bit at a loss. Which port to take? anybody has any suggestions on an easy port that is not taken yet?

[James.W@AST]

How about 8088?

[JohnnyFive]

fine by me, will change it again. Please reserve this port somewhere to prevent future issues

[clinton.hall]

Would it be possible to start a sticky thread where all devs/apkg-maintainers can coordinate which ports to use for packages with web servers?

I should have my new Asustor very soon and can't wait to play

I intend to get an NZBGet apkg up soon. That will likely use the default 6789 port, but I haven't had a chance to see what other posts are in use.

[James.W@AST]

That's a great idea, however, since we can't edit the same post, therefore, I guess I will have to figure out a better way so that we can all edit the same document.

do you have any suggestion?