Hubspot hosted website proxy

[VoytechMedia]

Hello, 
devops team has setup website page (https://adventure.ziflow.io/) that is a mirror (reverse proxy) of a page hosted on Hubspot https://adventure.ziflow.com/ 

But it started to get redirected to original source website https://adventure.ziflow.com/  with no real reason. Devops team is saying thay they did not change anything in a proxy setup nor did I (Hubspot developer). Domain settings stayed the same for a long time. They say that this is Hubspot that make this redirection. 

They have also sent me an error log of what's the issue - Cloudflare is forcing the page to redirect, meaning Hubspot. Is there any way to set it up so the https://adventure.ziflow.io/ is served correctly with no redirection?

curl -v https://adventure.folderflow.com
*   Trying 13.32.151.74:443...
* Connected to adventure.folderflow.com (13.32.151.74) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* [CONN-0-0][CF-SSL] (304) (OUT), TLS handshake, Client hello (1):
* [CONN-0-0][CF-SSL] (304) (IN), TLS handshake, Server hello (2):
* [CONN-0-0][CF-SSL] (304) (IN), TLS handshake, Unknown (8):
* [CONN-0-0][CF-SSL] (304) (IN), TLS handshake, Certificate (11):
* [CONN-0-0][CF-SSL] (304) (IN), TLS handshake, CERT verify (15):
* [CONN-0-0][CF-SSL] (304) (IN), TLS handshake, Finished (20):
* [CONN-0-0][CF-SSL] (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / 
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=adventure.folderflow.com
*  start date: Feb 21 00:00:00 2023 GMT
*  expire date: Mar 22 23:59:59 2024 GMT
*  subjectAltName: host "adventure.folderflow.com" matched cert's "adventure.folderflow.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M02
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* h2h3 [:method: GET]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: adventure.folderflow.com]
* h2h3 [user-agent: curl/7.87.0]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x156011e00)
> GET / HTTP/2
> Host: adventure.folderflow.com
> user-agent: curl/7.87.0
> accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 301
< content-length: 0
< location: https://adventure.ziflow.com/
< date: Tue, 05 Sep 2023 10:21:29 GMT
< cache-control: s-maxage=3600,max-age=120
< strict-transport-security: max-age=31536000; includeSubDomains
< content-security-policy: upgrade-insecure-requests
< x-hs-https-only: worker
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=LtdTWqHuTamlCDbAHDrOB4JWysON4wnd3LKP1TjKKxghw0fKMOc3WVM0X612ql%2B4R%2FsEh7uzXUpnhAOrdt1OEoBRJxfAZvQjXpN0"}],"group":"cf-nel","max_age":604800}
< nel: {"success_fraction":0.01,"report_to":"cf-nel","max_age":604800}
< server: cloudflare
< cf-ray: 801d9c15848-IAD
< x-cache: Hit from cloudfront
< via: 1.1 2cfc0bae5f623e1c8.cloudfront.net (CloudFront)
< x-amz-cf-pop: IAD66-C2
< x-amz-cf-id: UKwr9APQbH33U_bu5H9vgVkYTI12fYuJGPU5BKYg==
< age: 694

I changed some of the long chains of characters for the security reasons. I would really appreciate any hint about this. My devops team also said they were using this manual to handle this https://developers.hubspot.com/docs/cms/developer-reference/reverse-proxy-support and it didn't help. There might have been something on Hubspot system that has recently changed and maybe denying access to that proxy.