Feedbacky
Search…
Domain Setup
Use your own domain with Feedbacky.

Record

Before going into details, you must have your server pointed to your domain.
1. Access the DNS settings of your domain provider.
2. Create an A Record.
3. Find your public IP address.
1
curl ipinfo.io/ip
Copied!
4. Insert a subdomain, for example; feedbacky.
5. Put your public IP address in the address field.

Port Forwarding

Your webserver also needs to be accessible over the internet.
1. Forward port 80.
1
sudo ufw allow 80/tcp
Copied!
2. Forward port 443.
1
sudo ufw allow 443/tcp
Copied!

Virtual Hosts

Creating

Virtual Hosts enables you to run multiple website on a single webserver, this is useful if you are also hosting other services such as a store front, documentation site, etc..
1. Access your webserver's Virtual Host directory.
Apache
Nginx
1
cd /etc/apache2/sites-available
Copied!
1
cd /etc/nginx/sites-available
Copied!
2. Create a new file with the name being your domain, the file name must end with ".conf".
1
sudo nano {feedbacky.yourdomain}.conf
Copied!
{feedbacky.yourdomain}.conf
Your domain including the subdomain, example; feedbacky.myapp.conf.
3. Paste the following content to your newly created Virtual Host file.
Apache
Nginx
{feedbacky.yourdomain}.conf
1
<VirtualHost *:80>
2
ServerName {DOMAIN_NAME}
3
</VirtualHost>
4
5
# Comment out (Adding #) to the part below if you don't plan on using SSL!
6
<VirtualHost *:443>
7
ServerName {DOMAIN_NAME}
8
RewriteEngine On
9
RewriteCond %{HTTPS} !=on
10
RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]
11
SSLEngine on
12
SSLCertificateFile /etc/letsencrypt/live/{DOMAIN_NAME}/fullchain.pem
13
SSLCertificateKeyFile /etc/letsencrypt/live/{DOMAIN_NAME}/privkey.pem
14
</VirtualHost>
Copied!
{feedbacky.yourdomain}.conf
1
server {
2
listen 80;
3
server_name {DOMAIN_NAME};
4
5
return 301 https://$host$request_uri;
6
}
7
8
# Comment out (Adding #) to the part below if you don't plan on using SSL!
9
server {
10
listen 443 ssl http2;
11
server_name {DOMAIN_NAME};
12
13
ssl_certificate /etc/letsencrypt/live/{DOMAIN_NAME}/fullchain.pem;
14
ssl_certificate_key /etc/letsencrypt/live/{DOMAIN_NAME}/privkey.pem;
15
ssl_session_cache shared:SSL:10m;
16
ssl_protocols TLSv1.2 TLSv1.3;
17
ssl_ciphers "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES2>-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384";
18
ssl_prefer_server_ciphers on;
19
20
http2_idle_timeout 5m; # up from 3m default
21
client_max_body_size 0;
22
23
location / {
24
proxy_pass {SERVER_IP}:{CLIENT_APP_PORT};
25
}
26
}
Copied!
{DOMAIN_NAME}
Your fully qualified domain domain, example; feedbacky.app.cool.
{SERVER_IP} (Nginx)
The IP address (not public) of your Virtual Private Server (VPS) or dedicated hardware.
{CLIENT_APP_PORT}(Nginx)
The client port located in your .env file, by default it is 8090.
4. Save the file with CTRL + S and exit nano with CTRL + C.

Additional steps

Apache
Nginx
5. By default proxy and ssl are disabled in Apache, enable them.
1
sudo a2enmod proxy ssl
Copied!
Breakdown
To understand what this command does, we can break it down like this,
  • a2 means apache2
  • en means enable
  • mod means module
We are asking Apache to enable the proxy module which is located in the/etc/apache2/available-modules directory.
5. A symbolic link (symlink) must be created for making your Virtual Host work.
1
sudo ln -s /etc/nginx/sites-available/{DOMAIN_NAME}.conf /etc/nginx/sites-enabled/{DOMAIN_NAME}.conf
Copied!
Breakdown
Each time you will edit your Virtual Host located in /etc/nginx/sites-available it will also update the one created in /etc/nginx/sites-enabled.

Enabling

Apache
Nginx
1
sudo a2ensite {feedbacky.yourdomain}.conf
Copied!
1
sudo service nginx reload
Copied!

Generating a Certificate

Generate your domain SSL certificate.
Apache
Nginx
1
sudo certbot certonly --apache -d {DOMAIN_NAME}
Copied!
1
sudo certbot certonly --nginx -d {DOMAIN_NAME}
Copied!
Standalone
If neither the Apache nor the Nginx command worked, try using the standalone command.
1
sudo certbot certonly --standalone -d {DOMAIN_NAME}
Copied!
If everything went well, you should now have your own self-signed certificate for your domain.

Let's Encrypt Alternative

Cloudflare

An alternative method that you can follow instead of manually generating a certificate and adding additional values to your Virtual Host file is by using Cloudflare.
In short by adding your website to Cloudflare, you will be able to forward your board with Cloudflare's own proxy.
You can read more here.
The normal domain setup without SSL is still required!