WAN IP address change

[Sherlock]

Hello,

My ISP has changed my WAN ip-address.
From that moment on Domoticz is not able to communicate with external systems.
For example, Domoticz raises errors while trying to connect to:
- Prowl (for IOS push notifications)
- SolarEdge (with api-key to retrieve solar panel data).
- Telegram (also for notifications from my camera).

Is there anybody who can give me a hint on what's going on here.

I am running Domoticz v4.10717 on a Raspi 3B

Regards Bauke

[Dave21w]

A WAN IP change should not affect any outgoing connections, I take it the rest of your internet connected items are still functioning correctly ?

[Sherlock]

Yes any outgoing connection (apart from Domoticz) is oke.
This defect occurred immediately after my ISP changed my WAN ip.
It puzzels me.
Kind regards Bauke

[Treve]

Should be Ziggo, I have the same problem.
three different Wan addresses in one day.
I’m on vacation now and not be able to reach my Domoticz.

[Fredom]

The same here.
Then I have Caiway.
No problem with the app at home, but from outside I can no longer log in to Domoticz.
Everything has always worked well and nothing has changed from my side. So this problem is with the provider

[Treve]

maybe to make it difficult for (Russian) hackers?

[Sherlock]

@Fredom and Treve,
My ISP is SKP (a local Pijnacker provider and originally based on Caiway).
I was using Domoticz v4.10717 on Jessie.
Although the issues immediately appeared after my WAN ip was changed by SKP, they told me SKP could not help me because they are not familiar with Domoticz and I was the only one having problems.
So I decided to get a clean install and now I am running Buster with Domoticz 2022.1
No problems so far and everything is running fine.
Kind regards Bauke

[Fredom]

Hi Sherlock,

i also use debian buster with domoticz 2022.1
I've never had any problems and from one day to the next I couldn't log in remotely.
I then get an error in domoticz with a login ip address and if I enter that ip address in the app then I can log in. but that is not the ip address of my router and after a day it is the same problem again.