Settings/Services/Control
Jump to navigation
Jump to search
|
 Settings |
Services |
Control
|
Web server
Allow remote control via HTTP
| Settings level: | Standard |
| Description: | Enable to allow remote users to control this application through the built-in web server. |
| See also: | Webserver |
Port
| Settings level: | Standard |
| Description: | Defines the port by which the webserver will be reached. If changing the port ensure you do not conflict with standardized ports such as "21" for FTP or "22" for ssh. |
| See also: | List of TCP and UDP port numbers |
Require authentication
| Settings level: | Standard |
| Description: | Choose whether requests to the web server require a username and password. |
Username
| Settings level: | Standard |
| Description: | Defines the username which needs to be used to access the webserver. |
Password
| Settings level: | Standard |
| Description: | Defines the username which needs to be used to access the webserver. |
Web interface
| Settings level: | Standard |
| Description: | Select a web interface. The default is the Chorus2 web interface. |
| See also: | Web interface |
Application control
Allow remote control from applications on this system
| Settings level: | Standard |
| Description: | Allows programs on this device to control this application via the JSON-RPC over WebSocket, JSON-RPC over TCP or EventServer protocol, without authentication. |
| See also: | JSON-RPC_API |
Allow remote control from applications on other systems
| Settings level: | Standard |
| Description: | Allows programs on the network to control this application via the JSON-RPC over WebSocket, JSON-RPC over TCP or EventServer protocol, without authentication. It allows anyone with access to the network to completely control this application and, therefore, this device. Never expose these interfaces to the internet. |
| See also: | JSON-RPC_API |
| See also: | Event Server |
References
| Return to top |
|---|