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 494
    • Issues 494
    • 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
  • #3937

Closed
Open
Opened May 31, 2016 by Jens Groh@JeGr

Add switch for warning/disabling website after traffic quota exceeding

At the moment any webspace exceeding its traffic quota is sent an email via the nightly cronjob (00:30) and disabled afterwards. As this is something that can be breaking business for a website owner and showing the default webpage is kina strange, I'd like to suggest three things here:

  1. adding a setting or switch to change the behavior between "disable when exceeded" and "notify when exceeded" so there is a way to not disable the customers web but show it with traffic exceeded warning in ISPCs webspace list and get him/her to pay extra after that month (just an example)
  2. add a warning threshold like ~90% traffic exceeded that goes to the customers, reseller & admin mail addresses when setting is "disable when exceeded", so there is no 'surprise' if the website shows up without content
  3. create a warning page in the same style the custom error pages and default web pages are set up but with the info, that this web was disabled because of traffic exceeding, so the customer is actually aware of the source of the problem rather than calling the reseller/hoster with a "bug that shows the default page instead of the website".

That would make a great addition and IMHO create a much better handling than the current situation, as most reseller/hosters offer a) unlimited traffic (but log it so they can measure 'strange' spikes), b) 'fair use' traffic (if it is too high, user has to pay or gets limited) or c) a traffic package that has the user pay extra for traffic exceeding. But if you want the user to pay for extra traffic, it's not a rather good motivation for him to wake up the next day and look at a blank page ;)

https://www.howtoforge.de/forum/threads/website-am-traffic-limit-kunde-admin-bekommen-keine-nachricht.9436/

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#3937