Indieweb reader access with Wordpress on shared hosting

An Indieweb reader (like Monocle, Together or Indigenous) authenticates you with your personal website which also tells the indieweb reader where to fetch your feeds. Wordpress is a popular option for a personal website.

Although I’m not an active wordpress user, I’ve helped a few wordpress users interested in adding Indieweb functionality. I haven’t had much of a problem with the indieweb wordpress plugins and themes but from time to time, I’ve needed a little help from the usual suspects on the indieweb-wordpress chat.

I also have very little experience with shared hosting but it seems that with their one-click wordpress installers, this could be a good option to experience the benefits of an indieweb reader while avoiding more complex hosting options. Shared hosting seems to be much more affordable, too.

At IndiewebCamp Austin 2019, I investigated Dreamhost and Reclaim Hosting as two shared hosting options for interoperability with indieweb readers.

It turned out that what I thought was a missing piece was already available. Your website needs to declare where you keep your feeds so that your indieweb reader can find them. On wordpress, this can be accomplished with the aperture plugin. So, I added and activated this plugin to my existing indieweb wordpress test site hosted on dreamhost. The plugin automates the creation of an aperture account and adds a microsub link tag to your web page which points to your aperture url so that your indieweb reader can find your feeds. This ability to declare where you are storing your feeds allows you to change the microsub provider that is hosting your feeds. There are already several microsub providers to choose from.

Next, I tried logging into the Monocle indieweb reader and received a “bearer token not supplied” error.

Bearer token not supplied

Aaron Parecki who was nearby explained to me that the web server running wordpress was unfortunately stripping out the authorization request header. A quick search revealed a workaround for this issue by adding the following line to your .htaccess file:

SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

At this point, my unfamiliarity with shared hosting bit me as I had purposely avoided looking under the hood of my account. So, I assumed I could just use my normal credentials to upload the needed .htaccess file but my changes were ignored. It did not occur to me that there was another dreamhost user account under which the one-click wordpress was installed and I needed to use those credentials to make the changes.

As I didn’t immediately figure this out, I decided to try Reclaim Hosting as an alternative shared hosting provider and installed wordpress and the appropriate indieweb plugins and an indieweb-friendly theme. I had better luck this time (and much more affordable). Again, I ran into the “bearer token not supplied” error when logging into the indieweb reader, but luckily there was no multiple user account confusion with reclaim hosting. I could easily add the .htaccess file and confirm that it fixed the “bearer token not supplied” issue.

However, somehow I found myself in a coherency problem state as I received a “This token was issued to a different user” error where aperture was saying my microsub url was different than my website was claiming (different aperture user accounts). I was not able to resolve this issue by reinstalling the aperture wordpress plugin but I was able to resolve it by changing the aperture_microsub_url option name in the wp_options database table to match the one aperture was expecting.

IndiewebCamp Austin Thoughts

Day 1 Pic As expected, the day one schedule for IndiewebCamp Austin included a variety of cool sessions like p2p websites with Dat with Beaker Browser which allows you to easily create and share content without having to worry about server-side hosting and for those who like to worry about server-side hosting, there was Web Hosting and Migration.

On project day, I investigated two hosting providers for wordpress for the purpose of integrating with an indieweb reader. It was great that Aaron Parecki and David Shanske were around to help. As a Jekyll user, I don’t really have any skin in the game as far as needing a wordpress solution but it was a good learning exercise and I hope to document something soon.

It was also great seeing people experimenting with totally different platforms I’ve never heard of rather than the well-known ones.

Thanks Manton for organizing another IndiewebCamp!

IndiewebCamp Austin is this weekend!

I’m really looking forward to IndiewebCamp Austin. Something we didn’t have last time was indieweb readers. I have been using three of them and they all are fantastic. It is easy to switch among them because your subscribed feeds are maintained on a different server that each of the readers can point to. Here is Aaron Parecki introducing some of the new social readers at last year’s Indieweb Summit.

Saturday is open space sessions which will include introductory ones for people just getting started and Sunday is projects. There is still time to register for IndiewebCamp Austin.