Title: Setting up a proxy for my Gemini Site

Published: 2021-02-28 17:48

Author: Rev. Fr. Robert Bower


layout: blog


Setting up a proxy for my Gemini Site

Since I started using Gemini I have been trying to figure out a workflow to maintain content on my Gopher hole, my website, and my Gemini capsule. While that is still a work in progress, I have found a way for web users to access my Gemini content. There is a HTTP to Gemini proxy called Kineto that is designed for a single domain.

Kineto is a straight forward setup. Simply follow the directions given in the readme file. I am self hosting and because of ISP restrictions I has one additional thing I needed to do. I needed to edit my hosts file on the machine where Kineto resided. I edited it so the domain name for the Gemini server was equated with the internal IP of the Gemini server. If you are not self hosting with ISP restrictions you will not have to do this.

The trickiest part is setting up the reverse proxy server. I used Nginx and followed directions I found online. All the directions I found online were similar. So any should work. I found two things out by trial and error.

1. I found the Kineto server and the Gemini server can be on the same machine but the reverse proxy server needs to be on a different machine. Different virtual machines are fine.

2. If you are going to be using HTTPS rather than HTTP and are going to be using Certbot, you need to include the server_name in the reverse-proxy.conf file for the auto-configuration to work.

Now non-Gemini users can find my Gemini content via my proxy.

Links Bibliography

Kineto can be found here.

My Gemini Capsule via Kineto

Zettelkasten ID **settingupkineto-2021-02-28-1748**


Proxied content from gemini://frrobert.net/log/settingupkineto-2021-02-28-1748.gmi

Gemini request details:

Original URL
Status code
Proxied by

Be advised that no attempt was made to verify the remote SSL certificate.