Port requests
Port requests is how you tell Templass which listeners your service needs. Mitigation and firewall work is worse when the platform does not know you serve 443/tcp or a game port.
Use Templass Panel for the request. Do not send a port list to a random Discord user and assume it was applied.
How to file a request
- Open Port requests.
- State protocol (TCP or UDP) and port or range.
- Add a short reason (for example "HTTPS" or "game query"). That helps review.
- Submit once.
- Wait for the request to be accepted. This is an admin-backed step, not always instant.
If Panel has no form on your account yet, email [email protected] with the same facts, or ask in Discord.
What to request
- Ports your origin listens on for customers
- Both TCP and UDP when the application uses both
- New ports before you advertise them
Need a wide range? Ask [email protected] rather than requesting 1-65535 by default.
After acceptance
Confirm:
- Firewall still allows the port if you added deny rules
- Rate limiting is not clipping the new listener
- Clients use the protected address, not the origin
During an attack
A brand-new port request mid-event may not land in time. Say that you have a pending request when you ping support, and keep the existing listener on Templass. See Under attack.