Skip to content


I am a curious, technology and outdoor enthusiast. This portal is my focal node in the Inter-webs. Since 2006, this is where I retreat – to write, document and essentially keep track of various things evolving in my life.


I believe in all things open-source and over time shifted to owning my content in the digital space. Linux is my primary operating system on all machines I own. Powered by docker, I self-host the following tools that I use on a need-to basis.









I also manage a few portals for family and friends. If you need help setting any of the above applications, I’d be more than happy to help! Just ping!


I am currently with USAID with over 13 years of combined experience in Risk Management, Technology and Education; an alumnus of Columbia University, New York and consulting expertise from Willis Towers Watson, Boston and Infosys, India. More on my LinkedIn page.


The best way to reach me is via this site. Send me a message or just reply to one of my posts! I’m reasonably active on the following social media portals:

Srikanth Perinkulam

2 thoughts on “About”

    Hi Srikanth,

    Thank you for writing up this guide ( on how to install Trilium on a server. I’m very new to Docker and I cannot get it to work the way you intended. When I look at the status of the containers, the traefik one keeps crashing every 10 seconds with error code 1. I tried starting Docker in debug mode, but so far that has given nothing useful. I do wonder if the traefik-ssl.yml file needs to be modified to my current config? I read somewhere that you should replace – –${} with your own email address that you have registered at Let’s Encrypt, but I don’t know where to start on this one. If you can find the time, could you please point me in the right direction?
    Many Thanks, Erwin

    Hi Erwin,

    You’d definitely want to have your own e-mail address there for the ACME_EMAIL. Just replace the noreply[at]example[dot]com with the e-mail address you’d like to use. That alone shouldn’t be causing the container to crash though. Unfortunately, the error code 1 is a ‘catch-all’ code and does not provide much insight.

    A couple other things that I can think of are:
    01: See if you’re able to capture the logs from any of these commands before the container crashes:
    docker logs -f
    docker service logs

    02. Your socket-proxy could be causing you issues. While note ideal, try this yml instead and see if that does the trick.

    Hopefully one of these helps!

Leave a Reply

Your email address will not be published. Required fields are marked *