# Reverse Proxy stopped working

**URL:** <https://community.hubspot.com/t/reverse-proxy-stopped-working/94562>\
**Category:** CMS Development\
**Tags:** professional\
**Created:** [November 22, 2023, 10:29am UTC](https://community.hubspot.com/t/reverse-proxy-stopped-working/94562 "2023-11-22T10:29:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![SGRL23](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sgrl23/32/200671_2.png) [@SGRL23](https://community.hubspot.com/u/SGRL23)\
**Post date:** [November 22, 2023, 10:29am UTC](https://community.hubspot.com/t/reverse-proxy-stopped-working/94562/1 "2023-11-22T10:29:22Z")

</div>

Hello!

My team has had a test site setup using a reverse proxy for a few months now. Noticed near the end of October than it stopped working.

Errors are SSL handshake related. I believe it’s because the hubspot domain we’re proxying to doesn’t have our domain on the certificate.

Anyone else running into this? I’ve tried emailing hubspot support and not gotten a response.

Here is the output from openssl client

`openssl s_client -connect XXXX.sites-proxy.hscoscdnXX.net:443 -servername OURDOMAINCONNECTED(00000006)001E1CFA01000000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:ssl/record/rec_layer_s3.c:1586:SSL alert number 40---no peer certificate available---No client certificate CA names sent---SSL handshake has read 7 bytes and written 321 bytesVerification: OK---New, (NONE), Cipher is (NONE)This TLS version forbids renegotiation.Compression: NONEExpansion: NONENo ALPN negotiatedEarly data was not sentVerify return code: 0 (ok)---`