TOPIC: SCADA on the IPhone

Dear Mr. Tran,
Thank you for reaching out and providing detailed information about the installation issue. We understand the problem you're experiencing with the "Configuring gdm3" prompt during the TeslaCloud Standalone Server installation. This is a known behavior when installing packages in a non-interactive environment (such as cloud servers accessed via SSH). The gdm3 package (GNOME Display Manager) is being pulled in as a dependency and attempts to show an interactive configuration dialog. However, in headless cloud environments without a graphical console, keyboard input to these dialogs may not work as expected. In the next version of script we'll fix it (we need to test).
Now, please follow these steps to complete the installation:
Option 1. Quick Fix.
Run the installation with environment variables that suppress interactive prompts:
# Set non-interactive mode
export DEBIAN_FRONTEND=noninteractive
# Pre-configure debconf to auto-select defaults
echo "debconf debconf/frontend select Noninteractive" | sudo debconf-set-selections
# Re-run the installation
curl -fsSL teslascada.com/Downloads/install.sh | sudo bash
Option 2: If You're Currently Stuck on the gdm3 Screen
If the installer is currently frozen on the "Configuring gdm3" dialog:
1. Try pressing Tab to navigate between options, then Enter to select gdm3 or lightdm
2. If that doesn't work, press Ctrl+C to cancel the current installation
3. Then apply the commands from Option 1 above to restart with non-interactive mode

Best regards,
Ruslan

Ruslan:
I was able to install the Tesla Cloud Standalone but I can not connect to it using the Chrome browser.
I have the error response "157.245.225.133 refused to connect". The cloud server is online.
I did disable the firewall and antivirus on my computer.

When I use the RealVNC to connect to the server, It is connected and I can see the gnome GUI as normal.
Is there conflict between the TeslaSCADA web server and Gnome Server?
What CLI command should I use to check the running status of the TeslaSCADA service?

Best Regards,
Robert Tran

When I use the command: "sudo systemctl status servercloud"
This is status:

root@Acme-Scada:~# sudo systemctl status servercloud
● servercloud.service - TeslaCloud
Loaded: loaded (/etc/systemd/system/servercloud.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2026-04-26 12:42:43 UTC; 6min ago
Main PID: 1183 (java)
Tasks: 33 (limit: 4638)
Memory: 150.4M
CPU: 4.657s
CGroup: /system.slice/servercloud.service
└─1183 /usr/bin/java -Djava.util.prefs.userRoot=/opt/servercloud/.java_prefs -jar servercloud.jar

Apr 26 12:42:47 Acme-Scada java[1183]: 2026-04-26 12:42:47 INFO BaseServer2:29 - OpenSsl=false
Apr 26 12:42:47 Acme-Scada java[1183]: 2026-04-26 12:42:47 INFO MQTTWSBrokerServer:62 - MQTTWSBrokerServer listen on port: 1884
Apr 26 12:42:47 Acme-Scada java[1183]: 2026-04-26 12:42:47 INFO AliceHTTPSocketServer:52 - AliceHTTPSocketServer listen :8070
Apr 26 12:42:47 Acme-Scada java[1183]: 2026-04-26 12:42:47 INFO HTTPSocketServer:52 - HTTPSocketServer listen :8090
Apr 26 12:43:45 Acme-Scada java[1183]: 2026-04-26 12:43:45 INFO Holder:101 - NO SESSIONS
Apr 26 12:44:45 Acme-Scada java[1183]: 2026-04-26 12:44:45 INFO Holder:101 - NO SESSIONS
Apr 26 12:45:45 Acme-Scada java[1183]: 2026-04-26 12:45:45 INFO Holder:101 - NO SESSIONS
Apr 26 12:46:45 Acme-Scada java[1183]: 2026-04-26 12:46:45 INFO Holder:101 - NO SESSIONS
Apr 26 12:47:45 Acme-Scada java[1183]: 2026-04-26 12:47:45 INFO Holder:101 - NO SESSIONS
Apr 26 12:48:45 Acme-Scada java[1183]: 2026-04-26 12:48:45 INFO Holder:101 - NO SESSIONS
root@Acme-Scada:~#

More information When I use the command: "sudo systemctl status servercloud"

servercloud.service - TeslaCloud
Loaded: loaded (/etc/systemd/system/servercloud.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2026-04-26 14:06:22 UTC; 1min 22s ago
Main PID: 1214 (java)
Tasks: 33 (limit: 4638)
Memory: 148.6M
CPU: 3.632s
CGroup: /system.slice/servercloud.service
└─1214 /usr/bin/java -Djava.util.prefs.userRoot=/opt/servercloud/.java_prefs -jar servercloud.jar

Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO BaseServer2:29 - OpenSsl=false
Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO TCPSocketServer:44 - TCPSocketServer listen on tcp://10.120.0.3:7000
Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO WebSocketServer:36 - WebSocketServer listen on ws://10.120.0.3:7001
Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO TCPSocketServer:26 - TCPSparkplugSocketServer listen on tcp://10.120>
Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO BaseServer2:29 - OpenSsl=false
Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO MQTTBrokerServer:47 - MQTTBrokerServer listen :8883
Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO MQTTWSBrokerServer:62 - MQTTWSBrokerServer listen on port: 1884
Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO HTTPSocketServer:52 - HTTPSocketServer listen :8090
Apr 26 14:06:24 Acme-Scada java[1214]: 2026-04-26 14:06:24 INFO AliceHTTPSocketServer:52 - AliceHTTPSocketServer listen :8070
Apr 26 14:07:23 Acme-Scada java[1214]: 2026-04-26 14:07:23 INFO Holder:101 - NO SESSIONS

Ruslan:

Problem solved. Using HTTP Instead of HTTPS allow me to connect to the cloud server.
I will explore the Teslacloud now.

Thank you
Best Regards,
Robert Tran

Dear Ruslan:
I install both TeslaCloud Standalone Server and TeslaSCADA2 Runtime in one Ubuntu Clould Server. When I configure the TeslaSCADA runtime to send tags to the TeslaCloud Standalone Server, the tags do not appear at the standalone cloud server at all.
But when I configure the TeslaSCADA runtime to send tags to the cloud.teslascada.com, I did see the tags on the cloud.teslascada.com.

Is there possiblility that my Ubuntu Cloud Server blocks the communication from the runtime to the standalone server? They are both on the some computer.
Do I miss any configuration on the server that cause the problem?

Best Regards,
Robert Tran