1. Home
  2. vDDoS Proxy Protection
  3. Configuration
  4. Add Website HTTPS

Add Website HTTPS

Assuming you have a need to use HTTPS, you can also easily configure it to be similar to an HTTP web:

NOTE: To request a Let's Encrypt certificate please follow this article

Enable HTTPS:

1. Edit website.conf:

nano /vddos/conf.d/website.conf

# Website       Listen            Backend               Cache  Security  SSL-Prikey  SSL-CRTkey
your-domain.com	http://0.0.0.0:80 http://20.79.197.2:80 no     no       no          no
your-domain.com https://0.0.0.0:443 https://20.79.197.2:443 no no      /vddos/ssl/your-domain.com.pri /vddos/ssl/your-domain.com.crt


In that configuration:
Website is: your-domain.com

https://0.0.0.0:443 is: Protocol & IP:PORT, that vDDoS needs to listen to serve for your-domain.com domain.
https://20.79.197.2:443 is: Protocol & IP:PORT of the original web server of your-domain.com, which you want vDDoS to know and transfer traffic to that server (it’s called a Backend Server)

Cache is: no
Security is: no

Sets SSL Private-Public Key website for vDDoS:
SSL-Private key: /vddos/ssl/your-domain.com.pri
SSL-CRTkey: /vddos/ssl/your-domain.com.crt

2. Restart vDDoS (After each configuration change):

[root@vDDoS ~]# vddos restart

(Defensive Estimating ~ 273 RealReq/s)
0.0.0.0:80
0.0.0.0:443
vDDos service Restart success!


Check HTTPS:

[root@vDDoS ~]# curl -k -I https://your-domain.com 

HTTP/1.1 200 OK
Server: nginx-V-ddos
Date: Tue, 30 May 2017 10:24:52 GMT
Content-Type: text/html
Content-Length: 645
Connection: keep-alive
Keep-Alive: timeout=15
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Cache-Control: no-cache

Was this article helpful to you? Yes No