Capture client not using HTTPS #2816
-
|
Hey everyone, I’m running into an issue with the Capture client app. When set up an infrastructure Server URL to use https, https://:59232, I get the following error: Secure Connection Failed From what I can tell this usually means the service on that port isn’t speaking HTTPS/TLS. Does Capture expose only HTTP on its port, and if so what’s the right way to access it? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Hi @cschwarck Yes, Capture only uses the configured port for HTTP. There is an open issue for supporting SSL in capture repository. We studied this issue and decided that instead of changing the server-side operation, a better option would be to use Capture with a reverse proxy like Nginx, Traefik etc. As I know we don't have any running demo, but we will update the documentation for using Capture with reverse proxy and HTTPS. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Hello. I created a sample usage with SSL with caddy. I choose caddy because it's soo simple. |
Beta Was this translation helpful? Give feedback.
Hi @cschwarck
Yes, Capture only uses the configured port for HTTP. There is an open issue for supporting SSL in capture repository. We studied this issue and decided that instead of changing the server-side operation, a better option would be to use Capture with a reverse proxy like Nginx, Traefik etc.
As I know we don't have any running demo, but we will update the documentation for using Capture with reverse proxy and HTTPS.
( Probably with Nginx, to sync with checkmate's configuration )