Hi, I'm trying to obfuscate calls to the vapi api but running through an SSL Reverse Proxy in IIS. I would like to get some suggestions on how to get it going and the technical requirements. My early experiments simple stated the request was blocked on the Vapi end. I also noticed on the Vapi GitHub site there was a project called node-http-proxy and wondering if that was the purpose of the project.

@Craig Richards Hello! Setting up an SSL Reverse Proxy in IIS to obfuscate calls to the VAPI API is a great way to enhance security. Here are some general steps and technical requirements to get you started: 1. **SSL Certificate**: Ensure you have a valid SSL certificate installed on your IIS server to establish a secure connection. 2. **IIS Configuration**: Configure IIS to act as a reverse proxy. You'll need to install the URL Rewrite and Application Request Routing modules in IIS to enable reverse proxy functionality. 3. **URL Rewrite Rules**: Create URL rewrite rules to forward requests from your IIS server to the VAPI endpoint. Make sure to rewrite the HTTPS header to ensure that VAPI recognizes the request as secure. 4. **Firewall and Network Settings**: Adjust your firewall and network settings to allow traffic from your IIS server to the VAPI servers. Ensure that no rules are blocking the outgoing requests. 5. **Testing**: After setting up the reverse proxy, test the setup thoroughly to ensure that requests are correctly forwarded and responses are received. Regarding the

node-http-proxy

project you mentioned, it is a Node.js package that can create a proxy server or be used within another Node.js application to forward requests to a different server, which could be useful in a development environment. However, it is not specifically related to VAPI. If you're encountering issues where requests are blocked on the VAPI end, it could be due to several reasons, such as incorrect proxy configuration, SSL/TLS issues, or VAPI's security measures. It's important to check the logs and error messages for more details. If you need further assistance with the specific error messages or configurations, please provide more details, and I'll be happy to help you troubleshoot the issue. If the problem persists, you may need to reach out to VAPI support for more information on their end.

The site is certainly bound to a valid certificate and this is the web.config setting I am using. https://cdn.discordapp.com/attachments/1291682337133690922/1291689252643541042/web.config?ex=670102dc&is=66ffb15c&hm=2f2f2ed41a40bd5a31206c7f51291d8b17d915725438e747213e5a7246d1f7a8&

@Craig Richards what i have understood is you want to use proxy for the call requests.

const vapi = new Vapi('your-public-key', https://api.example.com/voice);

this would hit your API that you proxy to us.

Yes that is correct, right now I have configured IIS to reverse proxy to your servers but am getting blocked and want to understand what to do. I can provide my IIS Config for the reverse proxy or looking for other suggestions.

@Craig Richards can connect directly to the vapi server from IIS server? such as using curl?

I'm sorry i missed this. When is the next session? Of the same IIS Server using another application i can connect with no issues.

@Craig Richards can you DM me, we will connect over the call and resolve it.