Site default status error not allow create email for it

Доброго дня

потребовалось настроить HTTPS соединения, но возникает следующий трабл, помогите пожалуйста:
1. Bitrix virtual appliance version 7.3.3
стандартным способом иду в меню
6. Manage sites in the pool потом в пункт меню 5. Manage http/https settings
выбираю сайт и далее ошибка: not allow manage ssl settings for it

в чем может быть ошибка, заранее благодарю вас за помощь.

Enter site name (default) or 0 to exit: sitename.ru

HTTP and HTTPS are enabled for the site sitename.ru

Do you want to disable HTTP access for the site sitename.ru? (Y|n): Y

Command returned error — Site sitename.ru status=error, not allow manage ssl settings for it

Пользователь 180446 Эксперт Сообщений: 684 Баллов: 92 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 11.04.2013	В первую очередь загляни в логи задачи /opt/webdir/temp

Пользователь 3033513

Заглянувший

Сообщений: 16
Авторитет:

0
Рейтинг пользователя:

0
Регистрация: 21.03.2019

27.03.2019 17:26:14

Цитата
Александр Медведев написал: В первую очередь загляни в логи задачи /opt/webdir/temp

в этой папке все файлы старые, я сегодня пытался настроить, у них даты старые

Прикрепленные файлы

Снимок экрана 2019-03-27 в 17.25.30.png (31.79 КБ)

	может это из той темы [2019-03-27 13:49:18] 1359 CODE_00 «bxSite::nginx_config_options: not found cluster config, set default options for site»

Алексей Шафранский

Администратор

Сообщений: 1019
Баллов: 198
Авторитет:

1
Рейтинг пользователя:

1
Регистрация: 28.07.2008

28.03.2019 12:12:41

Цитата
Иван Распринов написал: Command returned error — Site sitename.ru status=error, not allow manage ssl settings for it

Иван Распринов, с вашим сайтом что-то не так) Проверка статуса для него возвращает ошибки, поэтому дальнейшие операции заблокированы (ssl, cron и т.д.).

	а что может быть не так, и там не на Битриксе сайт, я просто страница html это что, имеет значение содержимое? все работает, если принудительно прописать https в УРЛ сайт отдается по этому протоколу

Пользователь 180446 Эксперт Сообщений: 684 Баллов: 92 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 11.04.2013	Что конкретно ты хочешь настроить?

	чтобы сайт только на протоколе https работал, по умолчанию его сделать

Пользователь 180446 Эксперт Сообщений: 684 Баллов: 92 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 11.04.2013	Создай в корне файл .htsecure

Пользователь 3033513

Заглянувший

Сообщений: 16
Авторитет:

0
Рейтинг пользователя:

0
Регистрация: 21.03.2019

#10

28.03.2019 15:19:18

Цитата
Александр Медведев написал: Создай в корне файл .htsecure

и?

Пользователь 180446 Эксперт Сообщений: 684 Баллов: 92 Авторитет: 1 Рейтинг пользователя: 0 Регистрация: 11.04.2013	#11 0 28.03.2019 16:22:12

	#12 0 28.03.2019 16:44:14 Сэр, моя благодарность вам не знает границ) Огромнейшее спасибо и хорошего дня и остальных дней)

Пользователь 971817

Заглянувший

Сообщений: 1
Авторитет:

1
Рейтинг пользователя:

0
Регистрация: 21.05.2017

#13

28.08.2022 08:42:08

Цитата
написал: Создай в корне файл .htsecure

Спасибо большое!
Создал пустой файл, теперь сайт работает по HTTPS

Источник

Проверяем настройки почтового события веб-формы и связанные шаблоны

Давайте перейдем по пути Панель управления -> Настройки -> Настройки продукта -> Почтовые события и выберем событие.

1. На первой вкладке галочки кодов языка включены?
2. На вкладке «Шаблоны» галочка имени сайта включена?
3. Почтовый шаблон активен?
4. Поле «От кого» заполнено верно (по умолчанию #DEFAULT_EMAIL_FROM#) ?
5. Поле «Кому» заполнено верно (по умолчанию #EMAIL#) ?

Все верно? Смотрим дальше. В настройках модуля веб-формы отключите галочку «использовать упрощенный режим». Перейдите в настройки формы на вкладку «дополнительно» и проверьте, включен ли флаг привязки к почтовому шаблону. Готово?

Перейдите по адресу Настройки -> Инструменты -> SQL-запрос и выполните такой запрос:

SQL:

select * from b_event where event_name like '%form%' order by date_insert desc

Найдя событие выполнения формы, просмотрите поле SUCCESS_EXEC. Если видите «Y», то письмо из продукта ушло, и вам следует отправить запрос в техподдержку хостинга. Если видите «N», то перейдите в файл

/bitrix/php_interface/dbconn.php

и проверьте, определены ли 2 переменные: BX_CRONTAB и BX_CRONTAB_SUPPORT. Если да, то отмените определение.

Повторите SQL-запрос и снова просмотрите поле SUCCESS_EXEC. Если снова видите «N», очистите кэш в папке /bitrix/managed_cache/ через модуль управления структурой. Ни в коем случае ни через FTP! Если модуль выдаст ошибку, исправьте права доступа к папкам.

Если же значение «F», то функция mail() вернула значение False при отправке. Почему так бывает:

1. Не настроена функция mail() на хостинге. Обратитесь в техподдержку хостера.
2. Почтовый сервер не поддерживает формат письма.
Попробуйте изменять настройки отправки, убирать поле ВСС, убирать галочку «Дублировать email адрес в заголовке», ставить «Конвертировать 8-битные заголовки». Если не поможет, запросите у администратора логи почтового сервера.
Наконец, если в поле «0», вернитесь к началу, настройкам почтовых событий, и проверьте заново.
источник

Источник

Установка сертификата Let’s encrypt

В меню Bitrix virtual appliance перейдите в пункт
8. Manage pool web servers → 3. Configure certificates

Выбрать пункт меню 1. Configure «Let’s encrypt» certificate и ввести:

site name – имя сайта или несколько имен сайтов, для которых нужно выпустить сертификат(ы) Let’s encrypt (в данном примере: test2.b24test.site)
dns name(s) – все домены данного сайта, для которых должен быть выпущен сертификат, включая домен с www и без, вводить несколько доменов через запятую
email for LE notifications – почтовый адрес для уведомлений сервиса Lets Encrypt

и подтвердить ввод:

Мастер самостоятельно запросит и установит сертификат в течение нескольких минут. Пути SSL-сертификатов будут указаны в этом же разделе:

Проверить выпущенный сертификат можно легко – перейти на ваш сайт по протоколу https, у валидного сертификата будет замочек.

Срок действия сертификата – 90 дней. Перевыпуск сертификата происходит автоматически за 20 дней до окончания срока его действия.

Ручное обновление сертификата

С версии BitrixVM 7.4.0 проверка сертификатов автоматически производится еженедельно в субботу в 2 часа ночи по cron-у.

Если вам нужно вручную обновить сертификат, запустите получение сертификата для существующего домена. Система проверит и при необходимости обновит сертификаты.

Также вы можете вручную обновить сертификаты командой:

/home/bitrix/dehydrated/dehydrated -c

Система проверит сроки действия сертификатов и при необходимости запустит обновление.

Лог обновления сертификатов можно посмотреть по пути: /home/bitrix/dehydrated_update.log.

Внимание.
У сервиса Lets Encrypt есть свои ограничения на выпуск сертификатов. Основные из них:

Выпуск 50 сертификатов в неделю на домены (на зарегистрированные домены у регистратора, поддомены не входят в этот счет).
Если у вас много поддоменов, то можно все поддомены указать в одном сертификате, но здесь есть лимит в 100 поддоменов в одном сертификате.
5 ошибок в час выпуска сертификата на аккаунт для одного домена (не доступен хост, не прописаны записи в DNS домена и т.д).
Проверка HTTP-01 выполняется только с использованием порта 80. Если этот порт закрыт (провайдером, например), то сертификат не перевыпустится.

Источник

HTTP response status codes indicate whether a specific HTTP request has been successfully completed.
Responses are grouped in five classes:

Informational responses (100 – 199)
Successful responses (200 – 299)
Redirection messages (300 – 399)
Client error responses (400 – 499)
Server error responses (500 – 599)

The status codes listed below are defined by RFC 9110.

Note: If you receive a response that is not in this list, it is a non-standard response, possibly custom to the server’s software.

Information responses

100 Continue: This interim response indicates that the client should continue the request or ignore the response if the request is already finished.
101 Switching Protocols: This code is sent in response to an Upgrade request header from the client and indicates the protocol the server is switching to.
102 Processing (WebDAV): This code indicates that the server has received and is processing the request, but no response is available yet.
103 Early Hints: This status code is primarily intended to be used with the Link header, letting the user agent start preloading resources while the server prepares a response.

Successful responses

200 OK

The request succeeded. The result meaning of «success» depends on the HTTP method:

GET: The resource has been fetched and transmitted in the message body.
HEAD: The representation headers are included in the response without any message body.
PUT or POST: The resource describing the result of the action is transmitted in the message body.
TRACE: The message body contains the request message as received by the server.

201 Created

The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests.

202 Accepted

The request has been received but not yet acted upon.
It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request.
It is intended for cases where another process or server handles the request, or for batch processing.

This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy.
This is mostly used for mirrors or backups of another resource.
Except for that specific case, the 200 OK response is preferred to this status.

204 No Content

There is no content to send for this request, but the headers may be useful.
The user agent may update its cached headers for this resource with the new ones.

205 Reset Content

Tells the user agent to reset the document which sent this request.

206 Partial Content

This response code is used when the Range header is sent from the client to request only part of a resource.

207 Multi-Status (WebDAV)

Conveys information about multiple resources, for situations where multiple status codes might be appropriate.

208 Already Reported (WebDAV)

Used inside a <dav:propstat> response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.

226 IM Used (HTTP Delta encoding)

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

Redirection messages

300 Multiple Choices: The request has more than one possible response. The user agent or user should choose one of them. (There is no standardized way of choosing one of the responses, but HTML links to the possibilities are recommended so the user can pick.)
301 Moved Permanently: The URL of the requested resource has been changed permanently. The new URL is given in the response.
302 Found: This response code means that the URI of requested resource has been changed temporarily.
Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.
303 See Other: The server sent this response to direct the client to get the requested resource at another URI with a GET request.
304 Not Modified: This is used for caching purposes.
It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
305 Use Proxy Deprecated: Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy.
It has been deprecated due to security concerns regarding in-band configuration of a proxy.
306 unused: This response code is no longer used; it is just reserved. It was used in a previous version of the HTTP/1.1 specification.
307 Temporary Redirect: The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request.
This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.
308 Permanent Redirect: This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header.
This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.

Client error responses

400 Bad Request: The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
401 Unauthorized: Although the HTTP standard specifies «unauthorized», semantically this response means «unauthenticated».
That is, the client must authenticate itself to get the requested response.
402 Payment Required Experimental: This response code is reserved for future use.
The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.
403 Forbidden: The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource.
Unlike 401 Unauthorized, the client’s identity is known to the server.
404 Not Found: The server cannot find the requested resource.
In the browser, this means the URL is not recognized.
In an API, this can also mean that the endpoint is valid but the resource itself does not exist.
Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client.
This response code is probably the most well known due to its frequent occurrence on the web.
405 Method Not Allowed: The request method is known by the server but is not supported by the target resource.
For example, an API may not allow calling DELETE to remove a resource.
406 Not Acceptable: This response is sent when the web server, after performing server-driven content negotiation, doesn’t find any content that conforms to the criteria given by the user agent.
407 Proxy Authentication Required: This is similar to 401 Unauthorized but authentication is needed to be done by a proxy.
408 Request Timeout: This response is sent on an idle connection by some servers, even without any previous request by the client.
It means that the server would like to shut down this unused connection.
This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing.
Also note that some servers merely shut down the connection without sending this message.
409 Conflict: This response is sent when a request conflicts with the current state of the server.
410 Gone: This response is sent when the requested content has been permanently deleted from server, with no forwarding address.
Clients are expected to remove their caches and links to the resource.
The HTTP specification intends this status code to be used for «limited-time, promotional services».
APIs should not feel compelled to indicate resources that have been deleted with this status code.
411 Length Required: Server rejected the request because the Content-Length header field is not defined and the server requires it.
412 Precondition Failed: The client has indicated preconditions in its headers which the server does not meet.
413 Payload Too Large: Request entity is larger than limits defined by server.
The server might close the connection or return an Retry-After header field.
414 URI Too Long: The URI requested by the client is longer than the server is willing to interpret.
415 Unsupported Media Type: The media format of the requested data is not supported by the server, so the server is rejecting the request.
416 Range Not Satisfiable: The range specified by the Range header field in the request cannot be fulfilled.
It’s possible that the range is outside the size of the target URI’s data.
417 Expectation Failed: This response code means the expectation indicated by the Expect request header field cannot be met by the server.
418 I'm a teapot: The server refuses the attempt to brew coffee with a teapot.
421 Misdirected Request: The request was directed at a server that is not able to produce a response.
This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.
422 Unprocessable Entity (WebDAV): The request was well-formed but was unable to be followed due to semantic errors.
423 Locked (WebDAV): The resource that is being accessed is locked.
424 Failed Dependency (WebDAV): The request failed due to failure of a previous request.
425 Too Early Experimental: Indicates that the server is unwilling to risk processing a request that might be replayed.
426 Upgrade Required: The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.
The server sends an Upgrade header in a 426 response to indicate the required protocol(s).
428 Precondition Required: The origin server requires the request to be conditional.
This response is intended to prevent the ‘lost update’ problem, where a client GETs a resource’s state, modifies it and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
429 Too Many Requests: The user has sent too many requests in a given amount of time («rate limiting»).; The server is unwilling to process the request because its header fields are too large.
The request may be resubmitted after reducing the size of the request header fields.
451 Unavailable For Legal Reasons: The user agent requested a resource that cannot legally be provided, such as a web page censored by a government.

Server error responses

500 Internal Server Error: The server has encountered a situation it does not know how to handle.
501 Not Implemented: The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD.
502 Bad Gateway: This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.
503 Service Unavailable: The server is not ready to handle the request.
Common causes are a server that is down for maintenance or that is overloaded.
Note that together with this response, a user-friendly page explaining the problem should be sent.
This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time before the recovery of the service.
The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.
504 Gateway Timeout: This error response is given when the server is acting as a gateway and cannot get a response in time.
505 HTTP Version Not Supported: The HTTP version used in the request is not supported by the server.
506 Variant Also Negotiates: The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
507 Insufficient Storage (WebDAV): The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
508 Loop Detected (WebDAV): The server detected an infinite loop while processing the request.
510 Not Extended: Further extensions to the request are required for the server to fulfill it.
511 Network Authentication Required: Indicates that the client needs to authenticate to gain network access.

Browser compatibility

BCD tables only load in the browser

400 Bad Request
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
409 Conflict
410 Gone
413 Payload Too Large
415 Unsupported Media Type
422 Unprocessable Entity
429 Too Many Requests
The status of verifying the right to manage the site (ApiVerificationState)
Rights verification methods (ApiVerificationType)
Explicit methods of rights verification (ApiExplicitVerificationType)
Reasons for refusal to verify site management rights (ApiVerificationFailReason)
Source of the Sitemap file (ApiSitemapSource)
Type of Sitemap file (ApiSitemapType)
Site indexing status (ApiHostDataStatus)
Indexing indicators (ApiIndexingIndicator)
Query indicators (ApiQueryIndicator)
Query sorting order (ApiQueryOrderField)
Device type indicators (ApiDeviceTypeIndicator)
Indicators of external links (ApiExternalLinksIndicator)
Internal link indicators (ApiInternalLinksBrokenIndicator)
Reindexing request status (RecrawlStatusEnum)
Issue categories on the site (SiteProblemSeverityEnum)
State of the issue (ApiSiteProblemState)
Type of site issue (ApiSiteProblemTypeEnum)
HTTP status codes received by the robot during indexing (IndexingStatusEnum)
Site page status in search results (ApiSearchEventEnum)
Changes to important pages in the search (ApiImportantUrlChangeIndicator)
Reasons for excluding the page from search results (ApiExcludedUrlStatus)
RSS feed upload modes (PagesLoadMode)
RSS feed upload mode filter (TaskTypeFilter)
Status of the RSS feed upload task (LoadStatus)

ENTITY_VALIDATION_ERROR

The request body validation failed.

{
  "error_code": "ENTITY_VALIDATION_ERROR",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

FIELD_VALIDATION_ERROR

Invalid parameter passed.

{
  "error_code": "FIELD_VALIDATION_ERROR",
  "error_message": "explicit error message",
  "field_name": "some string",
  "field_value": "some string",
  "error_message": "explicit error message"
}

Parameter	Description
`error_code`	Error code.
`field_name`	Field.
`field_value`	Value.
`error_message`	Error message.

INVALID_URL

Wrong URL was passed.

{
  "error_code": "INVALID_URL",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

ACCESS_FORBIDDEN

The action is unavailable because the application doesn’t have the necessary permissions.

{
  "error_code": "ACCESS_FORBIDDEN",
  "error_message": "explicit error message"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

INVALID_OAUTH_TOKEN

The OAuth token is missing or invalid.

{
  "error_code": "INVALID_OAUTH_TOKEN",
  "error_message": "explicit error message"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

INVALID_USER_ID

The ID of the user who issued the token differs from the one specified in the request. In the examples below, {user_id} shows the correct uid of the OAuth token owner.

{
  "error_code": "INVALID_USER_ID",
  "available_user_id": 1,
  "error_message": "Invalid user id. {user_id} should be used."
}

Parameter	Description
`error_code`	Error code.
`available_user_id`	ID of the user who allowed access.
`error_message`	Error message.

LICENCE_NOT_ACCEPTED

You have to accept the User agreement.

{
  "error_code": "LICENCE_NOT_ACCEPTED",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

HOSTS_LIMIT_EXCEEDED

The number of sites in the user’s site list exceeded the limit (the current limit is 1703).

{
 "error_code": "HOSTS_LIMIT_EXCEEDED",
 "limit": 1,
 "error_message": "explicit error message"
}

Parameter	Description
`error_code`	Error code.
`limit`	The limit on the number of added sites.
`error_message`	Error message.

RESOURCE_NOT_FOUND

The resource at the requested path does not exist.

{
  "error_code": "RESOURCE_NOT_FOUND",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

HOST_NOT_INDEXED

The site isn’t indexed yet.

{
  "error_code": "HOST_NOT_INDEXED", //errorCode. 
  "host_id": "http:ya.ru:80", //id хоста. host id. 
  "error_message": "some string" //Error message. 
}

Parameter	Description
`error_code`	Error code.
`host_id`	ID of the requested site.
`error_message`	Error message.

HOST_NOT_LOADED

The site data isn’t uploaded to Yandex.Webmaster yet.

{
  "error_code": "HOST_NOT_LOADED",
  "host_id": "http:ya.ru:80",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`host_id`	ID of the requested site.
`error_message`	Error message.

HOST_NOT_VERIFIED

Site management rights are not verified.

{
  "error_code": "HOST_NOT_VERIFIED",
  "host_id": "http:ya.ru:80",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`host_id`	ID of the requested site.
`error_message`	Error message.

HOST_NOT_FOUND

The site is not in the list of the user’s sites.

{
  "error_code": "HOST_NOT_FOUND",
  "host_id": "http:ya.ru:80",
  "error_message": "explicit error message"
}

Parameter	Description
`error_code`	Error code.
`host_id`	ID of the requested site.
`error_message`	Error message.

SITEMAP_NOT_FOUND

The Sitemap for the site wasn’t found.

{
  "error_code": "SITEMAP_NOT_FOUND",
  "host_id": "http:ya.ru:80",
  "sitemap_id": "c7-fe:80-c0",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`host_id`	ID of the requested site.
`sitemap_id`	The Sitemap file ID.
`error_message`	Error message.

SITEMAP_NOT_ADDED

The Sitemap file is missing.

{
  "error_code": "SITEMAP_NOT_ADDED",
  "host_id": "http:ya.ru:80",
  "sitemap_id": "c7-fe:80-c0",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`host_id`	ID of the requested site.
`sitemap_id`	The Sitemap file ID.
`error_message`	Error message.

TASK_NOT_FOUND

Failed to find a task with the specified ID.

{
  "error_code": "TASK_NOT_FOUND",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

QUERY_ID_NOT_FOUND

The specified search query ID does not exist.

{
  "error_code": "QUERY_ID_NOT_FOUND",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

The HTTP method is not supported for this resource.

{
  "error_code": "METHOD_NOT_ALLOWED",
  "error_message": "explicit error message"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

The content types passed in the Accept header are not supported.

{
  "error_code": "CONTENT_TYPE_UNSUPPORTED",
  "acceptable_types": [
    "some string", ...
  ],
  "error_message": "explicit error message"
}

Parameter	Description
`error_code`	Error code.
`acceptable_type`	List of supported content types.
`error_message`	Error message.

URL_ALREADY_ADDED

The URL was already added for reindexing.

{
  "error_code": "URL_ALREADY_ADDED",
  "error_message": "some string"
}

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

HOST_ALREADY_ADDED

The site with the specified address is already added to the user’s sites list.

{
  "error_code": "HOST_ALREADY_ADDED",
  "host_id": "http:ya.ru:80",
  "verified": false,
  "error_message": "some string"
}

<Data>
  <error_code>HOST_ALREADY_ADDED</error_code> 
  <host_id>http:ya.ru:80</host_id> 
  <verified>false</verified> 
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`host_id`	The site ID.
`verified`	Indicates if the site rights are verified.
`error_message`	Error message.

VERIFICATION_ALREADY_IN_PROGRESS

The rights verification process is in progress.

{
  "error_code": "VERIFICATION_ALREADY_IN_PROGRESS",
  "verification_type": "META_TAG",
  "error_message": "some string"
}

<Data>
  <error_code>VERIFICATION_ALREADY_IN_PROGRESS</error_code>  
  <verification_type>META_TAG</verification_type> 
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`verification_type`	The verification method being processed ( ApiExplicitVerificationType ).
`error_message`	Error message.

TEXT_ALREADY_ADDED

The text you added earlier.

{
  "error_code": "TEXT_ALREADY_ADDED",
  "error_message": "some string"
}

<Data>
  <error_code>TEXT_ALREADY_ADDED</error_code>  
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

SITEMAP_ALREADY_ADDED

The Sitemap was already added.

{
  "error_code": "SITEMAP_ALREADY_ADDED",
  "sitemap_id": "c7-fe:80-c0",
  "error_message": "some string"
}

<Data>
  <error_code>SITEMAP_ALREADY_ADDED</error_code> 
  <sitemap_id>c7-fe:80-c0</sitemap_id>  
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`sitemap_id`	The Sitemap file ID.
`error_message`	Error message.

Resource unavailable

{
  "error_code": "UPLOAD_ADDRESS_EXPIRED",
  "valid_until": "2016-01-01T00:00:00,000+0300",
  "error_message": "some string"
}

<Data>
  <error_code>UPLOAD_ADDRESS_EXPIRED</error_code>
  <valid_until>2016-01-01T00:00:00,000+0300</valid_until>
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`valid_until`	The date and time until which the URL for task creation is available.
`error_message`	Error message.

The file size exceeds the limits.

{
  "error_code": "REQUEST_ENTITY_TOO_LARGE",
  "error_message": "some string"
}

<Data>
  <error_code>REQUEST_ENTITY_TOO_LARGE</error_code>
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`error_message`	Error message.

CONTENT_TYPE_UNSUPPORTED

The content type in the request is not supported.

{
  "error_code": "CONTENT_TYPE_UNSUPPORTED",
  "supported_content_types": [
    "some string", ...
  ],
  "error_message": "explicit error message"
}

<Data>
    <error_code>CONTENT_TYPE_UNSUPPORTED</error_code>
    <supported_content_type>some string</supported_content_type>
    ...
    <error_message>explicit error message</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`supported_content_type`	List of supported content types.
`error_message`	Error message.

CONTENT_ENCODING_UNSUPPORTED

The request encoding type is not supported.

{
  "error_code": "CONTENT_ENCODING_UNSUPPORTED",
  "supported_content_encodings": [
    "some string"
  ],
  "error_message": "some string"
}

<Data>
  <error_code>CONTENT_ENCODING_UNSUPPORTED</error_code> 
  <supported_content_encoding>some string</supported_content_encoding>  
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`supported_content_encoding`	List of supported encoding types.
`error_message`	Error message.

The passed text is too short or too long.

{
  "error_code": "TEXT_LENGTH_CONSTRAINTS_VIOLATION",
  "max_length": 1,
  "min_length": 1,
  "actual_length": 1,
  "error_message": "explicit error message"
}

<Data>
  <error_code>TEXT_LENGTH_CONSTRAINTS_VIOLATION</error_code>
    <max_length>1</max_length>
    <min_length>1</min_length>
    <actual_length>1</actual_length>
  <error_message>explicit error message</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`max_length`	Maximum length.
`min_length`	Minimum length.
`actual_length`	The length of the text in the request.
`error_message`	Error message.

QUOTA_EXCEEDED

The daily quota for requests was exceeded.

{
  "error_code": "QUOTA_EXCEEDED",
  "daily_quota": 1,
  "exceeded_until": "2016-01-01T00:00:00,000+0300",
  "error_message": "some string"
}

<Data>
  <error_code>QUOTA_EXCEEDED</error_code>  
  <daily_quota>1</daily_quota>  
  <exceeded_until>2016-01-01T00:00:00,000+0300</exceeded_until>  
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`daily_quota`	The maximum number of requests per day.
`exceeded_until`	Time when the new quota starts.
`error_message`	Error message.

TOO_MANY_REQUESTS_ERROR

Too many requests sent.

{
  "error_code": "TOO_MANY_REQUESTS_ERROR",
  "daily_quota": 1,
  "exceeded_until": "2016-01-01T00:00:00,000+0300",
  "error_message": "some string"
}

<Data>
  <error_code>TOO_MANY_REQUESTS_ERROR</error_code>  
  <daily_quota>1</daily_quota>  
  <exceeded_until>2016-01-01T00:00:00,000+0300</exceeded_until>  
  <error_message>some string</error_message>
</Data>

Parameter	Description
`error_code`	Error code.
`daily_quota`	The maximum number of requests per day.
`exceeded_until`	Time when the new quota starts.
`error_message`	Error message.

Status	Description
NONE	Verification wasn’t completed and rights are not confirmed.
VERIFIED	The rights are verified.
IN_PROGRESS	The rights verification is in progress.
VERIFICATION_FAILED	Verification was performed but rights are not confirmed.
INTERNAL_ERROR	An unexpected error occurred when verifying the rights.

Verification method	Whether a verification check can be requested	Description
AUTO	No	Automatic rights verification (deprecated; only for *.narod.ru sites).
DELEGATED	No	Rights were delegated.
DNS	Yes	Verifying rights with the DNS record.
HTML_FILE	Yes	Placing an HTML file in the site’s root directory.
META_TAG	Yes	Adding a meta tag to the site’s home page header.
PDD	No	Rights verification via Yandex.Mail for Domains.
TXT_FILE	No	Placing a text file in the site’s root directory.
WHOIS	Yes	Verifying data with information provided by the WHOIS service. This method works only for second-level domains (such as example.com).

Verification method	Whether a verification check can be requested	Description
DNS	Yes	Verifying rights with the DNS record.
HTML_FILE	Yes	Placing an HTML file in the site’s root directory.
META_TAG	Yes	Adding a meta tag to the site’s home page header.
WHOIS	Yes	Verifying data with information provided by the WHOIS service. This method works only for second-level domains (such as example.com).

Reason for refusal	Description
DELEGATION CANCELLED	Delegation of site management rights was canceled.
DNS_RECORD_NOT_FOUND	The specified DNS record doesn’t exist.
META_TAG_NOT_FOUND	The meta tag is missing in the site’s home page header.
PDD_VERIFICATION_CANCELLED	Verification of site management rights via Yandex.Mail for Domain isn’t allowed for this site.
WHOIS_EMAIL_NOT_FOUND	The specified email address is missing in the WHOIS record for this site.
WRONG_HTML_PAGE_CONTENT	The HTML file content is set incorrectly.

Source	Description
ROBOTS_TXT	Sitemap is specified in the site’s robots.txt file.
WEBMASTER	The user added the Sitemap in Yandex.Webmaster.
INDEX_SITEMAP	Sitemap found in another (index) Sitemap file.

Type	Description
SITEMAP	Normal Sitemap file that contains the URLs of site pages.
INDEX_SITEMAP	The Sitemap index file that contains the URLs of other Sitemap files.

Source	Description
NOT_INDEXED	The site isn’t indexed yet.
NOT_LOADED	The site data isn’t uploaded to Yandex.Webmaster yet.
OK	The site is indexed. The data is available in Yandex.Webmaster.

Indicator	Description
SEARCHABLE	Pages in the search.
DOWNLOADED	Downloaded pages.
DOWNLOADED_2XX	Pages downloaded with a 2XX code.
DOWNLOADED_3XX	Pages downloaded with a 3XX code.
DOWNLOADED_4XX	Pages downloaded with a 4XX code.
DOWNLOADED_5XX	Pages downloaded with a 5XX code.
FAILED_TO_DOWNLOAD	Failed to download.
EXCLUDED	Excluded pages.
EXCLUDED_DISALLOWED_BY_USER	Excluded at the request of the resource owner (4XX codes or prohibited in robots.txt).
EXCLUDED_SITE_ERROR	Excluded due to a site error.
EXCLUDED_NOT_SUPPORTED	Excluded as not supported by the Yandex robots.

Indicator	Description
TOTAL_SHOWS	The number of displays.
TOTAL_CLICKS	The number of clicks.
AVG_SHOW_POSITION	The average position of the display.
AVG_CLICK_POSITION	Average click position.

Indicator	Description
TOTAL_SHOWS	The number of displays.
TOTAL_CLICKS	The number of clicks.

Indicator	Description
ALL	All device types.
DESKTOP	Computers.
MOBILE_AND_TABLET	Mobile phones and tablets.
MOBILE	Mobile phones.
TABLET	Tablets.

If the request does not specify a device type indicator, the default value is ALL.

Indicator	Description
LINKS_TOTAL_COUNT	The total number of known external links to the host.

Indicator	Description
SITE_ERROR	The total number of known external links to the site.
DISALLOWED_BY_USER	The page doesn’t exist or is prohibited from indexing.
UNSUPPORTED_BY_ROBOT	Not supported by the main Search indexing robot.

Indicator	Description
IN_PROGRESS	The request is being processed.
DONE	The robot crawled the URL
FAILED	The robot failed to crawl the page. Make sure it is accessible to the robot and the server responds fast enough.

Indicator	Description	Note
FATAL	Fatal errors. Checks the server connection, site availability for indexing, security and compliance with Yandex guidelines.	This may lead to excluding individual pages or the entire site from search results. We recommend monitoring these errors and fixing them as soon as possible.
CRITICAL	Critical issues. Checks the presence and validity of the SSL certificate, the number of broken internal links, and the server response time.
POSSIBLE_PROBLEM	Possible issues. Checks the Sitemap and robots.txt file validity, settings for displaying non-existent files, the number of duplicate pages, the presence of redirects, annoying ads, and so on.	May affect the quality and speed of site indexing.
RECOMMENDATION	Recommendations. Usually includes suggestions for improving the site’s ranking in search results.	Use them to improve the site’s ranking in search results.

Indicator	Description
PRESENT	Present on the site.
ABSENT	Missing.
UNDEFINED	Not enough data to determine if there are issues.

Indicator	Description
FATAL
DISALLOWED_IN_ROBOTS	The site is prohibited for indexing in the robots.txt file.
DNS_ERROR	Failed to connect to the server due to a DNS error.
MAIN_PAGE_ERROR	The site’s home page returns an error.
THREATS	Security threats or issues were detected.
CRITICAL
SLOW_AVG_RESPONSE_TIME	Slow server response. For more information, see this Help section.
SSL_CERTIFICATE_ERROR	Invalid SSL certificate settings. For more information, see this Help section.
POSSIBLE_PROBLEM
BAD_ADVERTISEMENT	Ad formats do not comply with IAB Russia recommendations.
DOCUMENTS_MISSING_DESCRIPTION	Many pages do not have the Description meta tag.
DOCUMENTS_MISSING_TITLE	The title element is missing on many pages.
ERROR_IN_ROBOTS_TXT	Errors in the robots.txt file.
ERRORS_IN_SITEMAPS	Errors found in the Sitemap file.
MAIN_MIRROR_IS_NOT_HTTPS	The site’s main mirror doesn’t use the HTTPS protocol We recommend using the HTTPS protocol. For more information and instructions on switching protocols, see the Help.
MAIN_PAGE_REDIRECTS	The main page redirects to another site.
NO_METRIKA_COUNTER_CRAWL_ENABLED	Site crawling using Yandex.Metrica tags isn’t enabled. For more information about site indexing using the Yandex.Metrica tag, see the Help.
NO_ROBOTS_TXT	The robots.txt file wasn’t found.
NO_SITEMAPS	The Sitemap files used by the robot are missing.
NO_SITEMAP_MODIFICATIONS	The Sitemap files haven’t been updated for a long time.
NON_WORKING_VIDEO	The robot failed to index videos on the site.
SOFT_404	The display of non-existent files and pages is configured incorrectly.
TOO_MANY_DOMAINS_ON_SEARCH	The site subdomains are found in the search results.
TOO_MANY_PAGE_DUPLICATES	Too many duplicate pages.
RECOMMENDATION
FAVICON_PROBLEM	The favicon file was not found. The robot failed to load an image file to display in the browser tab and next to the site name in the search results. For more information about this error and how to fix it, see the help section.
INCOMPLETE_SPRAV_COMPANY_PROFILE	Yandex.Directory contains incomplete information about the organization.
NO_CHATS	Chats on Search are missing.
NO_METRIKA_COUNTER	Yandex.Metrica tag error
NO_REGIONS	The site region isn’t set.
NOT_IN_SPRAV	The site isn’t registered in Yandex.Directory.
NOT_MOBILE_FRIENDLY	The site isn’t optimized for mobile devices.

Indicator

Description

HTTP_2XX

HTTP_3XX

HTTP_4XX

HTTP_5XX

For more information about statuses, see the help section.

OTHER

Unsupported HTTP code, connection error, or other error.

Indicator	Description
APPEARED_IN_SEARCH	The page appeared in search results.
REMOVED_FROM_SEARCH	The page was removed from search results.

Indicator	Description
INDEXING_HTTP_CODE	The HTTP response code received by the robot when crawling the page changed.
SEARCH_STATUS	The page status in the search changed (it was added or removed).
TITLE	The page title changed.
DESCRIPTION	The Description meta tag content changed.

Indicator	Description
NOTHING_FOUND	The robot doesn’t know about the page, or it was unavailable for a long time. Submit the page for reindexing.
HOST_ERROR	When trying to access the site, the robot could not connect to the server. Check the server response and make sure that the Yandex robot isn’t blocked by the hosting provider. The site is indexed automatically when it becomes available for the robot. For information about the user agent robots, see the help section.
REDIRECT_NOTSEARCHABLE	The page redirects to another page. The target page is indexed (RedirectTarget). Check the indexing of the target page.
HTTP_ERROR	An error occurred when accessing the “HTTP error” page. Check the server response. If the problem persists, contact your site administrator or the server administrator. If the page is already available, submit it for reindexing.
NOT_CANONICAL	The page is indexed by the canonical URL specified in the rel=»canonical» attribute in its source code. Correct or delete the attribute if it is specified incorrectly. The robot will track the changes automatically.
NOT_MAIN_MIRROR	The page belongs to a secondary site mirror, so it was excluded from the search.
PARSER_ERROR	When trying to access the page, the robot couldn’t get its content. Check the server response or the presence of prohibiting HTML elements. If the problem persists, contact your site administrator or the server administrator. If the page is already available, send it for reindexing.
ROBOTS_HOST_ERROR	Site indexing is prohibited in the robots.txt file. The robot will automatically start crawling the page when the site becomes available for indexing.
ROBOTS_URL_ERROR	Page indexing is prohibited in the robots.txt file. The robot will automatically crawl the page when it becomes available for indexing.
DUPLICATE	The page duplicates a site page that is already in the search. For more information, see the help section.
LOW_QUALITY	The page has been removed from search results due to low quality as determined by a special algorithm. If the algorithm finds the page relevant to users’ search queries, it will appear in the search automatically.
CLEAN_PARAMS	The page was excluded from the search after the robot processed the Clean-param directive. To get the page indexed, edit the robots.txt file.
NO_INDEX	The page is excluded because the robots meta tag has the noindex value.
OTHER	The robot does not have updated data for the page. Check the server response or the presence of prohibiting HTML elements. If the page can’t be accessed by the robot, contact the administrator of your site or server. If the page is already available, send it for reindexing.

Indicator	Description
DEBUG	Debugging the Turbo page display.
PRODUCTION	Turbo pages publishing.

Indicator	Description
DEBUG	Debugging the Turbo page display.
PRODUCTION	Turbo pages publishing.
ALL	Getting information about both task types.

Indicator	Description
PROCESSING	The file is checked for errors.
OK	The file is loaded and it doesn’t contain errors.
WARNING	XML elements in the file aren’t supported by Yandex or are specified incorrectly.
ERROR	The file contains errors (for example, duplicate XML elements).

Источник

Установка сертификата Let’s encrypt

Ручное обновление сертификата

Information responses

Successful responses

Redirection messages

Client error responses

Server error responses

Browser compatibility

See also

Читайте также: