Hello Harald, On 3/18/19 8:20 AM, Harald Dunkel wrote: > Monitorix providing its own web service is surely a major > improvement, but using port 8080/tcp per default has a high > chance to introduce a conflict with other tools, esp. on > test systems run by unprivileged users. Port 8080/tcp is > the first port they use.
I do agree with you, 8080/tcp is a commonly used port. It would avoid potential conflict for monitorix to choose another port to listen to. > I would highly recommend to choose another default port > for monitorix' web service, e.g. 8888/tcp. Of course this > might conflict, too, but port 8080 is in *very* wide use. However, I'm not convinced that changing the default would be an improvement. The built-in http server has been around for a while now (6 years) and nowdays, people installing new instances of monitorix expect the webui to show up on :8080. I'm worried that if the default had to change, users would be thrown off by it. And I think that, in most cases, defaults should reflect what the majority of users expect. In case of monitorix: # apt install monitorix Open a browser to http://localhost:8080/ Moreover, should the port be already taken, it stays very easy to change it in monitorix's configuration file. Given that, I'm not in favor of changing monitorix default listening port. Best regards, -- Baptiste BEAUPLAT - lyknode
signature.asc
Description: OpenPGP digital signature
