{"id":5895,"date":"2021-06-16T23:02:38","date_gmt":"2021-06-16T23:02:38","guid":{"rendered":"https:\/\/www.geekdecoder.com\/?p=5895"},"modified":"2021-06-16T23:02:38","modified_gmt":"2021-06-16T23:02:38","slug":"setting-up-ipfs-server-with-nginx-and-gateway","status":"publish","type":"post","link":"https:\/\/www.qbytes.cloud\/index.php\/2021\/06\/16\/setting-up-ipfs-server-with-nginx-and-gateway\/","title":{"rendered":"Host a Web Site with a Domain on IPFS"},"content":{"rendered":"

This article describes how to host a web site on IPFS.<\/p>\n

Requirements:
\nAccess to a Registered Domain and DNS records.
\nEdit your DNS to point the A record to the IPFS server. We will need this to resolve in order to install a Let’s Encrypt Certificate.<\/p>\n

Lets Start with an Update<\/p>\n

\n# sudo apt update \n# sudo apt upgrade -y\n<\/pre>\n
Lets create a new user account to run IPFS and switch to it:<\/p>\n
\n# adduser ipfs\n<\/pre>\n
Install sudo<\/p>\n
\n# apt install sudo\n<\/pre>\n
Edit sudo and add the ipfs user<\/p>\n
\n# visudo\n<\/pre>\n
Add the IPFS user below root<\/p>\n
\n# User privilege specification\nroot    ALL=(ALL:ALL) ALL\nipfs    ALL=(ALL:ALL) ALL\n<\/pre>\n
change to the IPFS user.<\/p>\n
\n# su ipfs\n<\/pre>\n
Install IPFS
\nGet the latest release at https:\/\/dist.ipfs.tech\/#kubo<\/a><\/p>\n
\n$ wget https:\/\/dist.ipfs.tech\/kubo\/v0.16.0\/kubo_v0.16.0_linux-amd64.tar.gz\n$ tar xfv kubo_v0.16.0_linux-amd64.tar.gz\n$ cd kubo\n.\/install.sh\n<\/pre>\n
Initialize IPFS:<\/p>\n
\n$ ipfs init --profile=server\n<\/pre>\n
Switch to the root user:<\/p>\n
\n$ exit\n<\/pre>\n
Allow the ipfs user to run long-running services by enabling user lingering for that user:<\/p>\n
\n# loginctl enable-linger ipfs\n<\/pre>\n
Create the file \/etc\/systemd\/system\/ipfs.service with this content:<\/p>\n
\n# nano \/etc\/systemd\/system\/ipfs.service\n<\/pre>\n
 <\/p>\n
\n[Unit]\nDescription=IPFS Daemon\nAfter=syslog.target network.target remote-fs.target nss-lookup.target\n[Service]\nType=simple\nExecStart=\/usr\/local\/bin\/ipfs daemon --enable-namesys-pubsub\nUser=ipfs\n[Install]\nWantedBy=multi-user.target\n<\/pre>\n
Enable and start the service:<\/p>\n
\n# systemctl enable ipfs\n# systemctl start ipfs\n<\/pre>\n
IPFS should be up and running, and start when the server boots.<\/p>\n
Check IPFS<\/p>\n
\n$ su ipfs\n$ ipfs swarm peers\n<\/pre>\n
Add Website Files<\/p>\n
Create a folderfor your website files. Add this folder in the ipfs\/home directory<\/p>\n
\n$ cd ~\n$ mkdir mysitefiles\n<\/pre>\n
Upload the site files to the directory. Now we can add these to IPFS with the following contect<\/p>\n
\n$ ipfs add -r <path>\n<\/pre>\n
This adds all contents of the folder at to IPFS, recursively. You should see output similar to this:<\/p>\n
\n$ ipfs add -r mysitefiles\n<\/pre>\n
Output:<\/p>\n
\n ipfs add -r mysitefiles\/\nadded QmZrSe9TABdSsWL38FJTp4fW7TposFuzRLSBRYAEMVt1RE mysitefiles\/about.html\nadded Qmdf1mYmCjivJWcXpGikf87PV5VkBo6DQugsjq6GdNZ1az mysitefiles\/index.html\nadded QmW8U3NEHx3p73Nj9645sGnGa8XzR43rQh3Kd52UKncWMo mysitefiles\/moon-logo.png\nadded QmQ91HDqAt1eE7X4DHuJ9r74U3KgKN3pDGidLM6sadK2q2 mysitefiles\n 12.66 KiB \/ 12.66 KiB [==================================================================================================] 100.00%\n<\/pre>\n
Each of the long sequence of numbers is called a Content Identifier or CID. These are cryptographically hashed. We can now check to see if the site loads. You can check and use an active gateway here: https:\/\/ipfs.github.io\/public-gateway-checker\/<\/a><\/p>\n
Add the main Content Identifier (CID) folder ID to the URL. How to link to content on IPFS.<\/p>\n
\nhttps:\/\/ipfs.io\/ipfs\/<CID>\n# e.g\nhttps:\/\/ipfs.io\/ipfs\/QmQ91HDqAt1eE7X4DHuJ9r74U3KgKN3pDGidLM6sadK2q2\n<\/pre>\n
Now we can set up the DNS records. See: https:\/\/dnslink.io\/#introduction<\/a><\/p>\n
Login to manage your DNS. Add the following TXT Record:<\/p>\n
\ndnslink=\/ipfs\/QmQ91HDqAt1eE7X4DHuJ9r74U3KgKN3pDGidLM6sadK2q2\n<\/pre>\n
Here is my Namecheap DNS
\n\"\"<\/a><\/p>\n
Install nginx with Let’s Encrypt SSL certs
\nChange to root<\/p>\n
\n$ su root \n<\/pre>\n
 <\/p>\n
\n# apt-get update\n# apt-get install nginx\n<\/pre>\n
Check status to make sure it started and is not throwing any errors:<\/p>\n
$ systemctl status nginx\n<\/pre>\n
Results<\/p>\n
\u25cf nginx.service - A high performance web server and a reverse proxy server\n   Loaded: loaded (\/lib\/systemd\/system\/nginx.service; enabled; vendor preset: en\n   Active: active (running) since Wed 2021-06-16 22:59:51 UTC; 1min 44s ago\n     Docs: man:nginx(8)\n  Process: 13062 ExecStartPre=\/usr\/sbin\/nginx -t -q -g daemon on; master_process\n  Process: 13063 ExecStart=\/usr\/sbin\/nginx -g daemon on; master_process on; (cod\n Main PID: 13064 (nginx)\n    Tasks: 2 (limit: 1163)\n   Memory: 5.3M\n   CGroup: \/system.slice\/nginx.service\n           \u251c\u250013064 nginx: master process \/usr\/sbin\/nginx -g daemon on; master_pr\n           \u2514\u250013065 nginx: worker process\n\nJun 16 22:59:51 ip-10-0-1-209 systemd[1]: Starting A high performance web server\nJun 16 22:59:51 ip-10-0-1-209 systemd[1]: nginx.service: Failed to parse PID fro\nJun 16 22:59:51 ip-10-0-1-209 systemd[1]: Started A high performance web server\nlines 1-16\/16 (END)\n\n<\/pre>\n
Get your IP and open it with browser to make sure Nginx is serving its default page:<\/p>\n
$ curl -s domain.com\n$ curl -s Ip_address\n<\/pre>\n
Now browse to http:\/\/your-ip-here and you should see the Nginx default page “Welcome to Nginx”.<\/p>\n
\"\"<\/a><\/p>\n
Set Up your nginx configs:<\/p>\n
$ sudo mv \/etc\/nginx\/sites-available\/default \/etc\/nginx\/sites-available\/default_back\n# sudo nano \/etc\/nginx\/sites-available\/default\n<\/pre>\n
Copy and paste this config (change example.com to your domain)<\/p>\n
\n\nserver {\n    server_name example.com www.example.com;\n    server_tokens off;\n\n    listen 80;\n    listen [::]:80;\n    listen 443 ssl;\n    listen [::]:443 ssl;\n\n    location \/ {\n        proxy_pass http:\/\/localhost:8080;\n        proxy_http_version 1.1;\n        proxy_set_header Upgrade $http_upgrade;\n        proxy_set_header Connection 'upgrade';\n        proxy_set_header Host $host;\n        proxy_cache_bypass $http_upgrade;\n    }\n}\n<\/pre>\n
Test that new config syntax and make sure it is ok:<\/p>\n
$ sudo nginx -t\n<\/pre>\n
If all good reload:<\/p>\n
$ sudo systemctl reload nginx\n<\/pre>\n
Add Lets Encrypt according to this article – https:\/\/www.geekdecoder.com\/set-up-lets-encrypt-on-debian-10\/<\/a><\/p>\n
The final config should resemble this:<\/p>\n
\nserver {\n    server_name example.com www.example.com;\n    server_tokens off;\n\n    location \/ {\n        proxy_pass http:\/\/localhost:8080;\n        proxy_http_version 1.1;\n        proxy_set_header Upgrade $http_upgrade;\n        proxy_set_header Connection 'upgrade';\n        proxy_set_header Host $host;\n        proxy_cache_bypass $http_upgrade;\n    }\n\n    listen [::]:443 ssl ipv6only=on; # managed by Certbot\n    listen 443 ssl; # managed by Certbot\n    ssl_certificate \/etc\/letsencrypt\/live\/example.com\/fullchain.pem; # managed by Certbot\n    ssl_certificate_key \/etc\/letsencrypt\/live\/example.com\/privkey.pem; # managed by Certbot\n    include \/etc\/letsencrypt\/options-ssl-nginx.conf; # managed by Certbot\n    ssl_dhparam \/etc\/letsencrypt\/ssl-dhparams.pem; # managed by Certbot\n\n}\nserver {\n    if ($host = www.example.com) {\n        return 301 https:\/\/$host$request_uri;\n    } # managed by Certbot\n\n\n    if ($host = example.com) {\n        return 301 https:\/\/$host$request_uri;\n    } # managed by Certbot\n\n\n    server_name example.com www.example.com;\n\n    listen 80;\n    listen [::]:80;\n    return 404; # managed by Certbot\n}\n<\/pre>\n
The site should now be available.<\/p>\n","protected":false},"excerpt":{"rendered":"
This article describes how to host a web site on IPFS. Requirements: Access to a Registered Domain and DNS records. Edit your DNS to point the A record to the IPFS server. We will need this to resolve in order to install a Let’s Encrypt Certificate. Lets Start with an Update # sudo apt update … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[74],"tags":[],"class_list":["post-5895","post","type-post","status-publish","format-standard","hentry","category-nginx"],"_links":{"self":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts\/5895","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/comments?post=5895"}],"version-history":[{"count":0,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/posts\/5895\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/media?parent=5895"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/categories?post=5895"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.qbytes.cloud\/index.php\/wp-json\/wp\/v2\/tags?post=5895"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}