Airsonic with reverse proxy

General Discussion
4

jason_a69 I tried out Airsonic (and gave up on it because it used way too much memory for my tastes).

If you haven’t already checked it out, I would recommend looking into caddyserver as a reverse proxy. It’s easier to configure and its automatic SSL functionality is pretty slick. Only catch is sometimes you have to change the ports in other things that may be trying to listen in on ports 80 and 443.

Should you go down that route, there were two ways to go:

  1. Use the default config of the airsonic service with the path of /airsonic.
  2. Remove the path argument from the airsonic service (the -Dserver.context-path=/airsonic portion).

Option 1 was a stumper for me because I followed their config for caddy to the point (except for the conf file [virtual host] since I just use a singular Caddyfile) but it was wrong in a couple ways given the dietpi setup config. Going to : won’t work because it’s set to /airsonic. If I put the proxy to /airsonic, I got an error about too many redirects.

I fixed that by using the following entry for my Caddyfile:

mysubdomain.myhostname.com {
	proxy / <hostip>:<listeningport>/airsonic {
		transparent
			without /airsonic
	}
}

If you’re not going to host any other websites, you can remove the path argument so that it’s listening on just :. That simplifies the entry in the Caddyfile a little bit:

mysubdomain.myhostname.com {
	proxy / <hostip>:<listeningport> {
		transparent
	}
}