Host Administration¶
Host Administration is the control panel for application-wide infrastructure and operational settings in Emakin. All agent nodes in the same farm share this configuration.
Use this area when you need to manage:
- applications and domains
- application identity, shared URLs, and defaults
- database and repository connections
- authentication, platform, messaging, and security services
- background processing, domains, libraries, data stores, and licenses
Host Administration also supports environment-variable placeholders for selected sensitive settings such as connection strings, passwords, client secrets, certificate values, and timestamp-service credentials.
Access and Safety¶
The host administration panel is available through port 7180.
Warning: Port
7180should only be reachable from secured networks. It should not be exposed publicly.
Typical access flow:
- Open
https://<application-address>:7180orhttps://localhost:7180. - Enter the host administration password on the landing page.
- Expand the relevant application row, then use the top-level and nested tabs to reach the setting you need.
The documented default password is verysecret. After login, it should be changed from the top navigation.
To manage host administration access settings, review the relevant appsettings.json configuration under the agent configuration directory.
First-Time Setup Notes¶
When Emakin starts for the first time, it creates:
- a default application named
localhost - a default domain named
default - a default domain admin user:
[email protected]/admin
The application name can be changed from Host Administration. The documented domain name cannot be changed from the panel and would require manual database intervention if it must change.
Configuration Map¶
The host configuration uses the following tab hierarchy. The page links point to the detailed reference for each functional area.
| Top-level tab | Nested areas | Documentation |
|---|---|---|
| Application | Application Identity; Service Addresses; Defaults and Limits | Application |
| Database Settings | System Connections; Repositories | Database Settings |
| Authentication | Integrated Services; Login Services | Integrated Services, Login Services |
| Platform Services | AI Providers; Storage and Calendar; Editors and Search | Platform Services |
| Security | Sessions; Policies; File Protection; Advanced Protection | Security |
| Messaging and Automation | E-Mail; SMS Services; Activity Callbacks | E-Mail Services, SMS Services, Activity Callbacks |
| Operations | Maintenance; Workers; Domains; Libraries; Data Stores | Workers, Domains, Libraries, Data Stores |
| Licenses | Application and tenant entitlements | Licenses |
The Save command persists host configuration changes. Test external connections before relying on them in production, and use the Refresh command in the Domains area after an availability or level change.