Depending on the nature of the application or service which you want to make accessible over Lokinet, you may want to only run a temporary SNApp, or a SNApp that continues to persistently use the same .loki pubkey.
A temporary SNApp is a service accessible over Lokinet that does not have a permanent address. This means that the address you supply to others will not work once the server hosting the SNApp is restarted.
If you want users to be able to access your application or service over an extended period of time, a temporary SNApp is not recommended.
If you only want to host a temporary SNApp, jump to Step 2.
Note: This guide assumes you are running a standard Debian or Ubuntu Linux distribution on the machine on which you'll be hosting the SNApp and that you have Lokinet installed and running on this machine, if not please follow the guide to get Lokinet running. This guide also assumes you are relatively familiar with using the command line.
Step 1: Preparing your Lokinet address
Start by opening your lokinet.ini file and adding a path to where your SNApp key files will be stored.
If you have installed Lokinet from Deb packages, you can open your lokinet.ini file in the nano text editor with the following command:
Otherwise, if you have built Lokinet from source, your lokinet.ini file will be in the folder ~/.lokinet/lokinet.ini, and can be opened in nano with the following command:
With lokinet.ini open in the text editor, scroll down to your [network] section and add the following line:
Alternatively, you can set the filepath to wherever you want your SNApp private key to be stored.
Now, when you restart Lokinet, it will generate your snappkey.private file in the directory you have set.
Step 2: Finding your SNApp's Lokinet address
You can find your SNApp's current address using a host lookup tool:
You can also use the host command (the .loki address to query is the same, but the resolver uses the address 127.3.2.1 as to not conflict with other resolvers you may have installed):
Step 3: Install nginx
Install a proper web server:
Step 4: Configure nginx
Setup a Lokinet exclusive SNApp
If you want your SNApp to be accessible only via Lokinet and not via your IP address or domain name then you will need to configure nginx to run only on the lokinet interface.
First we will need to set the Lokinet interface IP range, we can do this by accessing our Lokinet config file as we did in and adding this line in the [network]section:
this can go underneath your existing network config changes, after this change is made restart Lokinet using:
Once Lokinet is restarted run the following command to open your nginx default configuration file, we are going to make a few changes here.
change any listen directives to use the lokinet IP 10.67.0.1 remove any IPV6 listen directives and replace the .loki address after server_name with the Lokinet address you discovered in
This should leave your default file in sites available looking something like this:
save the changes and exit the file. Once this step is complete you can reload nginx with the following command:
Proceed to
Setup a clearnet and Lokinet accessible SNApp
If you want your SNApp to be accessible via Lokinet and your clearnet IP/Domain name then fewer changes are required. First open /etc/nginx/sites-enabled/default using:
Then add your .loki address (which you discovered in ) as a server_name, after the changes your nginx default file should look something like this:
Proceed to
TIP: By default, you can drop files into /var/www/html to serve them as a SNApp. Make sure they are accessible via the www-data user (or whichever user nginx runs as.
TIP: You can make nginx generate a directory listing of files by adding autoindex on; on a new line into the location block in the nginx config file.
Step 5. Security (Optional)
Make sure no services bind to all interfaces.
Suggested firewall settings when using nginx:
Step 6: All done!
Congratulations! Your SNApp should now be accessible over Lokinet. Use the Lokinet address you discovered in , to access your SNApp
