- Getting Started
-
Administration Guide
-
Get Started with Administering Wyn Enterprise
- System Requirements
- Installing on Windows
- Installing on Linux
- Installing using Docker
- License Wyn Enterprise
- Deploying with HTTPS
- Deploying with Reverse Proxy
- Deploying to Azure App Service
- Deploying to Azure Kubernetes Service
- Deploying to Local Kubernetes
- Deploying as a Virtual Directory or Sub-Application
- Deploying in a Distributed Environment
- Migration from ActiveReports Server 12
- Upgrade Wyn Enterprise to Latest Version
- Logging on to the Administrator Portal
- Ports in Firewall
- Configuration Settings
- Account Management
- Security Management
- System Management
- Document Management
- How To and Troubleshooting
-
Get Started with Administering Wyn Enterprise
- User Guide
- Developer Guide
Using Nginx as Reverse Proxy
This article describes the HTTPS configuration steps to use Nginx as a reverse proxy to deploy Wyn Enterprise with HTTPS. However, the primary objective of this article is to configure the reverse proxy to map a public URL to the internal server in the reverse proxy.
For this, you need to expose two web applications to the internet when you publish Wyn Enterprise. These web applications are identity services and portals. Also, you must have your own domain name, for example, *.grapecitydev.com, and its associated SSL certificates.
Deploy Wyn Enterprise with HTTPS
The following steps describe the steps to use Nginx on Ubuntu 16.04 as a reverse proxy for deploying Wyn Enterprise with HTTPS.
Install Nginx using the following command.
sudo apt-get update sudo apt-get install nginx
Create the domain name for the portal that you have purchased and then map the domain name to your server's DNS or host IP. For example,
portal.grapecitydev.com.
Put your SSL certificates on the server.
Setup the reverse proxy with HTTPS in the Nginx configuration file. The configuration file of Nginx locates in '/etc/nginx/sites-available' and the name is "default".
Use the following command to open the configuration file in the text editor.
sudo vi /etc/nginx/sites-available/default
Modify the configuration file and update the details regarding the SSL certificates and application as shown in the below sample file.
server { listen 443; ssl on; ssl_certificate /etc/ssl/grapecitydev_chain.crt; ssl_certificate_key /etc/ssl/grapecitydev.key; server_name portal.grapecitydev.com; large_client_header_buffers 4 32k; location / { proxy_pass http://localhost:51980; 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_connect_timeout 60s; proxy_send_timeout 60s; proxy_read_timeout 60s; send_timeout 60s; sendfile on; proxy_buffer_size 64k; proxy_buffers 32 32k; proxy_busy_buffers_size 128k; fastcgi_buffers 8 16k; fastcgi_buffer_size 32k; client_max_body_size 8M; } }
Restart the Nginx using the below command.
sudo service nginx restart
If you use "server" authentication (identity server provider is "server"), there is no need to modify the Wyn configuration file.
Note that the configuration file in Linux is located here - /opt/Wyn/Monitor/conf/Wyn.conf.
Note: Since HTTPS uses port 443 by default, you need to add the inbound rule in the firewall to allow the 443 port to be accessed remotely.