Skip to main content

Change the Qalyptus server port

Qalyptus Server uses port 3994 by default for web interface access. You can change this port during installation or modify it afterward to resolve conflicts with other applications or meet network requirements.

When to Change the Port​

Common scenarios:

  • Port 3994 is already in use by another application
  • Corporate network policies require specific port ranges
  • Load balancer or proxy configuration requirements
  • Use the default HTTPS port (443) to avoid specifying the port

Prerequisites​

  • Administrative access to the Qalyptus Server machine
  • Credentials for the Qalyptus Server service user account
  • Knowledge of available ports (not reserved by other applications)
Check Port Availability

Ensure the new port number is not in use by another application. Use netstat -an to check active ports before making changes.

Changing the Server Port​

  1. Access the server machine with the user account that runs the Qalyptus Server service
  2. Open Qalyptus Server Configuration from the Start menu
  3. Navigate to the General tab
  4. Authenticate with the Qalyptus Server service user credentials
  5. Enter the new port number in the appropriate field
    • Choose a port not used by other applications
    • Common alternatives: 8080, 8443, 9994
  6. Update certificate settings (if applicable)
    • For third-party certificates, enter the certificate fingerprint
    • For self-signed certificates, leave the certificate field as default
  7. Save the configuration changes
  8. Verify the change when the confirmation message appears

Post-Configuration Steps​

Update Firewall Rules​

If Windows Firewall or network firewalls are enabled:

  • Add the new port to allowed applications
  • Remove the old port rule if no longer needed

Update User Bookmarks​

  • Notify users of the new URL format: https://server:newport
  • Update any automated scripts or integrations

Test Connectivity​

  • Access Qalyptus Server using the new port
  • Verify all functionality works correctly
  • Test from different network locations if applicable
Important

After changing the port, the old URL (with port 3994) will no longer work. Update all references to use the new port number.

Best Practice

Document the port change in your system documentation and notify all users before implementing the change.