It is up to you, you can continue this thread, or start new thread or write email to email@example.com to continue the conversation. Whichever suites you the best.
For the ERROR_WINHTTP_REDIRECT_FAILED:
I am not sure what exactly this can mean. However, I have two ideas:
1. You used wrong/invalid certificate on proxy server and the client connecting to the proxy cannot validate the certificate successfully.
The reason can be same as the previous issue = "common name does not match the hostname". However, now the client is complaining.
To fix this, the certificate used at the proxy, must be issued for hostname you are using on the client to connect to the proxy.
If you are using IP address instead of hostname, the certificate must be issued for that IP address, but it depends on the client,
whether it will validate such certificate successfully. If I am correct, e.g. Google Chrome will not validate such certificate successfully.
2. The PBX server uses its certificate to sign data (or part of it) which are sent to the client (e.g. signed SOAP works like this).
The client tries to verify the signature, but it has two different certificates. One from TLS layer and the second from signed content.
This can result to ERROR_WINHTTP_REDIRECT_FAILED.
To fix this, you have to use the exact same certificate on the proxy and PBX server.
Yes, there is level above Debug. Either execute "tlsproxy run --verbose"
Or maybe more useful is to set up a file logging in the config:
global: # Global logger (troubleshooting for debugging purposes)
Again, please see config-sample.yaml file for more details.