Server and application credentials
Applications are installed on the Marketplace tab in the client area. The same tab contains the Application Credentials block that displays the credentials of the installed application. An installation creates two independent sets of credentials: the application credentials and the VPS credentials.
By default the application uses a self-signed SSL certificate. When you first open the Admin URL, the browser may show an untrusted connection warning. This is expected behavior: the connection is encrypted, but the certificate is not confirmed by a certificate authority. To use a trusted certificate, connect your own domain as described in the "Connecting a custom domain and SSL" document.
Application credentials
The Application Credentials block contains the following fields.
- Current Stack – the installed application and operating system. After a reinstallation, the field shows the currently installed application.
- Admin URL – the address of the application web interface.
- Admin Login and Admin Password – the administrator login and password of the application, displayed for applications with automatically created credentials.
The contents of the block depend on the application type. There are three scenarios.
Scenario 1. The credentials are created automatically (for example, Zabbix Server). The login and password are generated during the installation and displayed in the Admin Login and Admin Password fields. The same data is stored on the server in /root/credentials.txt together with the current application URL.
Example of the file contents:
Zabbix URL: https://xx.xx.xx.xx (self-signed cert) Zabbix login: Admin Zabbix password: **************** Custom domain + free SSL: run 'setup-ssl' on the server
Scenario 2. The initial setup is completed by the client (for example, Dokploy). The Admin Login and Admin Password fields are not displayed: instead, the panel shows a note with the next steps. Open the address from the Admin URL field and create the first administrator account in the application web interface. You set the login and password yourself when creating the account and use them to sign in afterwards. The /root/credentials.txt file is not created for such applications.
Warning: credentials created during the initial setup exist only in the application itself and are not displayed in the client area. Save them in a password manager of your choice right after creating the account.
Scenario 3. An application without a web interface (for example, Zabbix Proxy). No credentials are created, the Admin URL field shows N/A. The setup is performed on the server: the panel and the server login banner point to the setup wizard command, for Zabbix Proxy it is setup-proxy. The /root/credentials.txt file contains connection parameters without passwords.
Example of the file contents:
Zabbix Proxy IP: xx.xx.xx.xx Proxy name: vpsXXXXX.introserv.cloud Zabbix Server: (not configured) Run 'setup-proxy' to connect to your Zabbix Server
In all scenarios, the current information about the way to access the application is provided in the Application Credentials block on the Marketplace tab.
VPS credentials
VPS credentials provide SSH access to the server under the root account. They are located in the client area on the Details page of the server: the IP address, login and password. This data is permanently available on the page and is not removed after an application is installed.
An installation from the Marketplace is performed with a full reinstallation of the operating system. Each installation or reinstallation of an application generates a new root password. The current value is displayed on the Details page after the page is refreshed. The application credentials are also created anew.
Warning: after a reinstallation, the SSH host key of the server changes. On the first connection, the SSH client displays a warning about the new key. This is standard behavior, confirm the new key to continue.
Changing the application login and password
For applications with automatically created credentials, the password is changed in the web interface using the standard tools of the application itself. For applications with the initial setup, the credentials are set by the client from the start and are known only to the client.
Warning: a manual password change is not reflected in the credentials.txt file or in the client area — they keep the credentials created during the installation. The support team will not be able to look up or restore the new password. Keep a record of the new credentials yourself, for example in a password manager of your choice.
After changing the password, log out of the application and log in again with the new credentials to verify that they are correct.
Changing the VPS login and password
The root account on the VPS remains unchanged. The root password is changed on the server with the command:
passwd
A password change on the server is not reflected in the client area: the Details page keeps the previous value. Record the new password yourself.
If necessary, the stored password can be removed from the panel using the Delete password icon next to the Password field on the Details page.
Connecting a custom domain and issuing an SSL certificate are described in a separate document.
