Podążaj za instrukcjami w poniższym filmie, aby zobaczyć, jak zainstalować naszą stronę jako aplikację internetową na ekranie głównym swojego urządzenia.
Informacja: Ta funkcja może nie być dostępna w niektórych przeglądarkach.
Używasz przestarzałej przeglądarki. Może ona nie wyświetlać poprawnie tej lub innych stron internetowych. Powinieneś zaktualizować swoją przeglądarkę lub użyć alternatywnej przeglądarki.
The panel from outside through QTS: a new switch on the Settings page, Open from outside through QTS, opens the panel also at https://<NAS name>/webportico/. The address goes through QTS's own web server and uses QTS's certificate. You sign in with WebPortico's password, as on the local network. No port is opened on the router: the panel is reachable wherever QTS's port 443 is reachable.
Off until you turn it on: after the install the switch is off and QTS's configuration stays as it was. The switch does not turn on while the panel has no password or QTS's web server is not found on the NAS. The panel then says why, and nothing changes.
Minor
The card shows the address, with the myQNAPcloud name when QTS has one.
Through that address the panel works over HTTPS only and never offers the first-run setup. Failed sign-ins count for each visitor's own address. Adminer and the takeover of ports 80 and 443 open on the local network only.
When QTS restarts its web services, it drops the address. WebPortico puts it back within 5 minutes. Turning the switch off, stopping WebPortico and removing it take the address out of QTS's configuration.
If WebPortico's front server holds ports 80 and 443, QTS answers HTTPS on another port, and the card's address carries that port. The panel then opens at that port and through myQNAPcloud Link, which reaches QTS's own web server.
A proxy site passes on the host name together with the port the browser used. On WebPortico's own ports (9542 and 9543, while QTS holds 80 and 443) an app that compares where a request comes from with its host refused every change: Bucket & Code's sign-in failed with "403 csrf". On 80 and 443 nothing changes.
A proxy site made before 0.37.0 passes the port on once you apply the change the Sites page offers after the install. Its bar says the running configuration is out of date: click Preview changes, then Apply changes.
The note of the Bucket & Code template also says to add 127.0.0.1 to Trusted proxies on Bucket & Code's Network page. Without it Bucket & Code does not see the visitors' own addresses.
Licence texts of the bundled programs: the package holds the licence and notice files of all 129 programs and libraries it bundles, in share/licenses/ of WebPortico's folder. Among them are Apache httpd, nginx, PHP, MariaDB, Percona Server, PostgreSQL, Valkey, Node.js, Grafana, OpenSearch and the Java runtime. share/licenses/NOTICE lists each one with its licence, its version and the address of its source.
Old nginx processes end within 5 minutes: when an install replaces nginx, the old worker processes finish their requests for at most 5 minutes. Then they close what they still hold, such as a websocket or a slow download, and the client connects again to the new nginx. Up to 0.36.2 the old workers waited for their last connection, for an hour or longer.
Minor
A change to a site reloads nginx. The same 5-minute limit holds for these reloads from the second change to a site after the install. The first change writes the setting into nginx's configuration.
Apache httpd 2.4.71: WebPortico's httpd is 2.4.71 (was 2.4.68). It fixes a flaw in httpd's HTTP/2 module through which a request could corrupt httpd's memory and run code (CVE-2026-119618). In WebPortico no request could reach the flaw: its httpd listens only on the NAS itself, behind WebPortico's nginx, and speaks only HTTP/1.1. The install starts httpd again with the new program. Sites served by Apache answer 502 while httpd starts again, and a request in progress on them at that moment fails. Sites served by nginx keep answering.
nginx 1.30.7: WebPortico's nginx is 1.30.7 (was 1.30.5). It fixes security flaws that let a request from the internet crash nginx's worker processes, corrupt their memory or tie them up in an endless loop, over HTTP/2, HTTP/3 and TLS (CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-118899), and in a site's own nginx lines with try_files and alias (CVE-2026-125283). The web application firewall's module is built for 1.30.7. The install hands the running nginx over to the new program, and the sites go on answering.
A site's mail through MailServerPro on this NAS: a site's mail settings are on its Mail tab, above the mailboxes. When MailServerPro on this NAS serves the site's domain, Outgoing mail offers MailServerPro on this NAS. You pick a mailbox and a sender and type the mailbox's password. WebPortico sets the server, the port and the security itself.
Send a test e-mail: the button sends one message with the values in the form, saved or not, the way PHP's mail() sends it from the site. It says whether it signed in and sent. If not, it names the cause, such as a refused password, no connection or a refused sender.
QuFirewall's effect on your sites: WebPortico reads QuFirewall's rules and says when they cut off sites behind Cloudflare, Let's Encrypt renewals or incoming mail. Each warning says what to allow in QuFirewall. WebPortico never changes QuFirewall's rules.
Minor
The PHP tab keeps an Outgoing mail card. It says what is set, and Open the Mail tab opens the settings.
Another SMTP server shows the server's fields as before. Set a new password opens the password form of the chosen mailbox.
The test's answer also says whether the values it used are saved and applied yet. The other causes it names: an unknown server name, a certificate for another name or from an unknown authority, and a refused recipient.
Incoming mail server (IMAP) takes 127.0.0.1 or localhost, the way an application on this NAS names MailServerPro, and says what to enter in the application. Check sign-in checks a mailbox's password at MailServerPro and does not save it.
On a screen up to 900 px wide, the tables of the DNS and Mail tabs show each row as a list. Up to 0.35.0 a tablet broke a mailbox's address over several lines.
Open webmail on a site's Mail tab opens MailServerPro's webmail where MailServerPro names it: /mail/ from MailServerPro 0.6.9, the port's root with an earlier version.
The Front server and ports page has a QuFirewall card. For the websites, and for TurboDNS and MailServerPro when they run, it shows the regions new connections can come from, in IPv4 and IPv6. Check again reads the rules at once.
A site behind Cloudflare gets its visitors through Cloudflare's servers. With QuFirewall 2.6.2, a region profile such as "only Poland" lets in 0.25 % of Cloudflare's IPv4 addresses, and the other visitors get Cloudflare's error 522. The Sites page and the site's Overview tab say so in one warning.
The fix is to allow the front server's ports from all regions, or Cloudflare's IP address ranges. The card lists the ranges with a copy button. Sites served through the Cloudflare Tunnel are not affected.
Each Let's Encrypt card on the SSL/TLS page warns when QuFirewall would stop its renewal. HTTP-01 needs the front server's HTTP port from all regions. DNS-01 through TurboDNS needs TCP and UDP port 53.
Without QuFirewall the pages look as before. The update changes only WebPortico's panel and agent, so the sites keep running and nothing needs to be applied.
Traffic of each site: the new Traffic page shows each site's requests, data sent and received, and server errors (5xx) over 1 hour, 24 hours or 7 days, for all sites or one. One chart shows requests per minute, the other data per second. A bar shows the share of 2xx, 3xx, 4xx and 5xx responses. Under the charts each site has its numbers and its line over the range.
Each site's requests on the Sites page: under each site's name the Sites page shows its requests in the last minute, such as "48/min", and a small line of its last 30 minutes. A click opens the site's traffic.
Minor
Counting starts once you apply the changes in 0.35.0. After the update, the Sites page says that the running server configuration is out of date. Click Preview changes, then Apply changes.
nginx keeps one short line per request in a buffer and writes the lines into one file within 5 seconds. The WebPortico agent reads the new lines every 10 seconds and then empties the file. It does not read the access logs.
WebPortico counts a request when it ends, so a long download shows in its last minute. It does not count requests that a site's own settings exclude with access_log off.
The Sites view of the Processes page has a Requests/min column. Its tooltip says how many requests a minute went on to PHP, Apache or the proxy target, and their average time.
The Processes icon in the menu is drawn correctly. Up to 0.34.3 it showed a cut-off corner of a larger drawing.
On a screen 1180 px or wider, a list of your sites sits beside the page, grouped by domain, with a filter. One click opens a site from any page. The button at the bottom of the menu bar hides or shows the list, and the browser remembers it. On a phone the same list is in the Menu sheet, under the pages.
On the Sites page a tap anywhere on a domain's header row folds or unfolds its sites. Up to 0.34.3 only a tap on the domain's name did.
CrowdSec keeps protecting your sites: WebPortico asks CrowdSec for new blocks every 5 seconds, and each check now closes its connection. Up to 0.34.2 each check left its connection open. After about 5 and a half hours CrowdSec ran out of open files and stopped answering, so new attacks were no longer blocked.
WebPortico restarts CrowdSec when it stops answering: the service watchdog asks CrowdSec for an answer every 20 seconds. After 80 seconds without one, it restarts CrowdSec. The restart is listed on the Backups page under Automatic recovery, and QTS gets one notification. The watchdog restarts CrowdSec at most 3 times in 30 minutes.
Minor
CrowdSec and the WebPortico agent can open up to 65,536 files. Before, they had the QTS limit of 4,096.
When CrowdSec does not answer, the CrowdSec page shows "Not answering" in red instead of "Starting". Its message says that your sites stay reachable and that new attacks are not blocked. After a restart, the page shows when it happened and whether CrowdSec answers again. The program's error goes to logs/agent.log.
Start, Stop and Restart on CrowdSec's row of the Services page work. Up to 0.34.2 Restart answered "CrowdSec did not start" and changed nothing. After Stop, CrowdSec stays stopped until you start it again, and the CrowdSec page says so.
When the Services page cannot act on a service, it says "This page cannot start, stop or restart … Nothing was changed." It no longer says that the service did not start.
Each domain on the Sites page starts folded to one row: the row shows the domain, how many sites it holds, where its DNS records are kept and Add site. If something in the domain needs a look, the row says so, for example "1 DNS record waiting" or "2 sites have a certificate problem". Click the domain's name, or press Enter or Space on it, to see its sites. Up to 0.34.1 every domain showed all its sites at once.
A search box finds a site as you type: the box above the list matches any part of a site's name or alias, in any case, such as "forum", "shop.example" or "EXAMPLE.COM". It opens the domains that hold a match while the search lasts. When nothing matches, the page says "No site matches your search." with Clear search. Escape also clears the box, and the domains fold back as they were.
Minor
The domains you open stay open in that browser, also after a reload. A site you open keeps its domain open when you come back to the list. A site you add with the wizard does the same once the wizard saves it, and a wizard you cancel changes nothing.
A site has a certificate problem when its certificate cannot be read, misses one of the site's names, or has ended or ends within 14 days. A live site set to an uploaded or QTS certificate counts too when that certificate is missing.
A Let's Encrypt request that failed is not counted on the folded row yet. The site's Domains and TLS tab and the SSL/TLS page show it as before.
The Default site stays at the top of the list and does not fold.