【隨記】‎ > ‎

Unifi 8080 埠被佔用

張貼者:2013年11月24日 下午11:37成平板   [ 已更新 2013年12月7日 下午5:16 ]

  • UniFi - What is the system.properties file?
by Ubiquiti Employee UBNT-David 4 weeks ago - edited Tuesday (575 Views)

Answer


The file system.properties sits under <unifi_base>/data and is used to define system-wide parameters for the UniFi Controller, such as ports. When editing the document, make changes to the below portion of the file. Lines preceded with a hash-tag exist as comments and are non-operational.  After changing this file, UniFi controller needs to be restarted in order to take these effective.

To change default ports for controller and UAPs (see linked article for detailed explaination). Otherwise, the default ports are listed below:

  • unifi.shutdown.port=8081   # for management purpose
  • unifi.http.port=8080           # device inform
  • unifi.https.port=8443         # controller UI / API
  • portal.http.port=8880        # portal redirect port for HTTP
  • portal.https.port=8843      # portal redirect port for HTTPs
  • unifi.db.port=27117          # local-bound port for DB server


If a controller machine has multiple IP interfaces, then below configuration can manually set the exact IP interface that adopted APs should communicate to the controller.

  • system_ip=a.b.c.d           # the IP devices should be talking to for inform


Below are advanced database configurations that we do not expect most users will ever need to touch. We also do not perform tests on these configurations, they are enabled for the convenience of database experts. One possible usage scenario is where few people run their controllers on a NAS, which has a smaller footprint than a normal server, hence need to reduce the required resources.

  • unifi.db.nojournal=false    # disable mongodb journaling
  • unifi.db.extraargs            # extra mongod args


The configuration below is used to faciliate controller installation. Again, most users will never need to set this. When the is_default is set to true, the controller will start with factory default configuration. For normal, everyday users, an uninstallation and then fresh re-installation is recommended over this.

  • is_default=false

 

(v3.1.7+) The configuration below is used to fix an earlier bug where, in earlier v3 versions, the controller allows you to delete the super admin account (the one created during installation) and this super admin cannot be restored back. We later fix this issue (super admin cannot be deleted any more). However, some might have accidently already done this hence we created below config to allow promoting of a super admin. We expect most users will never need to set this.

  • super_admin.name=account_id_to_be_promoted




::