New Proxy Rule

You can add more proxy rules to support more site via domain / subdomains

Matching Keyword / Domain Support subdomain and wildcard, e.g. s1.mydomain.com or *.test.mydomain.com. Use comma (,) for alias hostnames.

Target IP Address or Domain Name with port e.g. 192.168.0.101:8000 or example.com

Proxy Target require TLS Connection
(i.e. Your proxy target starts with https://)

Advance Settings

Sticky Session
Enable stick session on upstream load balancing

Enable uptime monitor
Automatically check upstream status and switch to another if offline

Disable Requests Logging
Disable requests logging for this host, recommended for high traffic sites

Tags Comma-separated list of tags for this proxy host.

Security

Ignore TLS/SSL Verification Error
For targets that is using self-signed, expired certificate (Not Recommended)

Skip WebSocket Origin Check
Allow cross-origin websocket requests (Usually not a security concern)

Allow plain HTTP access
Allow this subdomain to be connected without TLS (Require HTTP server enabled on port 80)

Access Control

Access Rule Allow regional access control using blacklist or whitelist. Use "default" for "allow all".

Require Basic Auth
Require client to login in order to view the page

Enter the username and password for allowing them to access this proxy endpoint

Username	Password	Remove
No Entered Credential

Require Rate Limit
This proxy endpoint will be rate limited.

Rate Limit

req / sec / IP

Return a 429 error code if request rate exceed the rate limit.

Matching Keyword Examples

Domain
Example of domain matching keyword:
aroz.org
Any acess requesting aroz.org will be proxy to the IP address below

Subdomain
Example of subdomain matching keyword:
s1.aroz.org
Any request starting with s1.aroz.org will be proxy to the IP address below

Wildcard
Example of wildcard matching keyword:
*.aroz.org
Any request with a host name matching *.aroz.org will be proxy to the IP address below. Here are some examples.

www.aroz.org

foo.bar.aroz.org

Remote Target Require TLS

Upstream TLS Requirement

When you enable Proxy Target require TLS Connection, it means the upstream server (the target you are proxying to) requires a secure (HTTPS) connection.
This does not affect whether clients connect to this proxy endpoint using HTTP or HTTPS.

Example

Matching Keyword: mydomain.com

                        Target: example.com:443 (TLS enabled)

Client connects to mydomain.com (HTTP or HTTPS, depending on your proxy setup)
Proxy forwards requests to example.com:443 using HTTPS

Use this option if your upstream server only accepts secure connections.
If your upstream uses a self-signed certificate, check the Ignore TLS/SSL Verification Error option in Advance Settings.

What is Sticky Session?

Sticky Session (Session Affinity)

Sticky session ensures that requests from the same client are always forwarded to the same upstream server. This is useful for applications that store session data locally and require the client to consistently connect to the same backend.

How to Add Multiple Upstreams

Go to HTTP Proxy in the sidebar.
Click Edit on your proxy rule.
Use the Upstreams section to add more upstream endpoints for load balancing.

Sticky session will only work if you have more than one upstream endpoint configured.