You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,6 +121,7 @@ Ensure you have configured your ADS instances by following the [Configuring AMP
121
121
122
122
⚠️ Ensure to change WHMCS_URL to your own domain where WHMCS is installed as this will allow AMP to tell WHMCS once the product is created and the status of the instance.
<h2>Setting up a Server Group & Product within WHMCS</h2>
126
127
@@ -189,6 +190,18 @@ You can set custom configuration options within WHMCS for settings such as RAM A
189
190
6. Further values can be set using a template as described in the following article or can be set in WHMCS directly by adding a `+` to the beginning of the key.
190
191
[Configuring AMP for Enterprise or Network Usage](https://discourse.cubecoders.com/t/configuring-amp-for-enterprise-or-network-usage/1830)
191
192
193
+
<h2>Troubleshooting</h2>
194
+
195
+
You can view a large portion of the communication between AMP and WHMCS by enabling debug logging in both.
196
+
1. In WHMCS, go to **System Logs -> Module Log** and enable Module Logging.
197
+
2. In AMP, search for "Debug" in the top right to change the logging level.
198
+
3. Repeat the action you were trying and look for output from both sides.
199
+
4. If you cannot figure out the issue on your own, you can share the logs through the support channels.
200
+
201
+
⚠️ The logs contain sensitive information, so be sure to remove any details you do not want public before sharing for support!
0 commit comments