Hi,
Did not get your point!
I have the same problem, the public IP is changing every 24 hours. Does you post points to two scripts which change the org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS to a new IP? How do I execute these scripts?
Maybe silly questions, but I can’t figure it out, sorry.
To not depend on jitsi.net or another third-party, I suppose a STUN server must be implemented somewhere.
Maybe Jitsi client could make this information job (new feature)?
Sorry for my ignorance about stun/turn services:
Is stun/turn server useful at same Jitsi server? (without being on another Internet place)
How cant it be enabled & started on a default Debian setup?
Some tcp/udp port to be forwarded?
Just a side note, in addition to the stun config - if you still want to have the local and public IPs, in most cloud platforms there is a way to discover the VM’s details, including private and public addresses.
For example in AWS a simple call to http://169.254.169.254/latest/meta-data/public-ipv4 gives you the public IP and to http://169.254.169.254/latest/meta-data/local-ipv4 gives you the private one.
With some automation scripts you can pre-populate the configs, with cron you can keep them updated in case IPs change.