Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 549
    • Issues 549
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #967
Closed
Open
Created Mar 12, 2010 by Ricardo@Germanius

Force client to use only allowed IPs

Would be nice if clients could only use IPs which a reseller/admin allowed him to use.

Example: Admin creates a website (example.com) for the client and chooses the IP 123.123.123.123 (NOT the *). Later on the client decides to create another website (web.example.com). Now he has the choice between * and 123.123.123.123. He has to choose the IP, but may be he doesnt know that, so he chooses the *. The result ist that the new site doesnt work. That are my experiences.

Another thing which i did not try: Admin adds a IP, because he needs it for SSL certificate. What happens to the ssl site or to the client site when another client chooses the ssl IP?

As a result I think it would be great if a client can only choose the IP(s) which the reseller/admin allowed him and of course not the *.

Assignee
Assign to
Time tracking