--- title: Configure url: https://doc2.pstreamer.tv/en/manual/webui/configure.html lang: en product: Perfect Streamer version: 2.0.2.362 --- # Configure The **Configure** group in the “Node” area brings together the settings that do not belong to the server services: access accounts and the electronic program guide (EPG) subsystem. The screens of the group are available to the administrator role. ## Users / Logins ![Users and logins.](../../_images/webui_users_local.en.png) Management of stream receiver access to the node. The screen contains the tabs: ****Local logins**** Accounts of the stream receivers — the clients of OTT delivery and of the peer protocols. For each one the login and the password or “IP address account” (the “IP address / CIDR” field; a single address and ranges are supported), “Allowed streams” (an empty list — all are allowed), the concurrent connection limits per protocol (PS1, SRT, HTTP/HLS), “Expiry date”, pause and “Prefix login” for integration with middleware ([12. Middleware integration](../extras/ott_caching.md#extras-ott-middleware)) are set. The web interface login accounts and their roles are configured on the “Web server & accounts” screen ([Web server & accounts](administration.md#webui-web-server)); the roles are described in [Access and roles](index.md#webui-access). ****Remote (billing)**** Authorization of stream receivers through an external system: instead of the local check the login is confirmed by an HTTP request to a third-party server. At the top of the tab is the “Billing service” card with the “Billing request interval (s)” parameter. Below it is the ordered “Billing servers” list; when a login is checked, the servers are queried in the order of the list (the order is set by dragging, and on a narrow screen by the `Alt+↑` and `Alt+↓` shortcuts, see [Keyboard operation](index.md#webui-keyboard)). For a server the “Name”, “URL”, password, “Timeout (s)”, “Session accounting”, “Login prefix” and “Login suffix” are set, while the “Connector” set to “Universal (HTTP)” fully describes the exchange — the HTTP request template (query, body, “Content-Type”, headers with template substitutions of the login, the password, the IP and so on) and the parsing of the response (“Response format” — the HTTP status code, a JSON body or an XML body — with the paths to the success indicator and to the rejection reason); “Trace” enables logging of the exchange. The “Prefix login” as a built-in alternative to external billing is described in [12. Middleware integration](../extras/ott_caching.md#extras-ott-middleware). ### User: add and edit The window for creating and editing a stream receiver account; it is opened by the “Add user” button or by “Edit” in a list row on the “Local logins” tab. Fields: - “Login” and “Password” — an ordinary account; when editing, an empty password keeps the current one. The “IP address account” flag replaces the “login — password” pair with the “IP address / CIDR” field (a single address or a range), and “Prefix login” enables the middleware integration mode ([12. Middleware integration](../extras/ott_caching.md#extras-ott-middleware)). - “Allowed streams” — the streams and adaptive sets the account is admitted to; an empty list imposes no restriction — all of them are allowed. The list only permits: a particular stream cannot be forbidden, it can merely be left out of the list; access can be closed entirely with “Protocol forbidden” in the connection limits — but that closes a protocol, not a single stream. A deleted stream stays in the list as a dead row: the interface shows it struck through and removes it on save, while an edit made through the API, bypassing the interface, is rejected in its entirety because of such a row — until it is removed, not even the note of the account can be changed. - “Max connections, PS1”, “Max connections, SRT” and “Max connections, HTTP/HLS” — separate limits on simultaneous connections for each of the delivery protocols. Each of them has three states: “No limit”, “Protocol forbidden” — the account is not served on this protocol at all — and “At most” with a number. The prohibition is stored as zero and meant a prohibition in the earlier builds as well, so the meaning of the saved settings does not change after the update; a separate “No limit” state did not exist before 2.0.1.263, it was represented by a deliberately large number, and such accounts keep working. The HTTP/HLS limit is counted separately for the direct MPEG-TS delivery and for the OTT sessions — each set up to the stated number — and they behave differently: a direct delivery connection over the limit is refused, while a new OTT session evicts the one of this login’s earlier sessions that has been idle the longest. - “Expiry date” and “Paused” — planned or temporary disabling of access without deleting the account. - “Display name” and “Note” — for the operator’s own records; they do not affect access. The HTTP/HLS limit that has been set applies to the direct MPEG-TS delivery as well: in earlier builds it constrained the delivery only at the value of 1, so wherever the limit was once set with room to spare and never checked, after the update the surplus connections will start being refused. What becomes of the account’s current sessions when it is edited depends on what exactly has changed. The list of allowed streams breaks sessions only where it has taken access away: adding a stream to a non-empty list and going back to an empty list touch nobody, while narrowing it — including the very first stream entered into an empty list, since until then all of them were allowed — closes the PS1 and SRT sessions on the streams the list no longer allows. For HTTP/HLS the disconnection remains common to the whole account: an OTT session is authorized anew and continues from the player’s next request if access to the stream has been kept, while a direct MPEG-TS delivery connection is closed and the receiver opens it again itself. Lowering the connection limit — including a switch from “No limit” to a number — closes every session of the account on that protocol, and not only the surplus ones; raising the limit and switching to “No limit” touch none of them. Putting the account on pause and entering an “Expiry date” that has already passed close all of the account’s sessions at once, whereas the date falling due by itself does not break them — it only refuses the next login, while the sessions already started hold until the receiver disconnects on its own. In builds before 2.0.1.263 any edit of the list of allowed streams disconnected the account entirely on all protocols, including the streams the edit did not concern. The web interface login accounts and their roles are set not here but on the “Web server & accounts” screen ([Web server & accounts](administration.md#webui-web-server)). ## EPG Settings ![EPG settings (import).](../../_images/webui_epg_import.en.png) Configuration of the electronic program guide: where the data comes from and how it is delivered. Viewing of the collected guide is placed on a separate screen, “EPG Database” ([EPG Database](monitor.md#webui-epg-database)). The screen contains the tabs: ****Import**** The general parameters of program guide import: “Enable import”, “Keep history, days” (the retention depth for past events), “Auto-clean orphan channels”, and also the “XMLTV source URL” and “XMLTV source name” of the main external source. EPG import as a whole is described in [EPG/XMLTV import](../streamer/epg/xmltv.md#streamer-epg-xmltv). ****Sources**** A list of external XMLTV sources. For each one — “Name”, “Source URL / path”, the “Enabled” flag, “Update interval, s”, “Content encoding” (auto-detect or forced GZip), credentials and Cookies for restricted web resources, and “Save downloaded copy” for diagnostics ([Source configuration](../streamer/epg/xmltv.md#streamer-epg-sources)). ****Channel sets**** Named sets that group channels for delivery to external consumers. On the tab a set is created (name and note); its composition — the channel membership — is defined in the EPG database ([EPG Database](../streamer/epg/xmltv.md#streamer-epg-database)). The use of the sets during delivery is described in [EPG for OTT middleware](../streamer/epg/middleware.md#streamer-epg-middleware). ****Accounts**** Access of external consumers to the built-in EPG server — the XMLTV download. For an account the login and the password, the “Channel set” (defines the composition of the delivery; without a set the delivery is empty), “Expiry date”, “Allowed IP” and the “Paused” flag are set. XMLTV delivery is described in [XMLTV delivery](../streamer/epg/middleware.md#streamer-epg-server). The EPG subsystem as a whole — EIT generation and delivery for OTT middleware — is described in [EPG/EIT](../streamer/epg/index.md#streamer-epg).