this post was submitted on 25 Nov 2023
2 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
 

Hi have a home lab setup with Nginx Proxy manager with few CNAMS setup which perfectly works fine.

But I have one issue as my company blocking all CNAME urls as it has wildcard ssl certs. It does allow to open Main URL but not any of the subdomain urls.

mainDomain.com works

sub.mainDomain.com is blocked

With the existing setup can I have additional URLS with port at the end to access the same subdomain backend urls something like mainDomain.com:1234 with the existing nginx proxy manager setup.

sub.mainDomain.com ==> backendIP:1234 ------Blocked

mainDomain.com:1234 ==> backendIP:1234 -----if this can be done with the existing NgnixProxyMamanager?

top 2 comments
sorted by: hot top controversial new old
[โ€“] [email protected] 1 points 10 months ago

Please elaborate, you are not telling the full story

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

NPM can also do URL proxying: you can reach sub.maindomain.com at maindomain.com/whatever/. Edit the proxy host definition for the main domain and look in the "custom locations" tab.

Alternatively, if you can control your browser's settings, you can try using DNS over HTTPS which can let you bypass your company's DNS. Try using https://dns.quad9.net/dns-query for example as the DNS over HTTPS address (or whatever your browser can offer).