Read this article for steps to install Lucidchart with Confluence or Jira using a firewall or proxy.
Plan availability: Free, Individual, Team, and Enterprise.
- Not available on FedRAMP accounts.
- Read the Lucid Plans article for more information about what is available on your account or the Upgrade your Lucid account article for instructions to upgrade.
Before getting started
Before getting started, you'll need to determine if your data center uses a proxy or not. Depending on the answer, you can follow the appropriate steps below.
Whether or not you your data center uses a proxy, please make sure that your configurations are set up so as to allow the relevant domains through your firewalls or other filters. A full list of domains to allow can be found in our Prepare your network for Lucid users article.
If you are unsure whether your firewall allows these domains, you can use our Firewall Test to verify. Navigate to the Lucidchart add-on configuration, select the Firewall Test tab, then select the “run test” button.
If the results show that the lucid.app domains are not reachable, you’ll need to allow them through your firewall before being able to use the integration.
Install with a proxy
- Double check that you have Confluence/Jira set up correctly to proxy as described in Confluence's documentation here.
- Try setting the following two system properties: https.proxyHost and https.proxyPort
- Go to Administration > System Information and verify that you see the proxy parameters in the "Java Runtime Arguments" section.
If these steps still don't do the trick, please contact Lucid support and let us know the values for your Confluence/Jira Version, JVM Vendor and Java version.
Install without a proxy
First, follow these steps:
- Try: telnet www.lucidchart.com 443.
- You should get:
"Trying 23.21.229.160...
Connected to lucidchart-web-1117125819.us-east-1.elb.amazonaws.com."
Note: Escape character is '^]'
If that doesn't work, try:
- Connecting to a random SSL site to determine if you can connect to other SSL sites. Try: telnet www.wellsfargo.com 443.
- You should get:
"Trying 151.151.88.133...
Connected to www.wellsfargo.com."
If you're unable to connect to another SSL site, there is still probably a firewall somewhere on your network that is blocking port 443. You'll need to work with your network team to determine what firewalls and proxies might exist on your network that would be blocking port 443.
Give feedback on this article
Have feedback about this article? Tell us about your experience here.