Accessing audiobookshelf container from outside network with custom domain and reverse proxy

Synology
1

Hello,

I am new to NAS and Networking so please be patient with me. I am trying to be able to access my audio bookshelf docker container from outside my local network using my custom domain and reverse proxy for protection. The end goal is to have an audiobook server for my family to use on the go.

I have watched all of the YouTube videos and I still just cannot seem to get it to work.

Things I have done so far:

  • Installed Audiobookshelf - working and can access locally with NASIP:port (cannot access locally with abs.customdomain .com (this is the intended subdomain I will be using)
  • at one point today I was able to access nas locally with custom domain and audiobookshelf with abs.customdomain .com:80 but I must’ve done something because now both of those seem to be broken
  • I have setup Reverse Proxy for abs.customdomain.com on ports 80 and 443(using Synology native reverse proxy)
  • I have Created DDNS with Synology .me - with goal to have my public IP update when needed - working according to DSM
  • I have setup ssl certificate for customdomain .com with subdomains of “abs”.
  • I have created a Cname for my abs subdomain pointing to my Synology.me I set up

Assuming I am not combining/confusing idea from different tutorials (I very well might be) I believe my issues are coming down to port forwarding on my router and setting up DNS records with porkbun (my domain provider).

I am new to the forum and am unsure what specific screen shots would be needed for people to analyze. I will happily add them if/when they are requested.

Any help would be massively appreciated.

AJ

2

Forward port 443 (WAN) to 443 (NAS_IP) on your router.

Then set your reverse proxy to
incoming: https/audiobookshelf.<domain.name>/443
target: http/your NAS IP/container external port.

858×956 36.4 KB

Be sure your SSL cert for the audiobookshelf subdomain is associated on the NAS.

3

Thank you for your response!

I have done the things you suggested. But I’m still unable to connect from outside local network. Do I also need to do anything with DNS @ porkbun?

Currently have cname abs.domain.com pointing to my synology.me

I am wondering if I need to just start the networking part from scratch.

4

Check that your 443 port is open. Any easy way to do this is via www.canyouseeme.org

5

I have set up port forwarding on 443 and 80 on my router: nas IP and external and internal ports set tp 443, and 80 on two separate rules. However when I check to see if the port is open It still says it is closed. Im wondering if there is something with my ISP that may be blocking the port?

Maybe I need to reboot my router for the rules to take hold?

6

Your ISP may be blocking those ports, or your ISP may assign CGNAT IPs which breaks port-forwarding. Starlink and most 5G ISPs use CGNAT, and other ISPs are moving to CGNAT. There are workarounds should any of those be your situation (Cloudflare tunnels, Tailscale, VPS, for example).