Warning
AI Disclosure: This project was developed entirely using AI. The creator is not a Python or Java programmer. Use at your own risk. The creator is not responsible for data loss or system instability.
Click to collapse Screenshots
Home Page:
Config Page:
Debug Page:
Settings Page:
Login Page:
Follow these steps to set up the environment and run the Unbound DNS WebUI.
First, ensure that pip and the venv package are installed on your system.
# Update package list and install pip
sudo apt install python3-pip
# Install the virtual environment package
sudo apt install python3-venv
It is recommended to use a virtual environment to manage your dependencies and keep your system clean.
# Create a virtual environment named 'venv'
python3 -m venv venv
# Activate the virtual environment
source venv/bin/activate
Once activated, you will see (venv) prepended to your terminal prompt.
Inside the activated virtual environment, install the required Python packages:
# Install FastAPI with standard dependencies
pip install "fastapi[standard]"
# Install the itsdangerous module for security
pip install itsdangerous
If you are using a reverse proxy (like Nginx), you do not need to install the cryptography package, as the proxy typically handles TLS termination. In this setup, the WebUI will be accessible via HTTP on port 8080.
However, if you are not using a proxy and want to use HTTPS directly (highly recommended), you must install the cryptography package. This allows the application to generate and manage self-signed TLS certificates:
pip install cryptography
Run the application using Python. On the first launch, if cryptography is installed, the system will automatically generate a self-signed TLS certificate.
python app.py
Example Output:
(venv) root@server:~/WebUI-for-Unbound-DNS# python app.py
[ssl] Generating self-signed TLS certificate…
[ssl] Certificate written to /root/WebUI-for-Unbound-DNS/ssl_cert.pem
[ssl] Private key written to /root/WebUI-for-Unbound-DNS/ssl_key.pem (chmod 600)
[ssl] Valid for 3650 days
[http-redirect] 8080 → https://...:8443
[app] HTTPS on [https://0.0.0.0:8443](https://0.0.0.0:8443)
Once the application is running:
- With TLS/HTTPS: Access the interface at
https://<your-ip>:8443. - Without TLS/HTTP: Access the interface at
http://<your-ip>:8080.
the default login credentials is admin/admin
Note
If you are using a self-signed certificate, your browser will display a "Potential Security Risk" warning. This is expected behavior; you can safely click "Advanced" and "Proceed" to access your local interface.