Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 550
    • Issues 550
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 40
    • Merge requests 40
  • 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
  • #5932

Closed
Open
Created Nov 26, 2020 by Sergio@SGr33n

When update ISPConfig, if a custom port is setted for apps domain it returns to the default 8081, only on the config file (remains custom on the web panel)

short description

When updating ISPConfig if App Domain have a non standard value it come back on the default 8081 even if the Web Panel reports the custom port.

correct behaviour

App domain should remain on the custom port as setted on the web panel.

environment

Server OS: Ubuntu Server OS version: 20.04.01 ISPConfig version: <= 3.2.1

Assignee
Assign to
Time tracking