Question about NPM: Why does choosing "https" not work for https? reddit / selfhosted ---------------------------------------------------------------------- MalcolmY · 2023-11-11 03:15 In Nginx Proxy Manager (NPM) when you set up a proxy you have to choose "scheme", either http or https. If you choose "https" for an "https" link, it doesn't work! The website returns and error. Today I spent a very long time setting up Vaultwarden. Even though I don't plan to expose it to the public internet, I had to get an SSL certificate because the thing wouldn't register/login without it. I setup everything right, it didn't work until I changed that "scheme" option over from "https" to "http"? So, if I want to setup a proxy that has: SSL certificate, force SSL, and will be visited through "https://", why would it only work with that http option? ---------------------------------------------------------------------- thekrautboy · 2023-11-11 03:18 As the NPM documentation also explains, that option refers to what the target (the destination) is offering. So Vaultwarden itself does not offer HTTPS, it only offers HTTP. So you need to tell your NPM to use HTTP to connect to Vaultwarden. ---------------------------------------------------------------------- tech2but1 · 2023-11-11 15:45 > I had to get an SSL certificate because the thing wouldn't register/login without it. I setup everything right, it didn't work until I changed that "scheme" option over from "https" to "http"? If it didn't work then you didn't "setup everything right". If you can access Vaultwarden locally using https then something else is wrong with your setup, obviously. I can access services locally over http and https directly or via NPM so this isn't an NPM issue. ---------------------------------------------------------------------- emprahsFury · 2023-11-11 16:23 I'm pretty sure Vaultwarden itself will not work over http. ---------------------------------------------------------------------- emprahsFury · 2023-11-11 16:24 You're not really giving a lot to go off of. What were the nginx errors? What were the Vaultwarden errors? If I could read minds I would be a TV preacher with a gulfstream by now. ---------------------------------------------------------------------- ProbablePenguin · 2023-11-11 16:47 >when you set up a proxy you have to choose "scheme", either http or https This is for the backend connection from NPM to your service (Bitwarden), NOT for the frontend. Unless you've set up SSL in Bitwarden itself, you are going to be using http for the backend connection. ---------------------------------------------------------------------- MalcolmY · 2023-11-11 21:29 Sorry it was a 502 Bad Gateway. But when I change the scheme to HTTP it works just fine. ---------------------------------------------------------------------- MalcolmY · 2023-11-11 21:31 That's true, it will not work if you you don't visit https://vaultwarden In my post I was not referring to the URL, but to the NPM scheme HTTPS/HTTP option. I don't have a problem, I'm just asking why would the HTTPS option not work, but the HTTP does? Especially considering that Vaultwarden refuses to work on http:// it requires https:// ---------------------------------------------------------------------- MalcolmY · 2023-11-11 21:33 Thanks. But if I go directly to Vaultwarden http://192.168.1.1:port it demands https. So how can NPM connect through http while I can't? ---------------------------------------------------------------------- ProbablePenguin · 2023-11-11 23:32 When connecting through NPM you are using HTTPS as a client, bitwarden doesn't mind if the proxy backend is HTTP. ---------------------------------------------------------------------- AnonymusChief · 2023-11-16 03:15 Unfortunately, I currently do not have an NPM deployment. However, NPM has a section wheee you setup the DNS challenge. Can you confirm that is setup?