@GregorTacTac If you use containers you can map something like 8080 on the host to 80 in the container. Generally it's recommended to have a reverse proxy listening on 80 and 443 with all your individual applications on localhost only high ports.
this post was submitted on 28 May 2024
8 points (83.3% liked)
Self Hosted - Self-hosting your services.
11419 readers
1 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 3 years ago
MODERATORS
Bitwarden has its own script to manage the containers. It’s not your typical self hosted app docker installation. What OP is looking for is easily accessible in their FAQ section of the documentation.
Q: How do I use custom server ports?
A: To use custom ports, instead of 80 and 443, edit the http_port= and https_port= values in ./bwdata/config.yml and run ./bitwarden.sh rebuild to rebuild your server assets.
Check that the custom port values have been proliferated to ./bwdata/env/global.override.env.
I'd like to have the applications running at the same time. This can't be done with just 2 ports, can it?
It can be done if you implement a reverse proxy in front of the services.
80 and 443 are the standard ports for webpages (http and https respectively). Lot of selfhosted software with web-based frontends will therefore try to use them.
You can change the ports for the bitwarden container to whatever you like, but the "proper" way to set up multiple services with web-based interfaces like this, is to use a reverse proxy to make them all accessible via these two standard ports. (Caddy is popular for this)
You can then access them using their respective subdomains or subpaths.
You'll want to use a reverse proxy with separate domains/subdomains for each service.
This doesn't show how to change those ports.
Does it not prompt during the installation wizard? That's what the documentation implies.
Nope, it doesn't,
I used to host bitwarden before switching to vaultwarden. Bitwarden’s documentation is pretty good and your question is easily found here:
https://bitwarden.com/help/hosting-faqs/#q-how-do-i-use-custom-server-ports
Q: How do I use custom server ports?
A: To use custom ports, instead of 80 and 443, edit the http_port= and https_port= values in ./bwdata/config.yml and run ./bitwarden.sh rebuild to rebuild your server assets.
Check that the custom port values have been proliferated to ./bwdata/env/global.override.env.
I'm planning on using Vaultwarden as well. Does this work for Vaultwarden?
With vaultwarden it's very easy, just change the port map in the docker compose file on the host side. No idea how to do it with the official server stack.
Unfortunately, I’m not familiar with installing Bitwarden so I can only offer general advice.
Port conflicts happen at runtime, not when software is installed. In general, you should be able to install as much software as you’d like that all relies on port 443 but only run one at a time.
If you’re seeing port conflicts when installing Bitwarden, then I suspect that something is starting the app after the install is done. If this is right, then maybe you can disable the automatic start. Or maybe you can ignore the error at install time, then configure the app, then start it.