Reverse Proxy FAQs

You might run into some errors when using Reverse Proxy.

Common errors and solutions

Issue Solution

Accessing company.cdsw.cloudera.com displays Apache2 default page This issue occurs because there is a default configuration that points to the same port. You can list the configurations listening to each port by entering apachectl -S. Disable the unnecessary configurations from the files to avoid this issue.

Seeing errors with the WebSockets

Issue	Solution
Accessing company.cdsw.cloudera.com displays Apache2 default page	This issue occurs because there is a default configuration that points to the same port. You can list the configurations listening to each port by entering `apachectl -S`. Disable the unnecessary configurations from the files to avoid this issue.
Seeing errors with the WebSockets	Usually this issue is seen when there are SSL certificate issues or the certificate is not trusted. Check the following: If the reverse proxy is configured with a certificate for `company.cdsw.cloudera.com` and `*.company.cdsw.cloudera.com` If the `backend-company.cdsw.cloudera.com` is configured with the certificate for `backend-company.cdsw.cloudera.com` If the CA is trusted in the client machine

Usually this issue is seen when there are SSL certificate issues or the certificate is not trusted. Check the following:

If the reverse proxy is configured with a certificate for company.cdsw.cloudera.com and *.company.cdsw.cloudera.com
If the backend-company.cdsw.cloudera.com is configured with the certificate for backend-company.cdsw.cloudera.com
If the CA is trusted in the client machine