I've created a simple passthrough proxy and associated with a virtual host and consistently get a 404. The proxy works as expected when using the default secure host.
We’ve:
Any help is greatly appreciated.
Solved! Go to Solution.
You could also try invoking your API using curl with the -v option. This will show info about the certificate being presented. See if it matches the certificate you associated with the new virtual host.
I've seen that sometimes there is a problem when creating the virtual host, and all API requests are routed to an existing virtual host (eg: secure), if your proxy is not listening on that old virtual host, you'l get the 404 message