This commit is contained in:
2021-12-10 20:49:14 +00:00
parent 4c7719db61
commit 44dabd0122

View File

@@ -274,7 +274,9 @@ A static IP address is **required** to host AyaNova on the internet. If you have
##### Registered domain name
An internet domain name is required to get an SSL certificate for secure encrypted communications between the AyaNova server and the end user across the internet. An entry will need to be made in your DNS record for your domain to provide a name to access the AyaNova server and it must point to the static IP address of your router or server. If the only service on your domain will be AyaNova then you can use the root domain name i.e. `example.com` or `www.example.com` but it's more common to use a subdomain specifically for AyaNova, i.e. `ayanova.example.com`. This DNS record needs to be in place and active **before** proceeding and can take minutes to hours to propagate so be sure to do this as soon as possible.
An internet domain name is required to get an SSL certificate for secure encrypted communications between the AyaNova server and the end user across the internet. An entry will need to be made in your DNS record for your domain to provide a name to access the AyaNova server and it must point to the static IP address of your router or server. If the only service on your domain will be AyaNova then you can use the root domain name i.e. `example.com` or `www.example.com` but it's more common to use a subdomain specifically for AyaNova, i.e. `ayanova.example.com`.
This DNS record needs to be in place and active **before** proceeding and can take minutes to hours to propagate so be sure to do this as soon as possible.
##### SSL certificate
@@ -367,7 +369,40 @@ Make a backup copy of the existing `default` config file to your HOME folder jus
cp /etc/nginx/sites-enabled/default ~/nginx-default-backup
```
Open the existing `default` config file in an editor, replace it's contents **entirely** with the following configuration and save:
```
server {
listen 80;
location / {
proxy_pass http://127.0.0.1:7575;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
```
In a later step the Lets Encrypt Certbot will automatically update this file with the correct settings for ongoing use, this is only the initial configuration to allow Lets Encrypt access.
Confirm that NGINX sees the configuration as valid:
```bash
sudo nginx -t
```
Restart NGINX so the new configuration takes effect:
```bash
sudo systemctl restart nginx
```
#### Confirm DNS is active
Confirm that you can now navigate to AyaNova web app login page through regular un-encrypted HTTP via the domain name configured earlier. i.e. `http://ayanova.yourdomain.com` or `http://yourdomain.com` if not using a subdomain.
### Login to AyaNova web app