Bug: Port 80 listener toggle incorrectly reports "already used" + Default Site ignored on HTTP

[yannickid]

Description

Two related bugs affecting the HTTP (port 80) listener behavior.

Bug 1: Port 80 toggle reports "already used" incorrectly

When Zoraxy itself holds port 80, the "Enable HTTP server on port 80"
toggle is permanently greyed out with the error "Port 80 is already
used by other services" — even though Zoraxy is the owner of the port.

Steps to reproduce:

1. Start Zoraxy in TLS mode
2. Enable port 80 listener
3. Restart Zoraxy
4. Try to toggle "Enable HTTP server on port 80" → greyed out

Bug 2: Default Site option ignored for unknown domains on port 80

When Force HTTPS is disabled, HTTP requests from unknown/unconfigured
domains always return 404 NOT FOUND, completely ignoring the
configured Default Site option (Static Web Server, Redirect, etc.).

Steps to reproduce:

1. Disable "Force redirect HTTP to HTTPS"
2. Set Default Site to "Internal Static Web Server"
3. Request any unconfigured domain via HTTP → 404 instead of Default Site

Fix

PR: #1184

Submitted a fix in the linked PR.

[expressrussian]

New install on Ubuntu 26.04. Zoraxy 333 restored settings from another old zoraxy 333.
I confirm Bug 1. "Port 80 is already used by other services"
in Linux this port 80 is used by zoraxy itself!!!
How to manage this???

tcp LISTEN 0 4096 *:443 : users:(("zoraxy_linux_am",pid=25615,fd=18)) ino:96346 sk:15 cgroup:/system.slice/zoraxy.service v6only:0 <->
tcp LISTEN 0 4096 *:80 : users:(("zoraxy_linux_am",pid=25615,fd=17)) ino:96343 sk:16 cgroup:/system.slice/zoraxy.service v6only:0 <->

[tobychui]

PR merged into v3.3.4 dev branch, should be in next release (v3.3.4-rc1) soon.
Closing this for now.