this post was submitted on 30 Nov 2023
0 points (50.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
[email protected]
0
Reverse Proxy: One vHost with locations for different docker apps (alien.top)
submitted 9 months ago by [email protected] to c/[email protected]
2 comments fedilink hide all child comments
 

My idea was to create one vHost myserver.local and have custom locations pointing to different docker apps:

myserver.local directly points to the NPM admin GUI on port 81.

myserver.local/portainer should point to portainer:8000

I tried it with NPM but it doesn't seem work: I get to the admin GUI but only get a 404 for /portainer... Googling the issue I mostly read about using sub domains instead of locations, but at the moment I am limited to one DNS entry for my home server.

Any suggestions?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 9 months ago (1 children)

Subdomains are better because some applications don't like to be in a custom path and might not work.

A single DNS entry (like *.local.example.com) should be enough to use anything in the subdomain instead of creating one entry for each application. (portainer.local.example.com, pihole.local.example.com, etc).

If your provider doesn't support that, can't you use Cloudflare? It's free.

[โ€“] [email protected] 1 points 9 months ago

I could be mistaken, but I believe Cloudflare doesn't allow second-level subdomains on their free plan