acme-companion
vaultwarden
Our great sponsors
acme-companion | vaultwarden | |
---|---|---|
32 | 489 | |
7,250 | 32,770 | |
0.7% | - | |
7.6 | 8.9 | |
25 days ago | 4 days ago | |
Shell | Rust | |
MIT License | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
acme-companion
-
Wireguard (docker-compose) has stopped being able to connect to the internet.
My hunch is that because I decided to include the acme-companion image in this nginx setup, that maybe it has something to do with the SSL certs? The only other thing I could think of is that I had to combine the networks in order for nginx-proxy and Sonarr both to be able to see my transmission instance via:
-
Add https to docker app
Probably want acme with nginx https://github.com/nginx-proxy/acme-companion
-
Beginner questions about deploying node.js app on Beanstalk
setting up letsencrypt with nginx-proxy and acme-companion
-
Further investigating 403 – access forbidden by rule
I'm experiencing a weird situation, and am not sure how to go about finding a solution. I am running the nginx-proxy container (https://github.com/nginx-proxy/nginx-proxy) together with the acme-companion container (https://github.com/nginx-proxy/acme-companion) to provide https connections to all my different applications under different subdomains on the same host (currently, for testing purposes: only two other nginx containers with a plain html page).
-
What is the correct way to have my webapp in one container and the webserver in another?
We use the nginx-proxy docker image with its acme-companion to have an auto configuring SSL reverse proxy, so it's really easy to deploy images (we do it based on a merge PR into protected release branches).
-
adding an SSL cert to a docker container
Use a reverse proxy to handle TLS/SSL encryption. I find nginx-proxy with companion easy to use, just follow steps 1, 2, 3.
-
502 Bad Gateway: Nginx Reverse Proxy + Docker + Let's Encrypt + Wordpress
Where I'm running into issues is with the two stacks I have deployed - one is a wordpress stack which uses the wordpress image along with a db image (going by the docs here), and the other is the nginx-proxy and acme-companion (going by the docs here).
-
dockerfile for httpd
Just use nginx-proxy and the LetsEncrypt companion as reverse proxy to handle TLS/SSL in front of your web server.
-
nginx-proxy-manager abandoned?
You can simply use this proxy container which automatically generates nginx config based on envs set in your containers. There is also a companion container which takes care of your certs. https://github.com/nginx-proxy/nginx-proxy https://github.com/nginx-proxy/acme-companion
-
Tools for automation and daily tasks
https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus
vaultwarden
-
Bitwarden
To people who want to self-host this, look at Vaultwarden which is a fully compatible alternate server with even more features:
https://github.com/dani-garcia/vaultwarden
Been running it for a year with 0 issues.
- Vaultwarden issue on sysnology
-
What program(s) do you use to remember passwords, including crypto?
For passwords and 2FA I use Bitwarden in combination with a self-hosted Vaultwarden service (for imcreased security and use of pro features for free).
- Comment gérez-vous vos mots de passe ?
-
List of your reverse proxied services
Vaultwarden as Password-Safe
-
Open Source: An Antidote to Closed Source Vulnerability
I have a lot of software that I host myself on my home server, partly to save money but also because I want to control my own data. For example, I host VaultWarden which is the open source server for BitWarden. This gives me all the premium features for free with the added bonus of keeping my passwords out of the cloud.
- Vaultwarden 1.30.0 released with passkey support
- Vaultwarden: Unofficial Bitwarden Compatible Server
-
Bitwarden: Free, open-source password manager
Self hosting is incredibly easy with vaultwarden (https://github.com/dani-garcia/vaultwarden)
-
Your privacy is optional
I have now switched to using the BitWarden app with the self-hosted VaultWarden server. I have set it up, so my passwords are only accessible when connected to my home network either physically or with a VPN (I am using tailscale for this).
What are some alternatives?
docker-compose-letsencrypt-nginx-proxy-companion - Automated docker nginx proxy integrated with letsencrypt. [Moved to: https://github.com/evertramos/nginx-proxy-automation]
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
Passbolt - Passbolt Community Edition (CE) API. The JSON API for the open source password manager for teams!
Docker Compose - Define and run multi-container applications with Docker
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
keepassxc - KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
docker-letsencrypt-nginx-proxy-companion - LetsEncrypt companion container for nginx-proxy [Moved to: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion]
authelia - The Single Sign-On Multi-Factor portal for web apps
nginx-proxy-automation - Automated docker nginx proxy integrated with letsencrypt.
Nextcloud - ☁️ Nextcloud server, a safe home for all your data