getting-help.adoc

   1 [[getting_help]]
   2 Getting Help
   3 ------------
   4 include::attributes.txt[]
   5 ifdef::wiki[]
   6 :pve-toplevel:
   7 endif::wiki[]
   8
   9
  10 Proxmox VE Wiki
  11 ~~~~~~~~~~~~~~~
  12
  13 The primary source of information is the {webwiki}. It combines the reference
  14 documentation with user contributed content.
  15
  16
  17 Community Support Forum
  18 ~~~~~~~~~~~~~~~~~~~~~~~
  19
  20 {pve} itself is fully open source, so we always encourage our users to
  21 discuss and share their knowledge using the {forum}. The forum is fully
  22 moderated by the Proxmox support team, and has a quite large user base
  23 around the whole world. Needless to say that such a large forum is a
  24 great place to get information.
  25
  26 Mailing Lists
  27 ~~~~~~~~~~~~~
  28
  29 This is a fast way to communicate via email with the Proxmox VE
  30 community
  31
  32 * Mailing list for users:
  33   http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user[PVE User
  34   List]
  35
  36 The primary communication channel for developers is:
  37
  38 * Mailing list for developer:
  39   http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel[PVE
  40   development discussion]
  41
  42
  43 Commercial Support
  44 ~~~~~~~~~~~~~~~~~~
  45
  46 {proxmoxGmbh} also offers commercial
  47 http://www.proxmox.com/proxmox-ve/pricing[{pve} Subscription Service
  48 Plans]. System Administrators with a standard subscription plan can access a
  49 dedicated support portal with guaranteed reponse time, where {pve}
  50 developers help them should an issue appear.
  51 Please contact the mailto:office@proxmox.com[Proxmox sales
  52 team] for more information or volume discounts.
  53
  54
  55 Bug Tracker
  56 ~~~~~~~~~~~
  57
  58 We also run a public a public bug tracker at
  59 https://bugzilla.proxmox.com. If you ever detect a bug, you can file
  60 an bug entry there. This makes it easy to track the bug status, and
  61 you will get notified as soon as the bug is fixed.