To register the Charging Manager on the cloud server, the cloud service must be activated in the Charging Manager configuration. The Charging Manager then establishes a TLS-encrypted connection to the cloud server at cloud.cfos-emobility.de. The "Cloud server", "Cloud ID" and "System password" input fields must remain empty. These are only required when operating your own cloud server.
If the cFos Cloud Server is used, the Cloud ID is also displayed in this section, which then corresponds to the serial number of the system. This is required to access your own system via the cloud server.
The Charging Manager must be connected to the cloud server as described above. Now use your browser to access the cloud server at https://cloud.cfos-emobility.de:4443. On the Cloud Server login page, enter the serial number of your system under "Cloud ID".
If you want to access the system as an admin, tick the corresponding box and enter the system's admin password under "Cloud user ID". The admin password must not be empty.
If you want to access the system as a user, at least one user must be set up there. Enter the user ID under "Cloud user ID". The "Connect as 'admin'" checkbox remains empty in this case. The admin password on the system must not be empty here either! Otherwise the login will fail for security reasons, even if the user ID is valid.
If you access your system via the cloud server, the additional menu item "Cloud Login" appears in the menu bar. This takes you back to the Cloud Server login screen.
Please note! The operator of the cloud server can view all transmitted data and potentially has access to your system / wallbox.
You can also operate your own cloud server with the Charging Manager. To do this, call up the charging_manager programme as follows:charging_manager run <port> -cloud_server
The <port> parameter represents the port number on which the cloud server should accept connections. By default, only TLS-encrypted HTTPS connections are accepted. If the programme is called with the optional parameter -allow_http, unencrypted HTTP connections are also accepted on the same port.
Furthermore, the parameter loglevel <1..4> can be used to set the initial log level in the corresponding levels Feler, Warnings, Information, Data.
The cloud server is configured and managed via the /ui/en/cloud-admin.htm page, e.g.https://localhost:<port>/ui/en/cloud-admin.htm
The admin password is that of the Charging Manager.
To register a new system on the Cloud Server, assign a Cloud ID and a Cloud password under "Cloud Server Admin Functions" and click on "Add new system".
You also enter the assigned cloud ID and password as well as the address of your cloud server in the configuration of your system in the "Cloud service" area. The input field for the cloud ID appears as soon as you enter a server other than the cFos server.
You should now be able to access your system via your cloud server as described in the previous section.
By default, the cloud server uses a self-signed certificate to establish encrypted connections. Although this says nothing about the level of encryption, such connections are usually labelled as insecure by browsers. However, you can also use your own certificates signed by a certification authority (CA) with the cloud server. To do this, the cloud server must first be started as described above.
Assuming that the cloud server is listening on port 4443, a new certificate can be imported by calling the cloud server again with the following parameters:charging_manager cloud_cert https://localhost:4443 /path/to/cert.pem /path/to/private_key.pem
Under Linux, the cloud server can run without root rights, but the certificate can be read and imported with root rights by prefixing the above command with "sudo".
We use cookies. Many are necessary to run the website and its functions, others are for statistical or marketing purposes. By choosing "Accept essential cookies only" we will respect your privacy and not set cookies that are not necessary for the operation of the site.