All channels interplaying with external sources demand that XCALLY server is reachable from the web on the 443 port (https).
...
You just need to create more A records in your DNS and add “server” sections in the NGINX set up file, as follows.
For example:
Record A = proxy1.mydomain.com will forward to myxcallyserver1.mydomain.com
Record A = proxy2.mydomain.com will forward to myxcallyserver2.mydomain.com
Code Block |
---|
# multi-server configuration. # You can add these sections for all your XCALLY servers by changing the server_name server { listen 80; server_name proxy1.mydomain.com; return 301 https://$server_name$request_uri; } server { listen 443 ssl; server_name proxy1.mydomain.com; ssl_certificate /etc/ssl/certs/mydomain_com.crt; ssl_certificate_key /etc/ssl/private/mydomain_com.key; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Real-Port $remote_port; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; location / { if ($request_uri = '/') { return 403; } proxy_pass https://myxcallyserver1.mydomain.com; } } |
...
Code Block |
---|
systemctl restart nginx |
Note |
---|
Consider that customers must modify the configuration on Motion environment, by inserting the reference to the created Reverse Proxy. |