Skip to main content

Change the database port

Qalyptus Server uses an internal PostgreSQL database that listens on port 4048 by default. This port can be changed to resolve conflicts with other applications or meet specific network requirements.

About the Database Port​

The database port is used for:

  • Internal operations: Qalyptus Server's data storage and retrieval
  • ODBC connections: External applications connecting to the database (not recommended)
  • Administrative tools: Database management and backup operations

When to Change the Database Port​

Common scenarios:

  • Port 4048 conflicts with another application
  • Network security policies require specific port ranges
  • ODBC connection requirements
  • Database administration tool conflicts

Prerequisites​

  • Administrative access to the Qalyptus Server machine
  • Qalyptus Server service user credentials
  • Knowledge of available ports
  • List of existing ODBC connections (if any)

Changing the Database Port​

  1. Access the server machine with the Qalyptus Server service user account
  2. Open Qalyptus Server Configuration from the Start menu
  3. Navigate to the Database Settings tab
  4. Enter the new port number in the Port field. Choose an available port (not used by other applications)
  5. Save the configuration
  6. Verify the confirmation message

Post-Configuration Tasks​

Update ODBC Connections​

If you have established ODBC connections to the Qalyptus database:

  1. Open ODBC Data Source Administrator
  2. Locate existing Qalyptus connections
  3. Update the port number in each connection
  4. Test the connections to ensure they work

Update External Applications​

  • Modify any custom applications that connect to the database
  • Update database connection strings in scripts or configuration files
  • Notify other administrators of the change

Firewall Configuration​

  • Add the new port to firewall exceptions if required
  • Remove the old port rule if no longer needed
Database Access Recommendation

Qalyptus does not recommend direct database access using ODBC connections and SQL queries. The database schema may change without notice in future updates, potentially breaking custom applications. Use the Qalyptus REST API instead for reliable, supported integration with external systems.