Overview

When sending a GET request for the PDF version of a document or blog post (for example, https://jiveinstanceurl/docs/doc-1001.pdf or
https://jiveinstanceurl/blogs/blog.pdf), the request sometimes fails with a 502 error code. The same requests typically work when they are sent again.

Solution

On each Jive web server, follow these steps:

1. Log in to the server through the command-line interface.
2. Change your account to the jive user by running the command: sudo su - jive
3. Go to: /usr/local/jive/etc/httpd/conf/
4. Use your preferred text editor to update the httpd.conf file.
5. Copy and paste the following lines at the end of the file:
   • Timeout 180
   • ProxyTimeout 180
6. Save the file.

Once you complete the above steps on all the web servers, conduct a rolling restart of your community.

Testing

1. Run multiple GET requests to the URLs that you were encountering this issue with.
2. Confirm that you are no longer receiving 502 error codes for those requests.
3. If the issue persists, please contact us so that ATLAS can assist you. If you are not satisfied with the solution provided by ATLAS, then it will create a ticket for you on which you can provide the below information:
   
   1. HAR file.
   2. The date and time of the last request that failed with a 502 error.
   3. The following log files attached (Log files can be found in the /usr/local/jive/var/logs folder on those servers):
      1. From your Jive web servers:
         • The sbs.out and sbs.log files.
         • The access log files: 
           
           • jive-httpd-access.log
           • jive-httpd-error.log
           • jive-httpd-ssl-access.log
           • httpd-error.log
      2. From your document conversion servers: The docconverter.out files.