Setting up per vhost network bandwidth monitoring/throttling?

Discussion in 'Installation/Configuration' started by Richard Foley, Jul 7, 2019.

Tags:
  1. Richard Foley

    Richard Foley Member

    hi all, I've followed the excellent https://www.howtoforge.com/tutorial/perfect-server-debian-9-nginx-bind-dovecot-ispconfig-3.1/3/ guide to get my ispConfig3 set up and running nicely. Disk quota is being tracked correctly (as far as I can tell) for mail and FTP and web space. However, I don't see any tracking of network bandwidth, nor any way to limit the bandwidth usage once (for expample) it goes over a certain amount. Am I missing the obvious documentation for this? Is there a recommended solution to use with ispConfig3? Thanks in advance for any helpful assistance and/or tips.
     
    Richard Foley, Jul 7, 2019
    #1
  2. Richard Foley

    Richard Foley Member

    Last edited: Jul 7, 2019
    Richard Foley, Jul 7, 2019
    #2
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    till, Jul 8, 2019
    #3
    Richard Foley likes this.
  4. Richard Foley

    Richard Foley Member

    Richard Foley, Jul 8, 2019
    #4
  5. Richard Foley

    Richard Foley Member

    The good news: I've managed to get both monit and munin working on my ispConfig3 installation. and munin also visible from within the ispConfig3 framework / menu structure. Not gotten to the nginx stuff yet.

    The bad news: monit displays a blank page because of the embedded credentials referred to in this April 2018 post: https://www.howtoforge.com/community/threads/monit-page-is-blank.76160/

    It is of course possible to work with monit outside of the ispConfig3 frame, so this is not critical, but as this would make life a lot more intuitive/easier, is there is an update/workaround which fixes this within it, please?
     
    Richard Foley, Jul 8, 2019
    #5
  6. Jesse Norell

    Jesse Norell Well-Known Member Staff Member Howtoforge Staff

    I setup a /monit/ location which uses a reverse proxy to the monit server and uses certificate authentication rather than a username/password between the proxy and monit, and verifies the user by checking that the ISPConfig session cookie is valid. It's heavily apache specific though, but you could take the general design and implement it in nginx.
     
    Jesse Norell, Jul 8, 2019
    #6
  7. Richard Foley

    Richard Foley Member

    Sounds plausible, Jesse, I'll look into doing something like that. Thanks for the suggestion.

     
    Richard Foley, Jul 8, 2019
    #7

Share This Page