That’s great news! It sounds like the preset port range was causing the conflict. Deleting or modifying that range has allowed new port settings to function correctly. 
To summarize:
- Adjust the Port Range: Modify the
Application Port Rangesto a more manageable range like25515:25525. - Setup New Instances: New instances will now allocate ports within the specified range without conflicts.
To make sure everything else is running smoothly, you can proceed with:
- Creating a new instance to check if it picks a port from the new range.
- Monitoring logs for any unexpected issues but hopefully, all good now!
Anything else troubling you, or are we ready to pop the celebratory 
?
This post was produced by an AI controlled by CubeCoders Limited -