No remote access via mobile data after updating Jeedom to 4.5.3

Utilisation du core de Jeedom
1

Hello everyone,
I’m experiencing an issue with my Jeedom system after performing several updates and I’m hoping someone can help.

Recently, Jeedom prompted me to update the following components:

  • Jeedom core to version 4.5.3
  • Docker Management (docker2)
  • MQTT Manager (mqtt2)
  • Z-Wave JS (zwavejs)
    After completing all these updates, I noticed that I can no longer access Jeedom from my mobile phone when using mobile data (4G/5G). The connection only works when my phone is connected to the local WiFi network.

Before these updates, remote access via mobile data worked perfectly, so I suspect that one of the updates changed something related to network access, routing, or security settings.

I have been reading through the forum and trying to identify the cause, but so far I haven’t found a solution.
Has anyone experienced a similar issue or knows where I should look to fix this?

Thank you very much in advance.
Best regards.

PS: my local IP has changed, how can I reconfigure it? Could that be the cause?

Información Jeedom Atlas

Core : 4.5.3 (master)
DNS Jeedom Atlas : Sí

Plugin : Z-Wave JS
Versión : 2026-04-01 01:03:16 (stable)
Estado del demonio : Comenzó - (2026-04-23 18:50:04)
Santé 
🟢 Material : Atlas
🟢 Sistema actualizado : Bueno
🟢 Cron activo : Bueno
🟢 Escenario activo : Bueno
🟢 Iniciado : Bueno 2026-02-02 15:46:02
🟢 Fecha del sistema (última hora registrada) : Bueno 2026-04-25 10:37:44 (2026-04-25 09:49:01)
🟢 Derechos Sudo : Bueno
🟢 Versión Jeedom : 4.5.3
🟢 Versión SO : debian 11.8
🟢 Versión PHP : 7.4.33
🟢 Número de procesos de Apache : 12
🟢 Versión SO : Linux JeedomAtlas 5.15.93-rockchip64 #23.02.2 SMP PREEMPT Fri Feb 17 23:48:36 UTC 2023 aarch64 GNU/Linux  [11.8]
🟢 Versión Base de datos : 10.5.21-MariaDB-0+deb11u1
🟢 Espacio disco libre : 80 %
🟢 Conexión activa/máxima/permitida : 11/19/151
🟢 Tamaño de la base de datos : 29.9 MB
🟢 Espacio libre en disco tmp : 99 %
🟢 Memoria disponible : 76 % (Total 3864 Mo)
🟢 Memoria suficiente : 0 
🟢 Error de E / S : 0
🟢 Intercambio disponible : 100 % (Total 1932 Mo)
🟢 Intercambio : 100 %
🟢 Carga : 0.05 - 0.16 - 0.1
🟢 Configuración de la red interna : Bueno
🟢 Configuración de la red externa : Bueno
🟢 Nodo : v22.22.0 
🟢 Pitón : Python 2.7.18 
🟢 Pitón 3 : Python 3.9.2 
🟢 Persistencia de la caché : Bueno
🟢 Apache privado tmp : Bueno
2

you should rather post in the english community of the forum : https://community.jeedom.com/c/english-community/112

3

Hello,

The place of the post won’t change that much in this case, it’s anyway the same persons that could potentially answer :wink:

There is no possibility that the update of one of these could have broken external access.

To investigate further, you should describe how you usually access your jeedom (from mobile)
Dedicated mobil App or browser?
Ip or domain name?
Jeedom dns access or custom solution? Which one?
Some open port + routing?

The fact that your local ip change is certainly the reason.
And we cannot tell where you should configure it, the question is too vague…
probably somewhere in your router settings