Closed Nightwalker83 closed 2 weeks ago
Hey there, sorry to hear you're running into this.
I'm a bit confused about what's going on. Can you give me more info?
Step 3 is just about making a TOKEN that you'll use to log into Vaultwarden later. It should be like this photo:
Thank you for helping me improve the project by reporting this issue. I hope I can help you whit this problem.
I mean the proxy manager setup sorry!
Hey there,
There's not enough information for me to help you yet. Can you provide some more details?
Are you using a valid domain?
Could you run the command docker compose logs -f
in the directory where your docker-compose.yaml
file is located and try the procedure again? After that, please paste the error that appears from the nginx-proxy-1
container here.
Well, it fails regardless of what I put for a domain such as vaultwarden.localhost or vaultwarden.ddns.net and when I check the logs they are empty.
I managed to get it to work by uploading certs created outside of letsencrypt.
Yes, since you're not using a valid domain/IP, the Certbot in Nginx Proxy Manager can't generate the certificate. I think that's the only way it would work. Glad to hear it worked out!
Hi,
During step 3 in the Lets encrypt setup for the ssl
https://github.com/Rapha-Borges/deploy-vaultwarden
The form an error "internal error" message when submitted.
The details of
Domain: Vaultwarden Scheme: http IP:172.18.0.3 (docker container)