How To Solve Issues Related to Log – 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 Issues Related to Log – The specified url doesnt start with any repository paths specified by the path.repo setting: or by repositories.url.allowed-urls setting:

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “The specified url doesnt start with any repository paths specified by the path.repo setting: or by repositories.url.allowed-urls setting:” it’s important to understand a few problems related to Elasticsearch concepts repositories, repository-azure. See bellow important tips and explanations on these concepts

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;
            }
        }




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Location Doesnt Match Any Of The Lo  

Path Repo Is Empty  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now