Introduction
Via the custo DynDNS service it is possible to make RDT transfer in custo diagnostic 5.x without a fixed external IP address.
The authentication is based on the custo cloud server login (kybe login).
Configuration
Start
If nothing is set up yet, the "dynamic URL and SSL" appears as follows:
(1) Indications appear, that nothing has been configured
(2) The dynDNS configuration cannot be done, everything is locked.
cloud server
As a custo med sales partner please go the retailer web page of the custo cloud server:
Please go to http://kybe.customed.de/CustoCentral/retailer/, log in with your sales partner account and create a customer account (if the customer does not yet have any). Then wait some minutes until the user credential information is distributed among the different cloud servers.
Then open a either the Internet Explorer or the MS Edge browser on the server where the custo diagnostic server is installed and open the following web pages:
https://kybe.customed.de/CustoCentral/ (Error 404 will appear, but's ok)
and
In case any of the SSL certificates on those web pages should be considered as untrusted please get the untrusted one stored in the computer certificate store.
Then go to the services.mmc and restart the Appache Tomcat server.
Open the Service Center again and go to the Cloud Server section. Enter the customer's Kybe user credentials and test the login data:
To be able to proceed you should get a message about successful logon. The save the configuration with the save button.
Now it is time to open up the firewalls (the internet firewall or router, the Windows Firewall and the virus scanner) for the external communication.
An example how to open an inbound port from the internet to the router Fritz Box can be found here:
https://avm.de/service/fritzbox/fritzbox-7590/wissensdatenbank/publication/show/893_Statische-Portfreigaben-einrichten/ (section 3 to allow access to the Fritz Box itself is not relevant). The port which needs to be forwarded from the internet to the custo diagnostics server is the SSL port, which per default is TCP port 8443. However the installation may use also 18443 or 28443.
To test the connection from outside you can try to open the connection in a browser like this: https://<your-external-ip>:<configured-port>/diag
If the "WebViewer-coming-soon picture is coming up the external connection will be run.
Then go back to the Service Center to the Dynamic URL and SSL section:
After the cloud server access is set up, this will also appear in the status window
System physician
At least the name and email address must be entered for the system physician, as the certificate is then created for him. If the doctor is correctly configured, this appears in the status window
If all configurations are successful, the DynDNS configuration is activated and the settings can be made.
DynDNS Configuration
By default the DynDNS configuration URL is set to https://null:8080. There is no need to change that URL. This will be done automatically if you click on "Setup DynURL and certificate".
The configuration works automatically and is done by click on Setup DynURL and certificate. Creating the certificate takes a few minutes.
If everything worked, the DynDNS name appears in the field DynUrl (1) and the period of validity of the certificate at DynURL Status (2)
Functions
ping test
Attempts to ping the server that is set up under DynUrl. This is useful to check if e.g. the router (FritzBox) is configured correctly and the port is forwarded correctly. Port mapping from 8443 for SSL external to 8443 internal.
Get secured CustoCfg.ini
Saves the CustoCfg.ini with the new URL to the disk so that it can be used for future purposes.