The specified url doesnt start with any repository paths specified by the path.repo setting: or by repositories.url.allowed-urls setting: – How to solve related issues

The specified url doesnt start with any repository paths specified by the path.repo setting: or by repositories.url.allowed-urls setting: – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” The specified url doesnt start with any repository paths specified by the path.repo setting: or by repositories.url.allowed-urls setting: ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: repositories and repository-azure.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “The specified url [{}] doesn’t start with any repository paths specified by the path.repo setting: [{}] or by repositories.url.allowed_urls setting: [{}]” classname is URLRepository.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     throw new RepositoryException(repositoryName; "cannot parse the specified url [" + url + "]");
                }
                // We didn't match white list - try to resolve against path.repo
                URL normalizedUrl = environment.resolveRepoURL(url);
                if (normalizedUrl == null) {
                    logger.warn("The specified url [{}] doesn't start with any repository paths specified by the path.repo setting: [{}] or by repositories.url.allowed_urls setting: [{}] "; url; environment.repoFiles());
                    throw new RepositoryException(repositoryName; "file url [" + url + "] doesn't match any of the locations specified by path.repo or repositories.url.allowed_urls");
                }
                return normalizedUrl;
            }
        }




 

Run the Check-Up to get customized recommendations like this:

checklist Run Check-Up

error

Heavy merges detected in specific nodes

error-img

Description

A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…

error-img

Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized code snippet to resolve the issue]

 

 

 

Optimize Elasticsearch Performance

Run The Tool