# Snownode over HTTPS

**URL:** <https://community.exalate.com/t/snownode-over-https/4991>\
**Category:** General Questions\
**Tags:** servicenow, snownode, migrated\_question, https, tls\
**Created:** [November 4, 2024, 7:36am UTC](https://community.exalate.com/t/snownode-over-https/4991 "2024-11-04T07:36:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 7:36am UTC](https://community.exalate.com/t/snownode-over-https/4991/1 "2024-11-04T07:36:42Z")

</div>

_Originally asked by David Martin on 29 December 2021 [(original question)](https://oldcommunity.exalate.com/questions/42830258)_

* * *

How can I configure Snownode to run over HTTPS for the Web UI and also redirect to HTTPS when HTTP is entered.

I am assuming it is to do with Tomcat or Apache configuration in the docker image

* * *

---

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 7:36am UTC](https://community.exalate.com/t/snownode-over-https/4991/2 "2024-11-04T07:36:43Z")

</div>

_Answer by Francis Martens (Exalate) on 03 January 2022_

Hi David,

An approach is to add a reverse proxy (on the same host) in front of the snownode.  
Nginx is in most cases the default choice, and the docker image [https://hub.docker.com/r/jwilder/nginx-proxy](https://hub.docker.com/r/jwilder/nginx-proxy) is very versatile, extremely popular and easy to use.

Have a look.

The docker-compose.yml we use in our test environment, combines that image with letsencrypt, which automates the creation of the certificates. The whole setup takes a couple of minutes.

```auto
version: '3'

services:
  proxy:
    restart: unless-stopped
    image: jwilder/nginx-proxy
    ports:
      - 80:80
      - 443:443
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock
      - ./certs:/etc/nginx/certs:ro
      - ./conf.d:/etc/nginx/conf.d
    labels:
      - com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy

  letsencrypt:
    restart: unless-stopped
    image: jrcs/letsencrypt-nginx-proxy-companion
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./certs:/etc/nginx/certs:rw

networks:
  default:
    external:
      name: proxy

```

* * *

#### Comments:

> **David Martin commented on 03 January 2022**
>
> > Hi Francis Martens (Exalate) ,
> 
> Thank you for the NGINX option. Is it not possible to set the container/web app to run as https only as we already have a reverse proxy (other server) we use and were just looking to secure comms between the reverse proxy and snownode.

> **Francis Martens (Exalate) commented on 04 January 2022**
>
> > Support for SSL connections are currently not supported in the product itself. As exalate is based on the play framework, it might be enabled by checking out  
> > [https://www.playframework.com/documentation/2.8.x/ConfiguringHttps](https://www.playframework.com/documentation/2.8.x/ConfiguringHttps)
> 
> If that is the route to follow - startup and application.conf will have to be externalized from the container image and adapted accordingly.
> 
> If this is a bridge too far, use jwilder/nginx as a workaround, and deploy it as part of the exalate node itself (by adding it as a service in the docker-compose)