Why are keys not issued to the 1C web client?

Question

1C

There is a terminal server, there is a MSSQL server and Server 1C. Everyone connects through a thin client to the terminal, and the 1C server issues keys. But when connecting through a browser, the keys are not visible. The error reads:

Платформа: 1С:Предприятие 8.2 (8.2.19.106)
Режим: Веб-сервер
Приложение: Веб-клиент

Ошибки:
--------------------------------------------------------------------------------
15.05.2015, 22:14:11
Не найдена лицензия. Не обнаружен ключ защиты программы или полученная программная лицензия!
Поиск лицензии на сервере:
ORGL8 Локальный, не установлен
Файл программной лицензии не найден
ORG8A Локальный, не установлен
ORG8B Локальный, не установлен
nethasp.ini: отсутствует, использованы настройки по умолчанию, ошибка соединения с менеджером лицензий: Net Status=0, System Error=0, Warning=129, ORGL8 Сетевой, не установлен
nethasp.ini: отсутствует, использованы настройки по умолчанию, ошибка соединения с менеджером лицензий: Net Status=0, System Error=0, Warning=129, ORG8A Сетевой, не установлен
nethasp.ini: отсутствует, использованы настройки по умолчанию, ошибка соединения с менеджером лицензий: Net Status=0, System Error=0, Warning=129, ORG8B Сетевой, не установлен

What is most interesting, errors on the key occur before the authorization form is opened. When, as usual, when the keys are not visible, the error occurs after authorization.

Answer 1

What is most interesting, errors on the key occur before the authorization form is opened. When, as usual, when the keys are not visible, the error occurs after authorization.

When accessing the web, after entering the login/password, you may catch the problem of the lack of free licenses. When the web server does not see the licensing server, it immediately says so.
In your description, you did not write a word about the computer on which your web server is located. The fact that the platform of the necessary version is installed on this computer is obvious, but judging by the message, it is also obvious that you did not create in the C:\Program Files\1cv8\conf or /opt/1C/v8.2/i386/conf directory ( depending on the OS) nethasp.ini file with the path to the license server. This helps if the server for some reason does not issue a license.
Next, check in the cluster console the name of the central computer (on which the licensing manager is running) and the availability of this name from the web server computer. I also met with such a situation - it helps to match the name and IP address in the hosts file.
The third option that comes to my mind and that I have seen in practice is that the firewall on the server blocks the port on which the web server extension tries to connect to the cluster. It helped to change the rules.

Answer 2

You need in the settings of the 1C server cluster in the properties of the desired database, check the box "Allow the issuance of keys by the server"