github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-16 08:33:59 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

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

New Issue
Closed
opened 2025-11-07 08:31:23 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-07 08:31:23 -06:00
Owner
Copy Link

Originally created by @georgedorn on GitHub (Apr 23, 2018).

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.

Originally created by @georgedorn on GitHub (Apr 23, 2018). 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.
GiteaMirror commented 2025-11-07 08:31:24 -06:00
Author
Owner
Copy Link

@georgedorn commented on GitHub (Apr 23, 2018):

just realized this is mobile, not docker

@georgedorn commented on GitHub (Apr 23, 2018): just realized this is mobile, not docker
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#216
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?