Redirecting a Dummy URL to a personal Zoom room

General Rules
1

What is the name of the domain?

example.com

What is the issue you’re encountering

Redirect not working

What steps have you taken to resolve the issue?

I have a website hosted elsewhere - which is working fine, cloudflare directs traffic to it just fine.
Now I’d like to add a dummy URL to forward traffic to my personal zoom room. Eg, www.mydomain.com/zoomchat should forward to https://us04web.zoom.us/j/4083458404
I have tried using Page Rules and Redirect Rules with 301 redirects but it will not work. Traffic seems to be forwarding to the default website and then 404’s. Do I have to do this at the webserver side? I have added the 192.0.2.1 A record, proxied it but I can’t change the CNAME - which is pointing to the webserver. Anything else I can try? I tried bulk, but that did not work.

2

Welcome to the Cloudflare Community. :logodrop:

I would use a single static redirect rule for this. It will need to use a :orange: proxied hostname. You probably already have that since you have an existing website.

Match on the hostname and the URI path.

http.host eq "www.example.com" and http.request.uri.path eq "/zoomchat/"

You may need to adjust adjust the selection critera a little to meet your needs, but the above should get you close.

You know the redirect URL already.

3

I’ve already done that and tried it at the redirect and page rule level. See pic attached. OR am I getting it wrong?

zoomchat
zoomchat2208×1634 200 KB

4

You will need to share your domain name in order for the Community to check your work.

You may want to loosen your match criteria. Try contains instead of eq.

You can see what happens to your request using Cloudflare Trace.

1 Like
5

I was able to get it working with another domain I own. The issue seems to be with the Proxy switch for A & CNAME records and Vercel.com - the webhost. I have read of issues with Vercel and will reach out to them to try resolve, unless anyone lese has found a solution.

6

issue has been resolved by enabling SSL Force and by proxying all A & CNAME records. But now DNS resolution takes MUCH longer - like ~20 seconds. :\ Homepage comes up eventually, but it’s super slow. Trace did not show me much that was helpful.