Reverse Proxy Support

Developer Support CMS Development
1

Hello,

i am trying to test the new Reverse Proxy Support with an nginx proxy server to redirect only www.mydomain.com/blog to hubspot.

I did the steps mentioned here reverse-proxy-support

My problem is that after doing the steps all requests will be directed to hubspot instead of my proxy server. which means even www.mydomain.com will also be directed to hubspot.

My questions are:

  1. Can i achieve that only with a different subdomain than www?
  2. In the steps “For example, if your HubID is 123, your correct origin CNAME would be 123.sites-proxy.hscoscdn20.net” I can off course get it but dont understand where do i have to put this “origin CNAME”
2

Hi @Kenan,

Thanks for getting in touch!

I’ll answer your questions below:

  1. Due to the way HubSpot configure domains and that we advise on the use of CNAME records, it is recommended that you use the subdomain www instead of a ‘naked domain’.
  2. This is just referencing the origin CNAME record i.e 123.sites-proxy.hscoscdn20.net - In this case, this record is added in the following step to configure your proxy to forward requests using this origin CNAME.

I hope this helps!

3

Hi @Willson,

Thanks for your answer. We already got that fixed and its working like a charm.

4

Hello @Kenan,
can you provide more information on how to do that?
thank you

5

Hi @Kenan , I am also facing the similar issue, can you please guide us for the solution.

6

Hi @Willson,

I am sorry to write 2 times but i also have another problem. In my company we are trying to test the Reverse Proxy Support from HubSpot so we can offer it to our customers. The first Test was from an Nginx server and it worked. now we are trying to do the same but from an Azure server. and the server’s ip address was blocked from Hubspot after the first request. How could we unblock it?

Thanks in advance

Kenan

7

Just chiming in here because we’re currently trying to set up reverse proxying from Fastly to HubSpot and run into the same problems. It seems that HubSpot doesn’t recognize our test-subdomain (e.g. hubspot.example.com) as such and wants us to change the settings on DNS/domain level (which renders the reverse proxy in between useless). Following the documentation from here Accounts Dashboard | HubSpot goes sideways at step 10, it never shows this text “It looks like this domain already has an SSL certificate from another provider” and thus allowing us to enter the txt/cname records to validate the domain. Did anyone else encounter an issue like that?

Best regards,

Matthias

8

I had a similar issue with reverse proxy setup. To keep only blog routed to HubSpot, make sure your nginx config specifically targets that path. Also, the origin CNAME is used in your proxy rules to point requests to HubSpot it’s not added in DNS but used internally in the proxy setup.