DNS and Nameserver question

Website Building
#5

Ok so I followed the instructions to set up cloudflare DNS. The nameservers are redirecting but I don’t think the cname is working.

I’m still getting a not secure website message. (The Https isn’t working).

Do the nameservers and the cname propagate differently?

Is there a way for you guys to tell me whether or not everything looks correct and I just need to wait for 24 hours as I’ve seen be the solution many times here in these posts?

Also instead of my domain “pointing” to my website it says its parked. Is this an isssue? I clicked add domain and clicked the radio button for point to, however it still remains at parked.

Thanks for all your time and help, sorry to be a pest

#6

WebhostDash
WebhostDash.jpg1074×255 25 KB
NameServersCloudFLare
NameServersCloudFLare.jpg1127×493 65.2 KB
NameServersGoDaddy
NameServersGoDaddy.jpg750×307 21.6 KB

#7

Unpark the domain from the cPanel, and use the point domain instead :slight_smile:

#8

it wont let me unpark even if i delete it out. It stays parked

#9

I removed it, try pointing it now :slight_smile:

#10

Thanks I was able to point it, i think.

newwebhost
newwebhost.jpg1062×228 25.8 KB

will it still take some time for the cname to propogate?

1 Like
#11

Nope, you should be able to access it instantly :slight_smile:

#12

Yeah its having tons of trouble

I dont know what the issue is

ERR_TOO_MANY_REDIRECTS

now

trying to redirect this url has been nothing but a headache. I dont understand what I’m doing wrong. I’ve read and reread the tutorials and everything seems like it should work. However either my pages show up with what looks like no css or now even after clearing browsing data I get this ERR_TOO_MANY_REDIRECTS…

im at my wits end… I just want this to work so I can send my portfolio to prospective employers.

#13

https://dnschecker.org/#CNAME/danowens.me says my cname is bad i think

#14

Do you have always https plugin is wordpress? :slight_smile:

#15

Im not sure which https plugin youre referring to, I didn’t install one if so.

can you remove it? will it fix the problem?

I can’t even get into wp dashboard at this point

#16

webpage
webpage.jpg1536×821 222 KB

So as you can see my site seems to work but not https: even with the nameservers and all that. I dont know if you fixed it to this point and there’s still issues or what.

The other thing to take note is that the pictures on the page are not resizing and overlapping, not the intended design. I’m hoping that resolving the https and http has some sort of correlation to the sizes of the pictures being off.?

#17

webpage2
webpage2.jpg1536×821 90.5 KB

no css?

idk I spent a month learning how to make this thing hopefully I didn’t tank it.

#18

Ok so now everything is really messed up. I went into cloudflare and deleted my dns. I went into godaddy and changed nameservers back to default. and then i went into the cpanel for webhost and deleted the dns links.

I went into wordpress general and changed back to http://dan0.000webhostapp.com for the 2 urls

now when i try to go to dan0.000webhostapp.com - it still points to danowens.me and on top of that says the webpage has been deleted.

I was just trying to get everything back to default, cause it actually worked then.

Please help.

#19

DNS isn’t instant it can take up to 48 hours in some situations, it can be quicker using Google DNS or alternative DNS and flushing your cache and your browser history.

Set it up the way you originally wanted it to work and leave it for a day.

#20

i can’t even get to my page anymore to get to wp-admin to change it back if i wanted to

#21

Check this tutorial and let me know how it went for you

You can use database option if you are unable to reach your site.

#22

Ok so heres what I have

webpage3

My question is should i make the http:// or https:// here.

Also when browsing to my website if you use http://danowens.me it produces this:

webpage4
webpage4.jpg960×540 62.9 KB

which is kind of my webpage… the picture although constrained to 300x300px is obviously oblong (oval)

So using http:// thats what you get.

When you use https://
ie. https://danowens.me

this is what you get:

webpage5
webpage5.jpg969×540 24.7 KB

As per your suggestion I set up everything on godaddy, 000webhostapp, and cloudflare the way they were in the pictures. Meaning my site should be on https:// correct? does that then mean i need to change in wordpress from http:// to https:// and all is fixed, or did I royally f something up.

I’d be willing to pm you the logins to my accounts if that makes it easier for you. I have a job interview on wednesday I was hoping to have this for. I was finished building the actual site last night and was happy to have it done early. rofl. I think I’m possibly overthinking this way too much.

Thanks for your patience and help. It is greatly appreciated.

#23

I’ll look into this soon I’m swamped currently.

#24

No worries I think I have it figured out. I scoured the interwebs for hours to find several solutions which seem to have worked.

First off if your run cloudflare with wordpress, it’s imperative to download the plugin called “Cloudflare Flexible SSL”

I recommend setting up cloudflare and getting the certificate before messing with the addon.
After the addon is installed I had to go into cloudflare and go to crypto and turn it to always https://

After I used that all my pages started working as Secure, however my css and other scripts couldn’t load because they were being pulled in through http:// so there were a ton of mixed content warnings.

I don’t know if its the way that wordpress gets installed on webhost’s end or something else but the whole backend was in http:// instead of https:// originally. So the wordpress dash wouldn’t work at all.

Now with everything secure I could at least enter the backend. The frontend stuff wasn’t working properly it was pretty janky but I could get into the backend.

So at this point I downloaded the addon “better search replace” and searched for every instance of http://dan0.webhostapp.com/ and replaced it with https://danowens.me
http://danowens.me/ replaced by https://danowens.me
https://dan0.000webhostapp.com replaced by https://danowens.me
http://www.danowens.me replaced by https://danowens.me

There were a few other linkes i seached and replaced, everytime replacing with https://danowens.me

At this point 90% of everything worked flawlessly. I had to readjust some of the sizes of my pictures because for some reason the size constraints I had entered weren’t working. So I just resized the picture to the constrained size and called it a day.

I did go to freenom and cloudflare and played for a few hours setting up wordpress onto an already forwarded domain. I tried parking my freenom domain and linking just the nameservers, but once you install wordpress it immediately gives you “security errors”. I also tried pointing freenom and using cloudflare, then installing wordpress. Same issues with the non secure websites and the dash not working.

There has to be something with the automated installation of wordpress.

If you install wordpress with cloudflare on then go to general settings and change wordpress url and site address url to be https:// instead of http:// it immediately gives you too many redirects and you can’t even connect to the backend or frontend. You have to go in via the ftp and add come code to either your functions.php to manually set the siteurl and wordpressurl.

This is when I found “Cloudflare Flexible SSL” and my whole process started. After confirming it worked on the new site, I applied (everything above) the same fix to my portfolio site. And wallah.

Anyway hopefully someone might find this useful.

I still think there’s a problem with installation of wordpress onto a domain not 000webhostapp.com. I don’t know if you make it so when you’re choosing the url during the first step of installing wordpress if you can somehow have it push the https:// to the install directory but i think that’s what needs to happen. If you install wordpress onto 000webhostapp.com with no forwarded domains and login to the backend you notice its https:// secure and everything is gravy. Once dns becomes involved, changing the url or installing wordpress always puts the whole wordpress into http://

So let me clarify, for instance lets say I bought danowens.me point it to cloudflare and in turn point cloudflare to 000webhost. Lets say everything is working as it should, you have your certificate, when you type in the address it forwards you where you want. Now lets say you install wordpress. It will let you pick danowens.me as the URL during the installation, which sets up your siteaddress url and wordpress url to danowens.me now. However it doesn’t set it to https:// it sets it to http://

Now lets say you install wordpress on a fresh 000webhost.com site. No DNS or anything set up, just plain ol’ 000webhost.com. Meaning your siteaddress url and wordpress url will be something like yoursite.000webhostapp.com. However this installation ALWAYS stays in https:// and everything works great.
However whenever your add DNS if you don’t have SSL your site is going to be broken.

At least this was the case for me in this whole situation. If you could somehow choose SSL when installing wordpress onto a non 000webhost domain then that might solve it. I’m not familiar with how any of that stuff works though, so this is only my best guess at a solution.