Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 492
    • Issues 492
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 28
    • Merge Requests 28
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4912

Closed
Open
Opened Jan 12, 2018 by Till Brehm@tbrehmOwner

Remote API call fails with IDS security error

Calls to the ISPConfig remote API fail with error "Possible attack detected. This action has been logged.".

Workaround:

Edit the file /usr/local/ispconfig/security/security_settings.ini and disable the IDS by changing these two values from 'yes' to 'no':

ids_anon_enabled=no
ids_user_enabled=no

or install an ISPConfig version where this issue is marked as fixed.

Edited Jan 12, 2018 by Till Brehm
Assignee
Assign to
3.1.12
Milestone
3.1.12
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#4912