If i use custom https port, any update will reset /etc/apache2/sites-available/vitalpbx.conf back to 443.
I can guess that if I am using some custom apache configuration, it will be also lost, at every update.
If you set up the custom port via the Web Interface, then the port won’t get overwritten on each update!
I already did it. I can reproduce the behaviour any time.
Maybe there is any solution for it?