Domain change to control.logiccloud.io
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
The logiccloud platform is now served on control.logiccloud.io. The former name app-eu.logiccloud.io still works.
What you must do
Section titled “What you must do”Usually nothing. Both names point to the same server (IP address
91.99.82.104 when this page was checked). Your projects do not change, and
old portal and documentation links redirect to the new names.
Check your network only if one of these applies:
- Your firewall or proxy allows outbound traffic by name (FQDN allow-list).
- Your firewall allows outbound traffic by IP address.
- You use a separate MQTT broker host name in your own scripts.
Names and ports
Section titled “Names and ports”| Name | Use | Port |
|---|---|---|
control.logiccloud.io | Portal, API, WebSocket, device connection, edge download | 443 (HTTPS and WSS) |
control.logiccloud.io | logiccloud MQTT broker (TLS) | 1883 |
app-eu.logiccloud.io | Former name, same server and ports. The portal address redirects to control.logiccloud.io. | 443, 1883 |
auth.app-eu.logiccloud.io | Sign-in (Keycloak). Its name did not change. | 443 |
docs.control.logiccloud.io | This documentation. docs.app-eu.logiccloud.io redirects to it. | 443 |
FQDN allow-lists
Section titled “FQDN allow-lists”Add control.logiccloud.io to your allow-list. Keep app-eu.logiccloud.io
until all your devices and scripts use the new name. Keep
auth.app-eu.logiccloud.io: the sign-in service stays on this name and is
the Keycloak issuer host.
IP allow-lists
Section titled “IP allow-lists”Both names resolved to 91.99.82.104 when this page was checked. We do not
promise a fixed address. Prefer an FQDN rule where your firewall supports it.
MQTT broker
Section titled “MQTT broker”The logiccloud MQTT broker listens on port 1883 and uses TLS on this port. The
certificate is valid for both control.logiccloud.io and app-eu.logiccloud.io,
so a client that uses either name connects without a certificate error. The
portal shows control.logiccloud.io as the broker host. See
MQTT connection.
Devices behind a proxy
Section titled “Devices behind a proxy”If your devices use a corporate proxy, the proxy must allow the names in the table above. See Configuring an outbound proxy on the edge.