This article explains the issue wherein the LWC is in Juniper Cloud Disconnected state even though the config is done on the JSI portal.
The JSI captive portal shows Juniper Cloud Disconnected and Not Provisioned.
All the config is done on the JSI captive portal.
Check the following:
https://www.juniper.net/documentation/us/en/quick-start/software/jsi/jsi-on-jsp-quick-start-vlwc/topics/topic-map/jsi-step-1-begin.html#task_zlv_lp4_dyb
https://www.juniper.net/documentation/us/en/quick-start/software/jsi/jsi-on-jsp-quick-start-vlwc/topics/topic-map/jsi-step-1-begin.html#concept_phd_2vx_hcc__table_cmc_jgy_xrb
Example: The Squid configuration directive
cache_peer AWSProxy-prod.jssprod.junipercloud.net parent 443 0 no-query default
is used to define an upstream proxy (a "parent" cache) and configure how the local Squid instance interacts with it.
Please note that this is an example from the squid proxy server (which is where Juniper does its testing).
You need to find the equivalent command for this (check with your proxy server team) and have that configured on your proxy server.