Mobile app version of vmapp.org
Login or Join
Rambettina238

: Example.com gets invalid url but www.example.com works great I am new to the web mastering stuff so please bear with me. My problem is that I have a domain example.com. If I go directly to

@Rambettina238

Posted in: #Cloudflare #Godaddy

I am new to the web mastering stuff so please bear with me.
My problem is that I have a domain example.com. If I go directly to it I get an invalid url error, however example.com works just great.
Here is the error message

Invalid URL

The requested URL "[no URL]", is invalid.
Reference #9 .b20fdd58.1490883354.a0914c3


We're using GoDaddy for domain, cloudflare for dns and hubspot for hosting some parts of our website.

So in GoDaddy I have my example.com. It has nothing set on it except the nameservers for the cloudflare. In cloudflare I have set a cname of example.com to be an alias of example.com Here are some server congfigs that probably might be relevant. There is this thing called cname flattening that happens. Also interestingly enough if I go to the hubspot url where my example.com is redirected it gives back the same error.


And in hubspot I have my example.com to be primary for content tools and then all the hubspot urls are redirecting to example.com.
Please help me and thank you all very much!

10.02% popularity Vote Up Vote Down


Login to follow query

More posts by @Rambettina238

2 Comments

Sorted by latest first Latest Oldest Best

 

@Debbie626

The problem was that Hubspot works only with urls that have So there should be domain forwarding for root to go to Doing it with GoDaddy is just a breeze. However in cloudflare there is no domain forwarding but there is url forwarding. I've set url forwarding and made the dns record to be processed by cloudflare (the orange cloud in the cloudflare). Thus the issue was solved.

10% popularity Vote Up Vote Down


 

@Mendez628

You need to create an A record with the IP of the webserver. This is because the bare hostnames with just domain.com can't be CNAME. Here is what you do:
Ping the working address with www:

ping secretexample.com

Ping the non-working address without www:

ping secretexample.com


If they show the same address, or just the last number differs (round robin), the problem is in the shared hosting and you shouldn't try fixing it in the domains.
If the second example fails, add the A record with the IP obtained from the first ping with

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme