ProxymanApp / ProxymanApp/Proxyman
Failed to intercept connections from kubectl command
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
I want to intercept traffic generated by kubectl command but Proxyman doesn't work.
Steps to Reproduce
- Intercept HTTPS traffic of
kubectlcommand by addingkubectlapp in Tools -> SSL Proxying List -> Include List. - Add client certificate and client key file in Certificate -> Add Custom Certificate.
- Enable SOCKS Proxy in Proxyman.
- Set
HTTPS_PROXYenvironment variable in terminal. - Run command
kubectl --insecure-skip-tls-verify=true get pods.
Current Behavior
kubectl command retries all the time.
BTW, if I edit and repeat the request, Proxyman fails with invalid host.
Expected Behavior
kubectl command works as usual.
Environment
- App version: 4.15.0 (49600)
- macOS version: 14.1.2 (23B92)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the kubectl request through Proxyman's SOCKS Proxy with HTTPS_PROXY, the SSL Proxying Include List, and the custom certificate settings described. Investigate why kubectl retries and why an edited request produces "invalid host"; done means kubectl --insecure-skip-tls-verify=true get pods works normally through the proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100