+-----------------------------------------+
| Server: Part 3                          |
+-----------------------------------------+-------+
|                                                 |
| Date: 20181129-22:44                            |
| Author: Sloum                                   |
| Soundtrack: - None -                            |
|                                                 |
+-------------------------------------------------+-------------------------+

Things have progressed further with the server. I got Gophernicus set
up. It did not have the best documentation and I dont have a good sense
of all of the options, but it seems to be configured alright. I have it
set to server user files from a gopher folder in their home directory.
It also serves up server files for the main gophermap and files from
elsewhere on the server drive.

As mentioned before, I got dynamic dns set up and working. However,
there seem to be some issues with it that I do not udnerstand. I am
not sure if they are on the side of the Pi or my router (or some other
player in the system). The dynamic dns is working, as I am often able
to connect via my domain name (either to gopher or SSH). Sometimes
though, all requests just time out. This issue seems to happen more
and more over the last day or so, but seems to occur randomly. I had
at first thought that the wifi or pi were going to sleep. I verified
that this is not the case, as best as I can tell (I used `iwconfig` to
check on the "Power Management" setting for wlan0 (which I am using to
connect to the router). It is pretty frustrating that sometimes I get
a connection and sometimes I do not. When things time out, it seems
clear that they are not getting to the pi. So I am thinking it may be
an issue with my dynamicdns or my router, but have been having trouble
finding suggestions online. For any that want to see if they can
connect to the gophersite:

                 gopher://colorfield.space:70/

If I can sort out this intermittent connection drop then I can finish
up the last few bits of the shell and start taking on my first user
or few.

I have noticed via `tail /var/log/syslog` that for every request to
the server that actually reaches it I get to rows:

1. systemd[1]: Started Gophernicus
2. in.gophernicus[1234]: request for "gopher://site.url:70/" from ...

The second one seems pretty clear, just a record of each request. This
is in line with what I would expect to see. The first one though, seems
a little odd. Why would Gophernicus need to "Start" for each request?
The daemon process should just always be running. If any of you out
there are running gophernicus and want to check if your server gives
you the same message for every request, I would appreciate the sanity
check (let me know: [email protected])

I'll keep digging tomorrow, and hopefully finish the shell over the
weekend. If I have time to write some user creation scripts that would
be a good step too.

I'm glad to have gotten to where things are though! Lots of fun progress.

Goodnight gopherspace!

You are viewing proxied material from circumlunar.space. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.