# Setting up SSL on Tomcat

**URL:** <https://community.letsencrypt.org/t/setting-up-ssl-on-tomcat/64820>\
**Category:** Help\
**Created:** [June 20, 2018, 9:10am UTC](https://community.letsencrypt.org/t/setting-up-ssl-on-tomcat/64820 "2018-06-20T09:10:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Softy](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@Softy](https://community.letsencrypt.org/u/Softy)\
**Post date:** [June 20, 2018, 9:10am UTC](https://community.letsencrypt.org/t/setting-up-ssl-on-tomcat/64820/1 "2018-06-20T09:10:06Z")

</div>

My domain [https://afghanchat.net](https://afghanchat.net)

My web server is (include version):Apche 2.2 and Tomcat

The operating system my web server runs on is (include version): Ubuntu 16

Hello Everyone,  
First of all I thank you guys for providing such a usefull service,

My Issue,  
I have installed SSL for Apache, and I am hosting a Chatserver script which is run by Tomcat,  
SSL is installed and working perfectly on Webserver,  
I need to configure tomcat to use the same certificate, bcoz Some websocket protocol needs to be secured too,  
can someone tell me how to use the same certificate which is already installed on Apche?  
thank you for your time

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [June 20, 2018, 9:56am UTC](https://community.letsencrypt.org/t/setting-up-ssl-on-tomcat/64820/2 "2018-06-20T09:56:44Z")

</div>

You are on Apache httpd 2.4, not 2.2.

You will probably want to use [https://httpd.apache.org/docs/2.4/mod/mod\_proxy\_wstunnel.html](https://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html) to proxy the websockets through your Apache server (via secure `wss://` connections), the same way you are already proxying httpd-\>Tomcat.

There shouldn’t be any need to do any extra configuration for certificates.

---

<div class="post-metadata">

**Author:** ![Softy](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@Softy](https://community.letsencrypt.org/u/Softy)\
**Post date:** [June 20, 2018, 10:02am UTC](https://community.letsencrypt.org/t/setting-up-ssl-on-tomcat/64820/3 "2018-06-20T10:02:50Z")

</div>

Thank you for your reply,  
The chatserver is running html5 and flash, the flash is working fine and yes indeed the WS is creating problem with Mix content error, so the browsers are blocking the WS connection, it should be WSS,  
I have hired a developer to fix the issue via proxy tunnel but he wasnt able to fix the issue

Edit:  
I am not sure if its allowed here or not, but is there any payed developer who is willing to fix this issue ?

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [June 20, 2018, 10:55am UTC](https://community.letsencrypt.org/t/setting-up-ssl-on-tomcat/64820/4 "2018-06-20T10:55:15Z")

</div>

I downloaded 123 Flash Chat 10.0 to try see what’s going on.

As far as I can tell, the `ws://` part of `ws://afghanchat.net:35555/websocket` is fully hardcoded in minified JavaScript, as part of the HTML Chat client.

The software does not appear provide a way to customize the protocol in a clean way.

Even the demo on the marketing site “cheats” and redirects to an insecure origin.

You could try and replace `ws://` with `wss://`, setup a a secure reverse proxy on another port, and change the client to that secure port, but it would be a hack.

Perhaps you can reach out to the developers and ask them to properly support SSL - or change to another chat package.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [August 7, 2018, 9:32am UTC](https://community.letsencrypt.org/t/setting-up-ssl-on-tomcat/64820/7 "2018-08-07T09:32:32Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
