Portal Management Guide
Portals are the connection points to your Xtream Codes servers. This guide explains how to manage portals effectively.
What is a Portal?
A portal represents a single Xtream Codes server configuration. It contains:
- Server URL (e.g., http://server.example.com:8080)
- A friendly name for easy identification
- Active/Inactive status
- Optional notes
💡 Use Cases for Multiple Portals:
- Different geographical servers (US, EU, Asia)
- Primary and backup servers
- Different content packages
- Testing vs production servers
Creating a Portal
- Navigate to "Portal Management" in the sidebar
- Click "Add New Portal"
- Enter the portal details:
- Portal Name: Give it a descriptive name
- Server URL: The full URL to your Xtream server
- Notes: Any additional information
- Click "Create Portal"
📸 Screenshot: Portal List
Shows the portal management page with list of portals and action buttons
Server URL Format
The server URL should be the base URL of your Xtream Codes panel:
http://your-server.com:8080
http://123.456.789.10:25461
https://secure-server.com
⚠️ Important: Do not include trailing slashes or paths like /player_api.php. Just the base URL with port.
Editing a Portal
- Find the portal in your list
- Click the Edit (✏️) button
- Modify the details as needed
- Click "Update Portal"
⚠️ Note: Changing the server URL will affect all codes using this portal. Make sure the new URL is valid.
Deactivating a Portal
If you need to temporarily disable a portal:
- Edit the portal
- Toggle the "Active" switch to OFF
- Save the changes
Deactivated portals:
- Won't allow new code creation
- Existing codes will show "Portal inactive" when validated
- Can be reactivated at any time
Deleting a Portal
You can only delete a portal if no codes are using it.
- First, delete or reassign all codes using this portal
- Click the Delete (🗑️) button on the portal
- Confirm the deletion
💡 Tip: The portal card shows "X codes" to help you see which portals are in use.
Best Practices
- Use descriptive names ("US East Server" vs "Server 1")
- Add notes about server capacity or special features
- Set up a backup portal for redundancy
- Regularly verify server URLs are accessible