Allowed Origins

Configure Pterodactyl Wings to accept connections from your PteroCA panel.

Overview

Allowed origins is a critical security setting in Pterodactyl that controls which domains are allowed to interact with your Wings instance. This must be configured to enable:

• Server console access

• Real-time statistics monitoring

• Server startup configuration

• WebSocket connections

Without this configuration, server consoles will not work.

Configure Allowed Origins

Step 1: Open Wings Configuration

Open the Pterodactyl Wings configuration file:

sudo nano /etc/pterodactyl/config.yml

Step 2: Add Allowed Origins

Locate (or create) the allowed_origins section and add your PteroCA panel domain or IP:

allowed_origins:
  - '127.0.0.1'  # Replace with your domain or IP where PteroCA is hosted
  # - '*'        # Optional: Wildcard to allow connections from any host (less secure)

Step 3: Save and Restart Wings

After saving the configuration file, restart Wings to apply changes:

sudo systemctl restart wings

Configuration Options

Specific Domain (Recommended)

Most secure approach - Only allow your specific domain:

allowed_origins:
  - 'panel.example.com'

Multiple Domains

If you have multiple domains pointing to PteroCA:

allowed_origins:
  - 'panel.example.com'
  - 'panel2.example.com'
  - '192.168.1.100'  # Can also include IP addresses

Wildcard (Not Recommended for Production)

Allows connections from any domain - only use for testing:

allowed_origins:
  - '*'

Security Warning: Using wildcard (*) allows connections from any domain, which may pose security risks in production environments.

Security Considerations

Production Environment

For production environments:

1. Use specific domains - Never use wildcard

2. Use HTTPS - Always use SSL/TLS

3. Match PteroCA URL - Use the exact domain from your PteroCA site URL

4. Limit origins - Only add domains you control

Development Environment

For development/testing:

1. Wildcard is acceptable - * can be used temporarily

2. Switch before production - Always update before going live

3. Document changes - Note what allowed origins are configured

Troubleshooting

Console Not Connecting

Symptom: Server console shows "Connection failed" or doesn't load

Solutions:

1. Verify allowed origins is configured

   cat /etc/pterodactyl/config.yml | grep -A 5 allowed_origins

2. Check PteroCA site URL matches

   • Go to PteroCA Admin Panel → Settings → General

   • Note the Site URL

   • Ensure it's in Wings allowed_origins

3. Restart Wings after changes

   sudo systemctl restart wings
   sudo systemctl status wings

4. Check Wings logs

   sudo journalctl -u wings -n 100 --no-pager

Mixed Content Errors

Symptom: Console fails with mixed content error

Cause: PteroCA uses HTTPS but Pterodactyl uses HTTP (or vice versa)

Solution:

• Both PteroCA and Pterodactyl must use same protocol (both HTTPS recommended)

• See SSL Configuration

WebSocket Connection Failed

Symptom: "WebSocket connection failed" in browser console

Solutions:

1. Check firewall allows WebSocket port (usually 8080 or 443)

   sudo ufw allow 8080/tcp

2. Verify Wings is running

   sudo systemctl status wings

3. Check Wings config has correct external address

   api:
     host: 0.0.0.0
     port: 8080
     ssl:
       enabled: false

Cloudflare Proxy Issues

Symptom: Console works without Cloudflare but fails with it enabled

Solution:

1. Enable WebSocket in Cloudflare

   • Go to Cloudflare Dashboard → Network

   • Enable WebSocket

2. Use Cloudflare's Spectrum (if available)

   • Create Spectrum app for Wings port

   • Point to Wings server IP:8080

3. Or disable Cloudflare proxy for Wings subdomain

   • Set DNS record to "DNS only" (grey cloud)

Advanced Configuration

Custom Wings Port

If Wings uses a custom port:

# Wings config.yml
api:
  port: 8443  # Custom port
  ssl:
    enabled: true

Ensure firewall allows the custom port:

sudo ufw allow 8443/tcp

Multiple Wings Instances

If using multiple Wings instances, add origins for all of them:

# On each Wings instance
allowed_origins:
  - 'panel.example.com'

Reverse Proxy Configuration

If using a reverse proxy (like NGINX) in front of Wings:

# Wings config
allowed_origins:
  - 'panel.example.com'  # Your PteroCA domain

# NGINX proxy config should include
proxy_set_header Origin $http_origin;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

Testing Console Access

After configuring allowed origins:

1. Log into PteroCA

2. Navigate to a server

3. Click on Console tab

4. Verify console loads and shows output

5. Test sending a command

If console still doesn't work, check these additional causes:

• Reverse proxy configuration

• SSL mismatches

• Firewall rules

• Network connectivity

For more troubleshooting help, see Runtime Issues.

Related Guides

• Pterodactyl API Configuration - Set up API integration

• SSL Configuration - Enable HTTPS

• Troubleshooting - Common issues