title: JMeter 1 user Response code: Non HTTP response code: java.net.ConnectionException Response message: Non HTTP response
body: <p>I'm trying to learn load testing with JMeter(Very new). Using the tutorial to Build a Web Test Plan on the JMeter website and another youtube tutorial, I created an HTTP GET request to hit www.google.com/ but I get the following result:</p>
  
  <pre><code>    Thread Name: Thread Group 1-1
      Sample Start: 2018-07-16 12:44:09 CDT
      Load time: 64018
      Connect Time: 64018
      Latency: 0
      Size in bytes: 2390
      Sent bytes:0
      Headers size in bytes: 0
      Body size in bytes: 2390
      Sample Count: 1
      Error Count: 1
      Data type ("text"|"bin"|""): text
      Response code: Non HTTP response code: java.net.ConnectException
      Response message: Non HTTP response message: Connection timed out: connect
  </code></pre>
  
  <p>Here's my request:
  <a href="https://i.stack.imgur.com/E067U.png" rel="nofollow noreferrer">link to image since I don't have 10 reputation yet</a></p>
  
  <p>Looking around other people are getting this issue but their issue is after 250+ users: <a href="https://stackoverflow.com/questions/39507765/response-code-non-http-response-code-java-net-connectexception-response-messag">Response code: Non HTTP response code: java.net.ConnectException Response message: Non HTTP response message: Connection timed out: connect</a></p>
  
  <p>However, I'm only trying to use one user and one thread, and I couldn't find anyone having the same error with only one user.</p>
  
  <p>I set the Client implementation to HttpClient4 like the second answer suggests from <a href="https://stackoverflow.com/questions/42388993/jmeter-non-http-response-code-java-net-connectexception">jmeter Non HTTP response code: java.net.ConnectException</a> but I still get the same issue.</p>
  
  <p>Thanks in advance!</p>
  
  <p><strong>Answer</strong> Turns out it was because of our proxy server. Which was strange because I'm able to send request via postman and get responses. But I switched to a computer not on the proxy and everything is working now.</p>