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. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

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




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content