this post was submitted on 15 Sep 2025
33 points (97.1% liked)

Selfhosted

51631 readers
635 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
33
Beginners Questions about Audiobookshelf, DNS and nginx (lemmy.dbzer0.com)
submitted 1 week 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
[–] Lyra_Lycan@lemmy.blahaj.zone 3 points 1 week ago* (last edited 1 week ago) (2 children)

On your DNS provider, the domain name must point to the public IP of your router. All devices connected to your network use the same public IP.

On the router, ports 80 and 443 must be forwarded to the (local IP of) the machine running Nginx.

Nginx must have the domain name point to the local IP of the machine running ABS.

Are you using Nginx or Nginx Proxy Manager?

Edit: If Nginx, as they're on the same docker setup, instead of the Nginx config pointing to ABS' local IP you can use 172.17.0.1 (iirc) and the port you used, or the container_name from compose.yaml, e.g. audiobookshelf:3748

I use NginX Proxy Manager so my methods may differ slightly.

Note about domains: It's always good to buy one.

RIP DuckDNS.. it used to be a fairly reliable Dynamic DNS (DDNS) and it cost nothing to make an account and five domains.. However, apparently, it was shut down without notice under a month ago.

[–] TheBlindPew@lemmy.dbzer0.com 1 points 6 days ago (1 children)

Is 172.17.0.1 like dockers loopback for its own services?