Briefly, this error occurs when Elasticsearch tries to access a repository URL that is not allowed by the path.repo setting or repositories.url.allowed_urls setting. This could be due to incorrect configuration or a typo in the URL. To resolve this issue, you can: 1) Check and correct the repository URL in your request; 2) Update the path.repo setting in elasticsearch.yml to include the correct path; 3) Add the repository URL to the repositories.url.allowed_urls setting in elasticsearch.yml. Always remember to restart Elasticsearch after making changes to the configuration file.
This guide will help you check for common problems that cause the log ” The specified url [{}] doesn’t 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.
Overview
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported:
Repository types
| Repository type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “gcs” |
Examples
To register an “fs” repository:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}Notes and good things to know
- S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
- The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
- When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
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;
}
}
