For the proper configuration of the chatbot, we need to provide https link pointing to our deployed application on the customer’s side. A reverse proxy solution would be suitable in this case. In the provided example we used nginx software. Please be aware that the domain name should be registered and assigned to the proper server IP address. Below you can find a screen from sample nginx reverse-proxy configuration.
server {
listen 443;
server_name <example DNS entry>;
ssl on;
ssl_dhparam <example-path>/dhparam.pem;
ssl_certificate <example-path>/<example-cert>.crt;
ssl_certificate_key <example-path>/<example-key>.key;
ssl_protocols TLSv1.2 TLSv1.1 TLSv1;
ssl_prefer_server_ciphers on;
ssl_session_timeout 5m;
location / {
proxy_set_header Host $host;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://localhost:<example-port>;
}
# Websocket support
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
}
server_name should be reserved DNS entry.
proxy_pass pointing onto the port which is specified by docker command when starting the container.
Table with default port assignment
| Port Description | Internal Port (inside container) | Assigned port (if available) |
| node.js app of Conversational Actions Connector | 8000 | 8000 |
| Web-socket server of Conversational Actions Connector (maintain speech-to-text recognition from Hybrid Chats) | 8001 | 8001 |
| www.skybuffer.com |