Connectivity to Slack without using Ngrok

I want to integrate my RASA bot with slack’s desktop version. I want to do this without using ngrok since it is a security concern. Please suggest the alternatives to this.

Hi @gurpreetbajwa! Depending on your exact security concerns with ngrok, another option would be to deploy it on a server. I just deployed a rasa bot on a Google Cloud Compute Engine VM using the slack connector a few weeks ago, so I could definitely help with that if you want to go this route. Let me know! Otherwise, if you could please elaborate a bit more on your security concerns with ngrok and perhaps what your ideal solution to those concerns would need to be, that would help us to be able to answer your question

You could also check out Inlets. Perhaps that might also be an alternative to ngrok

Hi @tyd,

I am also currently running a rasa bot on Google Cloud Compute Engine VM, however cannot connect it to Slack (specially cannot proceed with url verification). Would you mind helping me with my problem?

Hi @mia.le0711. Sure, happy to help. Are you able to chat with it using share your bot or the rest channel?

Thank you @tyd. I deployed Rasa Open Source only, I didn’t apply Rasa X!

@mia.le0711 No worries. There is not a difference for channels, other than we won’t be able to use the share your bot channel to help us debug the problem. Is the rest channel working?

@tyd Can you please help me running the RASA X on Windows Server. For so long i was running RASAX on local machine using ngrok but now the issue is, ngrok expires in 7 hours and i need the chatbot running 24*7. Please help.

Hi @nayakpraneet. I would recommend using Multipass to deploy Rasa X to a windows server.

@tyd When I try to run multipass using Oracle Virtual Box I get this error

C:\Users\AIadmin>multipass launch --name k3s --mem 4G --disk 50G launch failed: Could not start VM: Waiting for VM “k3s” to power on… VBoxManage.exe: error: UUID {643b3289-7d4d-4f65-a03c-87f8c3503902} of the medium ‘C:\windows\system32\config\systemprofile\AppData\Roaming\multipassd\virtualbox\vault\instances\k3s\ubuntu-20.04-server-cloudimg-amd64.vdi’ does not match the value {a95ceaf5-8582-46cb-90dc-f5bbc6c7b68d} stored in the media registry (‘C:\windows\system32\config\systemprofile.VirtualBox\VirtualBox.xml’) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MediumWrap, interface IMedium

@tyd And when i use Hyper-V instead of Virtual Box, I get this error

C:\Users\AIadmin>multipass set local.driver=hyperv

C:\Users\AIadmin>multipass launch --name k3s --mem 4G --disk 50G launch failed: The Hyper-V Hypervisor is disabled. Please enable by using the following command in an Administrator Powershell and reboot: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor

@tyd I am using Windows Server 2019, Is that an issue? I read Multipass doesnt support Windows Server?

@nayakpraneet I am not super familiar with windows server. Maybe something like " then you can export this virtual machine from Windows 10 to your Windows 2012 R2 server" helps?

Hi, I have an issue with connecting slack to RASA. After a fair chunk of rasa docs and googling I can’t find the reason why this fails. I have a setup on an LXC cluster with Haproxy on the front with letsEncrypt cert. 443 working fine and I can curl the bot on the /webhooks/rest/webhook and getting a correct reply from the model - great.

external domain with cert bot SSL → RT → host (HA proxy) > LXC > HA cluster (bot is part of it) *feel free to pop me a line if you hit a wall with a similar setup.

However when I try to connect slack and try /webhooks/slack/webhook I get a fail `Your URL didn’t respond with the value of the challenge parameter’

if I try the /webhooks/rest/webhook I get: `Our Request: POST “body”: { “type”: “url_verification”, “token”: “”, “challenge”: “” } Your Response: “code”: “error”: “challenge_failed” “body”: {


NOTE: For all those who are amazed by RASA documentation…it was a lot lot worse back in the early days. In my case it was as simple as uncommenting the #slack part in credentials.yml and the token values below …

PS. I also came across that previous versions had https://host:port/core/webhooks/slack/webhook perhaps it will help others

Cheers, Peter