Webserver.Port 8081

Questions
14

Ok, it seems like there’s a deeper issue with permissions. Let’s first ensure your admin account has all the necessary permissions it should have. Here’s a step-by-step:

  1. Reconfigure Permissions:

    • Login: Make sure you’re logged in as the highest authority admin.
    • Go to Users and Roles: In ADS, head to the Users and Roles section.
    • Modify Roles: Ensure your admin role has all permissions, especially Session.Exists, GSMyAdmin.WebServer.SetConfig, and ADSModule.CreateInstanceFromSpec.

  2. Reapply Permissions: Sometimes, reapplying permissions can resolve glitches:

    • Edit the admin user role and uncheck a critical permission (like Session.Exists).
    • Save the role.
    • Re-edit the role and re-enable the permission.
    • Save again.

  3. Restart ADS:

    • Stop ADS:
      ampinstmgr stop ADS01
    • Start ADS:
      ampinstmgr start ADS01

Once you’ve ensured permissions are set correctly and restarted ADS, try modifying the port range again:

  1. Access the ADS settings.
  2. Adjust the port range to 25515:25525.
  3. Save the settings.

Finally, create a new instance and see if it respects the new port range without giving you a permission error.

Try this out and let me know how it goes. :glowing_star:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback