PAYG behind proxy.

modules/administration/nav-administration-guide.adoc

@@ -89,6 +89,7 @@ endif::[]
 *** xref:troubleshooting/tshoot-packages-proxy.adoc[Repository Via Proxy Issues]
 *** xref:troubleshooting/tshoot-passing-grains-to-start-event.adoc[Passing Grains to a Start Event]
 *** xref:troubleshooting/tshoot-payg.adoc[{payg}]
+*** xref:troubleshooting/tshoot-public-cloud-configure-payg-behind-proxy.adoc[{payg} Behind Proxy]
 *** xref:troubleshooting/tshoot-proxy-connections-and-fqdns.adoc[Proxy Connections and FQDN]
 *** xref:troubleshooting/tshoot-registerclones.adoc[Registering Cloned Clients]
 *** xref:troubleshooting/tshoot-reg-from-webui-fails-no-errors.adoc[Registration from {webui} fails and does not show any errors]

modules/administration/pages/troubleshooting/tshoot-public-cloud-configure-payg-behind-proxy.adoc

@@ -0,0 +1,16 @@
+[[troubleshooting-public-cloud-configure-payg-behind-proxy]]
+= Configure {payglongform} Behind Proxy
+
+To identify if a machine is {payg} or not, {productname} needs to use [literal]``sudo`` to run [literal]``instance-flavor-check``tool.
+
+
+If the customer is using a http proxy, they need to make sure this setting is correctly managed by [literal]``sudo``, because by default most environment variables are disregarded.
+
+One way for the customer to do it, is to add a file [path]``/etc/sudoers.d/keep_proxy.conf`` with the following content:
+
+----
+# Preserve any possible proxy configuration
+Defaults env_keep += "http_proxy https_proxy no_proxy"
+----
+
+This ensures the proxy related environment variables are preserved during the privileges escalation.