Certbot renewal script should use the configured ports, not 443/80.

[georgedorn]

After installing with certbot enabled, certbot always uses 443 when checking whether the cert needs renewing, even if bitwarden has been configured to run on a different port.

During bitwarden.sh install, certbot runs before the port is asked for, so it's necessary to shut down anything else running on that port during initial installation. After, every startup also runs certbot to check whether renewal is needed, and that fails as well.

A workaround for the startup problem is to edit bwdata/scripts/run.sh by hand to change the port, but bitwarden.sh update clobbers edits to that file.

[georgedorn]

just realized this is mobile, not docker