Selfhosted

61361 readers

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

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Beginners Questions about Audiobookshelf, DNS and nginx (lemmy.dbzer0.com)

submitted 11 months ago by TheBlindPew@lemmy.dbzer0.com to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

Hey all, I'm relatively new to the selfhosting game the most I've done to date is own and maintain a plex server for the last few years, but that mainly handles all of the networking for me so I'd say it doesn't really count.

Recently, due in part to the ongoing controversy with audibles royalty and streaming model I've decided to try my hand at setting up an Audiobookshelf server of my own. For reference I'm running on a machine with Ubuntu 20.04. Ive managed to get Audiobookshelf and nginx running through docker and accessible via the localhost:port, but now I feel like I'm missing some key understandings.

I assume I need to have a domain name through a DNS service like cloudflare in order to make use of it, but I'm not sure what to do after that and the documentation that I have read doesn't outright answer my questions.

Once I have my DNS setup, how do I associate it with my server or point it through the nginx reverse proxy?

I know I'll have to setup a .conf file for nginx at some point and I found the example .conf in the audiobookshelf documentation, but I just feel like I'm missing the step between getting a domain name and establishing the reverse proxy.

Any help would be greatly appreciated, thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] communism@lemmy.ml 1 points 11 months ago (1 children)

You get a domain name, and use an A record to point it towards your server's public IP address.

You tell nginx to forward requests to a given domain. For instance, you could tell nginx to forward requests to foo.bar.com to 127.0.0.1:1337. To do this:

http {
    server {
        server_name foo.bar.com;
        listen 80;
        
        location / {
            proxy_pass http://127.0.0.1:1337$request_uri;
        }
    }
}

Note that this is a very basic setup that doesn't have HTTPS or anything. If you want an SSL certificate, look into Let's Encrypt and Certbot.

Also, the service you're hosting (which I'm not familiar with) may have an example reverse proxy config you should use as a starting point if it exists.

[–] TheBlindPew@lemmy.dbzer0.com 1 points 11 months ago

Ive got a reverse proxy config that was available in the Audiobookshelf github documentation, I was mainly struggling to understand how to get all of the parts working together. Thanks for the help