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