this post was submitted on 11 Nov 2023
3 points (100.0% liked)

Self-Hosted Main

502 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
3
Question about NPM: Why does choosing "https" not work for https? (alien.top)
submitted 10 months ago by MalcolmY@alien.top to c/main@selfhosted.forum
2 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] AnonymusChief@alien.top 1 points 10 months ago

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?