Subsonic & Caddy – oh my…


Subsonic has the nasty habit of generating certain URLs in a very hardcoded way.

The login screen for example. If you call index.view and are not logged in, it redirects you to $ServerSubsonicThinksItIs/login.view.

That will be localhost, if you want to do the „oh yay, let’s reverse proxy here“ thing. To make matters worse, $ServerSubsonicThinksItIs also contains protocol and port. This is apparently due to the implementation of Subsonics „generate a“ redirection.

As far as I can see, only the login and settings pages are the ones that are affected by this. They are still accessible if you manually add /login.view to your public address.

Of course, you can tell Subsonic to believe that it is on the servername you chose for it. As long as Subsonic and the reverse proxy server are in agreement of which host, path & port are shown to the browser, everything is fine. With non-encrypted http that is.

Of course you can re-enable https on Subsonic, in order to successfully proxy everything from A to B, but…

…Caddy checks the validity of the SSL certificate of whatever site it reverse-proxies to. And throws a Bad Gateway if it doesn’t like what it sees. This is actually done with a reason, but it doesn’t help me right now.

As far as I can see, I either have to wait for…

  • Subsonic finally learning to generate sane URLs or
  • Caddyserver being able to ignore faulty certificates upstream

Subsonic with Caddy

Ok, now that there is Let’s Encrypt, I thought that I shouldn’t have to do this certificate hackery all the time when Subsonic updates or the StartSSL certificate expires.

Caddyserver is the first Webserver/Proxy that I found that has most of the process automated and build in, so I’m using this. Getting started with this was pretty straightforward: Download, expand,  create a config file and before you start up, make sure that Caddy can run on port 80 without requiring to be root:

sudo setcap cap_net_bind_service=+ep ./caddy

My Caddyfile eventually ended up looking like this: {
 proxy / localhost:4040 {
 proxy_header Host
 proxy_header Scheme https

Well, it turned out to not be quite as easy. First I also had to make Subsonic stop hogging port 443. Those settings are found in /etc/default/subsonic. And while you’re at it, also edit out any certificates you may have added earlier in /usr/bin/subsonic. Oh, and make sure to note down which port non-https Subsonic runs, hopefully not 80, because Caddy needs that! I may have chosen 4040.

Restart Subsonic and make sure that you can reach it on the correct ports.

As stated, Caddy also needs to run on Port 80 for a brief moment. This is so it can do the certificate domain validation process. So edit your /etc/apache2/ports.conf to make sure not to block anything.

Restart apache2.

Now, to find out if everything works, start Caddy. If all is good, you’ll see a glorious all-ok message and can now access the server via https with a valid certificate.

But as you’ve undoubtedly noticed, Caddy isn’t running as a service yet. Thankfully Ubuntu has Upstart. So, add in a new file /etc/init/caddyservice.conf (thank you Mathias):

description "Caddy Server startup script"
author "Mathias Beke"
start on runlevel [2345]
stop on runlevel [016]
setuid runasme
setgid runasme
respawn limit 10 5
 cd /home/runasme/
 exec ./caddy

At this point I want to take a short moment to mention that whoever thinks that the Upstart Cookbook is an easy entry-level document is clearly out of their mind. Seriously, this „Cookbook“ has a whole chapter named „Critique of the System V init System“!

But I digress. If you don’t make the same mistake as me and confuse init with init.d, then you’re golden and now have a Caddy running as a service, forwarding requests to your Subsonic installation.

The only issue I haven’t been able to solve is that Subsonic has some stupid static URL linking going on so I have to open the settings in a new tab. But I can live with that.

Mehr Überwachung!

Ich wollte gerade einen längeren Text dazu schreiben in dem ich erneut darauf verweise, dass all die bestehende Überwachung wieder einmal erschreckend wenig (nämlich eigentlich gar nichts) verhindert hat, dass die Spuren, die jetzt aktuell geholfen haben aus unter anderem einem weggeworfenen Handy (unverschlüsselt) plus einem nicht gelöschtem Streckenverlauf im Navi eines Mietwagens bestanden.

Dazu könnte ich darauf verweisen, dass Terroristen immer auch einen weiteren Weg zur geheimen Kommunikation finden werden. Oder dass es denen ja eigentlich egal ist, weil sie ja eh auf eine Konfrontation aus sind.

Aber diejenigen, die das hier lesen sind eh schon überzeugt, und die anderen werde ich damit nicht überzeugen. Also lasse ich es…

Webcomic Montag: Die Apokalypse!

Lange war es still um diese Rubrik, aber ich habe ja wieder ein wenig neues Futter für Euch!

Fangen wir so richtig romantisch an. Romantically Apocalyptic um genau zu sein. Visuell ein meiner Ansicht nach herausragender Webcomic, irgendwo zwischen gezeichnet und photorealistisch. Die Story kann ich leider nicht wiedergeben, die ist zu bizarr. Generell sehen wir die Postapokalypse, wie sie der Captain, Snippy, Pilot und Engie erleben. Wenn Ihr seltsamen Humor und die Postapokalypse mögt, werdet Ihr das hier lieben.

Schwarzhumoriger und dabei aber auch zugänglicher kommt Gone with the Blastwave daher. Wieder Postapokalypse. Hier kämpfen namen- und gesichtslose Soldaten dreier nicht wirklich definierbaren Armeen gegeneinander. Warum? Daran kann sich niemand mehr so recht erinnern. Aber seit wann hält das Leute davon ab, aufeinander zu schießen, richtig?