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