We will release a new Theia version that will use IPv6 ranges to give a different IPv6 to each of it's embedded partitions. Until now all subpartitions had the same IPv6 as Theia.
This is useful to cleanly avoid IPv6 conflicts between embedded instances in Theia, or between an embeddded instance and Theia itself. Until now we've had to carefully use different ports to avoid conflicts.
This upgrade will therefore change the IPv6s of the embedded partitions in your Theia. This can cause problems with your instances.
Note that the IPv4s will remain the same. There can still be IPv4 conflicts. Introducing IPV4 ranges may happen someday but is not yet planned.
If this is a problem for you, disable the automatic processing of partitions on your Theia: put parameter "Automatically Run Software/Instance" ("autorun") to "stopped". The partitions will still receive a new IP, but the old IP will still remain available for your Theia and as long as you don't reprocess your instances, they won't use the new one. Doing this can only be a short-term stopgap to buy time until a moment when you are ready to fix any issues caused by the changing IPv6s. You are highly encouraged to reprocess your instances and let the IPs change as soon as possible. Note that manually processing your instances by running "slapos node instance" in a Theia terminal will also result in the IPv6s changing.