Hardware recommendations for hosting ProjectSend<\/h2>\n
I recommend the following hardware for hosting ProjectSend:<\/p>\n
- \n
- Official Raspberry Pi 3 Case - Red\/White<\/a><\/li>\n
- Raspberry PI 3 Model B A1.2GHz 64-bit quad-core ARMv8 CPU, 1GB RAM<\/a><\/li>\n
- SanDisk Ultra 128GB microSDXC UHS-I Card with Adapter, Black, Standard Packaging (SDSQUNC-128G-GN6MA)<\/a><\/li>\n
- CanaKit 5V 2.5A Raspberry Pi 3 Power Supply \/ Adapter \/ Charger (UL Listed)<\/a><\/li>\n
- AmazonBasics RJ45 Cat-6 Ethernet Patch Cable - 3 Feet (0.9 Meters)<\/a><\/li>\n<\/ul>\n
If you had a spare micro USB charger that came along with your typical Android phone, you can use it to power your Raspberry Pi 3 instead of buying the CanaKit 5V 2.5A Raspberry Pi 3 Power Supply \/ Adapter \/ Charger (UL Listed)<\/a>.<\/p>\n
Prerequisite hardware to install operating system onto microSD<\/h2>\n
Raspberry Pi 3 board will load an operating system from a microSD card. Hence, we will need to have a computer with a SD card reader. If your computer does not come with a SD card reader<\/a>, you have to get one. <\/p>\n
Getting a copy of Raspbian Lite<\/h2>\n
Once we had gotten the hardware, we can then proceed to download a copy of Raspbian Jessie Lite<\/a>. The latest Raspbian operating system is available at https:\/\/www.raspberrypi.org\/downloads\/raspbian\/<\/a>. As of this writing, the one that was available was \"RASPBIAN JESSIE LITE\":<\/p>\n
![\"2017-07-13](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/2017-07-13_raspbian-download-page.gif\")
<\/p>\nClick on the Download ZIP<\/a> button and save the file onto your file system. <\/p>\n
Installing Raspbian Lite on the microSD card<\/h2>\n
Once you had gotten the
.zip<\/code> file in your computer, extract the.img<\/code> file from the.zip<\/code> file. The.img<\/code> file is the operating system image that we will use for installing Raspbian Jessie Lite onto the microSD card.<\/p>\nIf you have a MacBook, you can use Etcher to install the operating system image onto your microSD card<\/a>.<\/p>\n
If you are using a windows machine, you can use Win32DiskImager to install the operating system for your Raspberry Pi 3<\/a>.<\/p>\n
If you are using a Linux desktop, you should be able to Etcher to install the operating system for your Raspberry Pi 3.<\/p>\n
Enabling SSH server for accessing your Raspberry Pi 3 without connecting a keyboard and monitor to it<\/h2>\n
With an SSH server running on Raspbian Jessie Lite, we do not have to find a spare keyboard and monitor in order to configure Raspbian Jessie Lite after it had booted up for the first time. To ensure that we have the SSH server running after the first boot, we can create a file named \"ssh\u201d in the boot partition of the SD card:<\/p>\n
![\"Raspbian](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/raspbian-jessie-lite-20170705-boot-with-ssh-file.gif\")
<\/p>\nAssembling the hardware to host ProjectSend<\/h2>\n
Once you have installed Raspbian Jessie Lite onto your microSD card, remove your microSD card from your SD card reader and insert it to the SD card slot on the Raspberry Pi 3 board. After that, proceed to assemble the Raspberry Pi 3 board to the Official Raspberry Pi case<\/a>.<\/p>\n
Booting up your Raspbian Lite operating system<\/h2>\n
With the assembly of your Raspberry Pi 3 board and Official Raspberry Pi case, you need to connect one end of the RJ45 cable to the RJ45 port on your Raspberry Pi 3 board and the other end of the cable to one of the switch port of your home router. After that, plugin your micro USB cable and supply power to your Raspberry Pi 3 board.<\/p>\n
Finding the IP address of your Raspberry Pi 3<\/h2>\n
When Raspbian Jessie Lite boots up, it will request an IP address from your router. We will need this IP address in order to SSH into the Raspberry Pi 3. Go to your router's address allocation table and find an entry with the name raspberrypi<\/strong>. Note that IP address for SSH access.<\/p>\n
SSH into your Rasbian Jessie Lite with the default credentials<\/h2>\n
With the IP address, we can then SSH into our Raspberry Pi 3. Assuming that the router had given our Raspberry Pi 3 the IP address 192.168.0.118<\/strong>, we will then open up a terminal program and enter the following command:<\/p>\n
\r\nssh pi@192.168.0.118\r\n<\/pre>\n
The default password for the default user pi<\/strong> is raspberry<\/strong>. Enter raspberry<\/strong> when the ssh command prompts for a password and we will be able to get into our Raspbian Jessie Lite to perform other configurations.<\/p>\n
After logging into your Raspbian Jessie Lite successfully, you will be able to see the following output:<\/p>\n
\r\nThe programs included with the Debian GNU\/Linux system are free software;\r\nthe exact distribution terms for each program are described in the\r\nindividual files in \/usr\/share\/doc\/*\/copyright.\r\n\r\nDebian GNU\/Linux comes with ABSOLUTELY NO WARRANTY, to the extent\r\npermitted by applicable law.\r\n\r\nSSH is enabled and the default password for the 'pi' user has not been changed.\r\nThis is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.\r\n<\/pre>\n
Changing the default password for user pi<\/h2>\n
As hinted by the server output, we should change the default password for the pi<\/strong> user. To do so, we enter the following command into the terminal after we had logged into Raspbian Jessie Lite as the pi<\/strong> user:<\/p>\n
\r\npasswd\r\n<\/pre>\n
At the prompt, type in raspberry<\/strong> for (current) UNIX password<\/strong> and your favourite password for the next two prompts. <\/p>\n
Configuring the locale settings<\/h2>\n
Once we have changed the password, we should configure the locale settings too.<\/p>\n
To do so, we first run the Raspberry Pi Software Configuration Tool:<\/p>\n
\r\nsudo raspi-config\r\n<\/pre>\n
And use it to generate the \"en_US.UTF-8\" locale and set it as the default locale for the system environment:<\/p>\n
![\"raspi-config](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/raspi-config-raspbian-jessie-lite-with-localisation-options-selected.gif\")
<\/p>\n![\"raspi-config](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/raspi-config-raspbian-jessie-lite-with-localisation-options-change-locale-selected.gif\")
<\/p>\n![\"raspi-config](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/raspi-config-raspbian-jessie-lite-screen-for-generating-en-us-utf-8-locale.gif\")
<\/p>\n![\"raspi-config](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/raspi-config-raspbian-jessie-lite-setting-en-us-utf-8-as-default-locale-for-system-environment.gif\")
<\/p>\nAfter doing so, open up
\/etc\/default\/locale<\/code> with nano:<\/p>\n\r\nsudo nano \/etc\/default\/locale\r\n<\/pre>\n
And updated the contents to look like the following:<\/p>\n
\r\nLANG=en_US.UTF-8\r\nLC_ALL=en_US.UTF-8\r\nLANGUAGE=en_US.UTF-8\r\n<\/pre>\n
This will ensure that the locale setting persist through system reboots.<\/p>\n
Installing the MySQL database server on Raspbian Jessie Lite <\/h2>\n
ProjectSend requires a MySQL database instance for persisting data. Hence, after setting the locale, we proceed to install MySQL database on Raspbian Jessie Lite.<\/p>\n
To do install the MySQL client and MySQL server on Raspbian Jessie Lite, we run the following command:<\/p>\n
\r\nsudo apt-get install mysql-server mysql-client -y\r\n<\/pre>\n
The command will prompt the following screens for the creation of a password for the root user:<\/p>\n
![\"Configuring](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/configuring-mysql-server-5.5-on-raspbian-jessie-lite-enter-root-password.gif\")
<\/p>\n![\"Configuring](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/configuring-mysql-server-5.5-on-raspbian-jessie-lite-repeat-root-password.gif\")
<\/p>\nAfter the command had completed, we can run the following command to verify whether MySQL Server was successfully installed:<\/p>\n
\r\nsudo systemctl status mysql\r\n<\/pre>\n
If MySQL Server was successfully installed, you will see output similar to the following:<\/p>\n
\r\n\u25cf mysql.service - LSB: Start and stop the mysql database server daemon\r\n Loaded: loaded (\/etc\/init.d\/mysql)\r\n Active: active (running) since Fri 2017-08-11 11:12:40 UTC; 7min ago\r\n CGroup: \/system.slice\/mysql.service\r\n \u251c\u25006110 \/bin\/sh \/usr\/bin\/mysqld_safe\r\n \u2514\u25006454 \/usr\/sbin\/mysqld --basedir=\/usr --datadir=\/var\/lib\/mysql --plugin-dir=\/usr\/lib\/mysql\/plugin -...\r\n\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.general_log OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.help_category OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.help_keyword OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.help_relation OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.help_topic OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.host OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.ndb_binlog_index OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.plugin OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.proc OK\r\nAug 11 11:12:57 raspberrypi \/etc\/mysql\/debian-start[6525]: mysql.procs_priv OK\r\n\r\n<\/pre>\n
Installing PHP on Raspbian Jessie Lite<\/h2>\n
Since ProjectSend is written in PHP, we will install the necessary PHP components next. To install PHP on Raspbian Jessie Lite, we will run the following command:<\/p>\n
\r\nsudo apt-get install php5 php5-fpm php5-mysql -y\r\n<\/pre>\n
After the command had completed, we can run the following to verify whether the PHP FastCGI Process Manager is up and running:<\/p>\n
\r\nsudo systemctl status php5-fpm\r\n<\/pre>\n
You should see output similar to the following if PHP FastCGI Process Manager is running fine:<\/p>\n
\r\n\u25cf php5-fpm.service - The PHP FastCGI Process Manager\r\n Loaded: loaded (\/lib\/systemd\/system\/php5-fpm.service; enabled)\r\n Active: active (running) since Fri 2017-08-11 15:10:02 UTC; 4min 7s ago\r\n Main PID: 10998 (php5-fpm)\r\n Status: "Processes active: 0, idle: 2, Requests: 0, slow: 0, Traffic: 0req\/sec"\r\n CGroup: \/system.slice\/php5-fpm.service\r\n \u251c\u250010998 php-fpm: master process (\/etc\/php5\/fpm\/php-fpm.conf)\r\n \u251c\u250011000 php-fpm: pool www\r\n \u2514\u250011001 php-fpm: pool www\r\n\r\nAug 11 15:10:02 raspberrypi systemd[1]: Started The PHP FastCGI Process Manager.\r\nAug 11 15:10:04 raspberrypi systemd[1]: Started The PHP FastCGI Process Manager.\r\n<\/pre>\n
Configuring PHP FPM to listen on a port rather than unix socket<\/h2>\n
If you have a reverse proxy server sitting on a different device, you will need to configure your PHP FastCGI Process Manager to listen on a port so that the reverse proxy server is able to talk to your PHP FPM.<\/p>\n
To configure PHP FPM to listen on a port rather than through unix socket, open up
\/etc\/php5\/fpm\/pool.d\/www.conf<\/code> and look for the 'listen' variable and set it to a port number (for example 9000):<\/p>\n\r\nlisten = 9000\r\n<\/pre>\n
Once you had saved your changes, restart PHP FPM by running the following command:<\/p>\n
\r\nsudo systemctl restart php5-fpm.service\r\n<\/pre>\n
You can verify whether your PHP FPM is listening on your new port by running the following command:<\/p>\n
\r\nsudo netstat -lptn\r\n<\/pre>\n
You should see output similar to the following:<\/p>\n
\r\nActive Internet connections (only servers)\r\nProto Recv-Q Send-Q Local Address Foreign Address State PID\/Program name\r\ntcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 2068\/php-fpm.conf)\r\n<\/pre>\n
Installing nginx server<\/h2>\n
If you had setup a reverse proxy server with nginx, Raspian Jessie Lite and Raspberry Pi 3<\/a> or have an nginx<\/a> server running somewhere in your home network, you can skip this section.<\/p>\n
If you do not have a dedicated reverse proxy server<\/a>, you may want to install it on the same Raspberry Pi 3. <\/p>\n
To install nginx server on Raspbian Jessie Lite, you can run the following command:<\/p>\n
\r\nsudo apt-get update\r\nsudo apt-get install nginx -y --fix-missing\r\n<\/pre>\n
Run the following command to verify that your nginx server is running successfully:<\/p>\n
\r\ncurl -0 http:\/\/localhost\r\n<\/pre>\n
You should see output similar to the following if your nginx server is running successfully:<\/p>\n
\r\n<!DOCTYPE html>\r\n<html>\r\n<head>\r\n<title>Welcome to nginx on Debian!<\/title>\r\n<style>\r\n body {\r\n width: 35em;\r\n margin: 0 auto;\r\n font-family: Tahoma, Verdana, Arial, sans-serif;\r\n }\r\n<\/style>\r\n<\/head>\r\n<body>\r\n<h1>Welcome to nginx on Debian!<\/h1>\r\n<p>If you see this page, the nginx web server is successfully installed and\r\nworking on Debian. Further configuration is required.<\/p>\r\n\r\n<p>For online documentation and support please refer to\r\n<a href="http:\/\/nginx.org\/">nginx.org<\/a><\/p>\r\n\r\n<p>\r\n Please use the <tt>reportbug<\/tt> tool to report bugs in the\r\n nginx package with Debian. However, check <a\r\n href="http:\/\/bugs.debian.org\/cgi-bin\/pkgreport.cgi?ordering=normal;archive=0;src=nginx;repeatmerged=0">existing\r\n bug reports<\/a> before reporting a new bug.\r\n<\/p>\r\n\r\n<p><em>Thank you for using debian and nginx.<\/em><\/p>\r\n\r\n\r\n<\/body>\r\n<\/html>\r\n<\/pre>\nGetting a copy of ProjectSend<\/h2>\n
As of this writing, the latest version of ProjectSend is r754. To download this version of ProjectSend from your Raspbian Jessie Lite, you can run the following command:<\/p>\n
\r\ncd \/var\/www \r\nsudo wget https:\/\/github.com\/ignacionelson\/ProjectSend\/archive\/r756.zip\r\nsudo unzip r756.zip\r\nsudo rm r756.zip\r\n<\/pre>\n
With that you will have the source codes at
\/var\/www\/ProjectSend-r756<\/code>.<\/p>\nChanging the owner of ProjectSend's upload folder<\/h2>\n
In order for the file upload feature to work correctly, the user that runs PHP FPM had to own ProjectSend's upload folder. The PHP FPM is run by the www-data user by default. Therefore, we need to run the following command to change the ownership of ProjectSend's upload folder to the www-data user:<\/p>\n
\r\nsudo chown -R www-data:www-data \/var\/www\/ProjectSend-r756\/upload\r\n<\/pre>\n
Creating a new MySQL user and a database instance for your ProjectSend website<\/h2>\n
Your instance of ProjectSend will require a MySQL user along with a database instance for data persistence. To begin with the creation of the user and database instance, we first login to the MySQL server instance with the MySQL client:<\/p>\n
\r\nmysql -u root -p\r\n<\/pre>\n
After providing your password to the password prompt, you can then create the database instance:<\/p>\n
\r\nmysql> CREATE DATABASE myProjectSendDb;\r\n<\/pre>\n
Once your database instance had been created successfully, proceed on to create the MySQL user which could interact with it:<\/p>\n
\r\nmysql> CREATE USER 'anewuser'@'localhost' IDENTIFIED BY 'password';\r\nmysql> GRANT ALL ON myProjectSendDb.* TO 'anewuser'@'localhost';\r\n<\/pre>\n
Creating ProjectSend configuration file for interacting with the database instance<\/h2>\n
Inside the
\/var\/www\/ProjectSend-r756\/includes<\/code> directory, there is asys.config.sample.php<\/code> for us to use as a basis for configuring our ProjectSend instance. <\/p>\nTo configure our ProjectSend instance, we first make a copy of the sample configuration, naming it as
sys.config.php<\/code>:<\/p>\n\r\nsudo cp \/var\/www\/ProjectSend-r756\/includes\/sys.config.sample.php \/var\/www\/ProjectSend-r756\/includes\/sys.config.php\r\n<\/pre>\n
Based on the example values that we had defined earlier, we will replace the database definitions inside
sys.config.php<\/code> to look like the following:<\/p>\n\r\n\/** Database name *\/\r\ndefine('DB_NAME', 'myProjectSendDb');\r\n\r\n\/** Database host (in most cases it's localhost) *\/\r\ndefine('DB_HOST', 'localhost');\r\n\r\n\/** Database username (must be assigned to the database) *\/\r\ndefine('DB_USER', 'anewuser');\r\n\r\n\/** Database password *\/\r\ndefine('DB_PASSWORD', 'password');\r\n<\/pre>\nPreventing incorrect table definition for MySQL Server versions below 5.6<\/h2>\n
Since as of this writing, the MySQL server that was installed was 5.5.57, there cannot be more than one column in a table with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause. <\/p>\n
Hence, we need to edit a particular column definition inside
\/var\/www\/ProjectSend-r756\/install\/database.php<\/code>. Look for expiry_date<\/strong> and change the code to look like the following:<\/p>\n\r\n`expiry_date` TIMESTAMP NOT NULL DEFAULT "2017-01-01 00:00:00"\r\n<\/pre>\n
Configuring nginx to serve HTTP requests for your ProjectSend website<\/h2>\n
To reach our ProjectSend website, we will need to configure our nginx to proxy HTTP requests to our PHP web application<\/a> served by PHP FPM. <\/p>\n
Assuming that we had created a DNS type A record which points
sf.anexistingurl.com<\/code> to our reverse proxy server, the following configuration is what we will need to configure our nginx to proxy HTTP requests to our PHP FPM instance:<\/p>\n\r\nserver {\r\n listen 80;\r\n root \/var\/www\/ProjectSend-r756;\r\n index index.php index.html;\r\n \r\n server_name sf.anexistingurl.com;\r\n \r\n location \/ {\r\n # First attempt to serve request as file, then\r\n # as directory, then fall back to index.html\r\n try_files $uri $uri\/ \/index.html;\r\n }\r\n \r\n error_page 404 \/404.html;\r\n \r\n # redirect server error pages to the static page \/50x.html\r\n error_page 500 502 503 504 \/50x.html;\r\n location = \/50x.html {\r\n root \/usr\/share\/nginx\/www;\r\n }\r\n \r\n # pass the PHP scripts to FastCGI server \r\n location ~ \\.php$ {\r\n fastcgi_split_path_info ^(.+\\.php)(\/.+)$;\r\n \r\n fastcgi_index index.php;\r\n include fastcgi_params;\r\n fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\r\n fastcgi_pass 192.168.0.118:9000;\r\n }\r\n}\r\n<\/pre>\nOn my Raspbian Jessie Lite reverse proxy server<\/a>, I will save this file as
\/etc\/nginx\/sites-enabled\/sf.anexistingurl.com.conf<\/strong><\/code>.<\/p>\nAfter I do so, I would restart nginx with the following command:<\/p>\n
\r\nsudo systemctl restart nginx.service\r\n<\/pre>\n
Running the install script of ProjectSend<\/h2>\n
Once you got the nginx configurations in place, you can then access
http:\/\/sf.anexistingurl.com\/install<\/code> with your browser. Complete the necessary details and click on theInstall<\/code> button:<\/p>\n![\"Accessing](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/accessing-ProjectSend-running-on-Raspbian-Jessie-Lite-from-chrome.gif\")
<\/p>\nOnce you do so, you will see the following screen:<\/p>\n
![\"Successfully](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/successfully-installed-ProjectSend-on-Raspbian-Jessie-Lite.gif\")
<\/p>\nConfiguring SSL for your ProjectSend website<\/h2>\n
With Let's Encrypt, getting an SSL certificate comes with no cost. Since we may be sharing private files with our friends, why not go further to configure SSL for our ProjectSend website?<\/p>\n
Installing CertBot on our Raspbian Jessie Lite reverse proxy server<\/h3>\n
With an ACME client like CertBot<\/a>, we will be able to automate the retrieval of SSL artefacts from Let's Encrypt. If you do not have CertBot installed on your Raspbian Jessie Lite reverse proxy server, you will need to install it first<\/a>. <\/p>\n
Configuring nginx to demonstrate control over your domain<\/h3>\n
The Let's Encrypt server will look for some random file written by Certbot at the
\/.well-known<\/code> uri path of our domain in order to be convinced that we owned the domain that we wish to secure with HTTPS.<\/p>\nTherefore, we will have to modify our nginx configuration to serve files via the
\/.well-known<\/code> uri. To do so, I will open up\/etc\/nginx\/sites-enabled\/sf.anexistingurl.com.conf<\/strong><\/code> and add the following nginx configuration block inside the server block:<\/p>\n\r\nlocation ~ \/.well-known {\r\n allow all;\r\n}\r\n<\/pre>\nThe resultant nginx configuration file will look like this:<\/p>\n
\r\nserver {\r\n listen 80;\r\n root \/var\/www\/ProjectSend-r756;\r\n index index.php index.html;\r\n \r\n server_name sf.anexistingurl.com;\r\n \r\n location \/ {\r\n # First attempt to serve request as file, then\r\n # as directory, then fall back to index.html\r\n try_files $uri $uri\/ \/index.html;\r\n }\r\n \r\n error_page 404 \/404.html;\r\n \r\n # redirect server error pages to the static page \/50x.html\r\n error_page 500 502 503 504 \/50x.html;\r\n location = \/50x.html {\r\n root \/usr\/share\/nginx\/www;\r\n }\r\n \r\n # pass the PHP scripts to FastCGI server \r\n location ~ \\.php$ {\r\n fastcgi_split_path_info ^(.+\\.php)(\/.+)$;\r\n \r\n fastcgi_index index.php;\r\n include fastcgi_params;\r\n fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\r\n fastcgi_pass 192.168.0.118:9000;\r\n }\r\n\r\n location ~ \/.well-known {\r\n allow all;\r\n }\r\n}\r\n<\/pre>\nOnce I had saved the changes made to the nginx configuration file, I restart nginx by running the following command:<\/p>\n
\r\nsudo systemctl restart nginx.service\r\n<\/pre>\n
Using Certbot to get Let's Encrypt to issue the SSL certificate for our domain<\/h3>\n
After the nginx configurations is being applied, we are ready to use Certbot to get Let's Encrypt to issue the SSL certificate for our domain. To do so, enter the following command:<\/p>\n
\r\nsudo certbot certonly --webroot -w \/var\/www\/ProjectSend-r756 -d sf.anexistingurl.com\r\n<\/pre>\n
When the command runs for the very first time on your machine, it will ask for an email address to notify when the SSL certificate is going to expire and an agreement to Let's Encrypt Terms of Service.<\/p>\n
Once we have given the necessary responses, CertBot will create the SSL artefacts inside the
\/etc\/letsencrypt\/live\/sf.anexistingurl.com<\/code> folder. Inside\/etc\/letsencrypt\/live\/sf.anexistingurl.com<\/code>, we will also find cert.pem, chain.pem, fullchain.pem and privkey.pem. The files inside\/etc\/letsencrypt\/live\/sf.anexistingurl.com<\/code> folder are symbolic links for facilitating certificate renewal without changing our server side configurations.<\/p>\nGenerating a strong Diffie-Hellman group<\/h2>\n
After the SSL certificate and the corresponding private key were created successfully, we should also precompute a strong Diffie-Hellman group for our reverse proxy server to use for exchanging cryptographic keys with its clients:<\/p>\n
\r\nsudo openssl dhparam -out \/etc\/ssl\/certs\/dhparam.pem 2048\r\n<\/pre>\n
This process will take a very long time to complete but it will be worth the effort as it would make communicating with our server more secure.<\/p>\n
Creating the nginx configurations for serving HTTPS for your ProjectSend website<\/h2>\n
Apart from enabling HTTPS communication on port 443 of our Raspbian Jessie Lite reverse proxy server, we also want any HTTP request made to port 80 to be redirected to port 443 via the HTTPS protocol. To serve such a use case, we will open up
\/etc\/nginx\/sites-enabled\/sf.anexistingurl.com.conf<\/strong><\/code> and replace the content with the following:<\/p>\n\r\n# Redirect HTTP requests to HTTPS \r\nserver {\r\n listen 80;\r\n server_name sf.anexistingurl.com;\r\n return 301 https:\/\/$host$request_uri;\r\n}\r\n \r\n# For ssl\r\nserver {\r\n ssl on;\r\n ssl_certificate \/etc\/letsencrypt\/live\/sf.anexistingurl.com\/fullchain.pem;\r\n ssl_certificate_key \/etc\/letsencrypt\/live\/sf.anexistingurl.com\/privkey.pem;\r\n ssl_protocols TLSv1 TLSv1.1 TLSv1.2;\r\n ssl_prefer_server_ciphers on;\r\n ssl_dhparam \/etc\/ssl\/certs\/dhparam.pem;\r\n ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';\r\n ssl_session_timeout 1d;\r\n ssl_session_cache shared:SSL:50m;\r\n ssl_stapling on;\r\n ssl_stapling_verify on;\r\n add_header Strict-Transport-Security max-age=15768000;\r\n \r\n default_type application\/octet-stream;\r\n \r\n listen 443;\r\n server_name sf.anexistingurl.com;\r\n \r\n root \/var\/www\/ProjectSend-r756;\r\n index index.php index.html;\r\n \r\n location \/ {\r\n # First attempt to serve request as file, then\r\n # as directory, then fall back to index.html\r\n try_files $uri $uri\/ \/index.html;\r\n }\r\n \r\n error_page 404 \/404.html;\r\n \r\n # redirect server error pages to the static page \/50x.html\r\n error_page 500 502 503 504 \/50x.html;\r\n location = \/50x.html {\r\n root \/usr\/share\/nginx\/www;\r\n }\r\n \r\n # pass the PHP scripts to FastCGI server \r\n location ~ \\.php$ {\r\n fastcgi_split_path_info ^(.+\\.php)(\/.+)$;\r\n \r\n fastcgi_index index.php;\r\n include fastcgi_params;\r\n fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\r\n fastcgi_pass 192.168.0.118:9000;\r\n }\r\n\r\n location ~ \/.well-known {\r\n allow all;\r\n }\r\n}\r\n<\/pre>\nAnd after we had saved the changes, we restart nginx with the following command:<\/p>\n
\r\nsudo systemctl restart nginx.service\r\n<\/pre>\n
Updating base uri to reflect https<\/h3>\n
Since ProjectSend saved the base uri with the protocol scheme, we need to change it in order for ProjectSend to work properly via HTTPS. To do so, we first log into our MySQL server through the MySQL client:<\/p>\n
\r\nsudo mysql -u root -p\r\n<\/pre>\n
After entering the password, we run the following SQL statement to update the base uri with
https:\/\/<\/code> as the protocol scheme:<\/p>\n\r\nmysql> UPDATE tbl_options SET value = 'https:\/\/sf.anexistingurl.com\/' WHERE name = 'base_uri';\r\n<\/pre>\n
Buying the recommended hardware list to setup your own ProjectSend website with Raspbian Jessie Lite<\/h2>\n
If you do not have the Raspberry Pi 3 hardware mentioned in this post yet, you may want to purchase them from Amazon. Simply click on the button below to add the Raspberry Pi 3 hardware to your cart. You may remove anything that you already have or replace some of the hardware with other hardware.<\/p>\n
<\/p>\n - Raspberry PI 3 Model B A1.2GHz 64-bit quad-core ARMv8 CPU, 1GB RAM<\/a><\/li>\n