How To Solve Issues Related to Log – Got successful response from URL

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Jan-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Got successful response from URL” it’s important to understand common problems related to Elasticsearch concepts: response. See detailed explanations below complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 ElasticSearch.NET NEST search url 4.37 K 6

2Unable To Launch Logstash And Inges  


Log Context

Log ”Got successful response [{}] from URL [{}]” classname is WaitForHttpResource.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

         try {
            final HttpURLConnection connection = buildConnection(ssl);
            connection.connect();
            final Integer response = connection.getResponseCode();
            if (validResponseCodes.contains(response)) {
                logger.info("Got successful response [{}] from URL [{}]"; response; url);
                return;
            } else {
                throw new IOException(response + " " + connection.getResponseMessage());
            }
        } catch (IOException e) {






About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster