Website only accessible via “xxxxxxx.com”; 500 error as “www.xxxxxx.com”

  • Hey all! Been kind of stumped with a friends website. I would normally assume a problem like this was related to bad a and cname configuration, but alas I’ve been told it is a problem with the .htaccess configuration in WordPress. I’ve read instructions here but am not sure if it applies, or if I would end up breaking it/fouling the sites SEO.

    https://wordpress.stackexchange.com/questions/256038/htaccess-https-redirect-from-www-to-non-www

    My friends want their website to be accessible by people typing both “arnoldjewelers.com” and “www.arnoldjewelers.com”. As it is, trying to append “www.” to the root url throws back a 500 error.

    We’ve had a few “wordpress” experts look at it only to be stumped a few hundred dollars later. Before we go spending more cash I would like to get a second opinion from you fellows here ??

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)

  • A 500 error says the server doesn’t know what to do with that…

    So, I’d make sure that server knew what to do with that name it sees under HTTP 1.1 after the DNS tosses the Cname to the resolver because it looks like the server doesn’t quite know what to do when it is handed a ‘www’ well-known service name (you might call it a subdomain even though it’s not really).

    Also, the way that is handled in DNS, you should see the canonization of the root domain in place of the domain with ‘www’ so don’t be disappointed with that when it does begin to work… After you fix things.

    I’d probably ask the host (GoDaddy?) for some help or else do what is needed to cause www + domain name to point to the WordPress directory where WordPress should know what to do next.

    It still needs the control panel (server) to deal with the ‘www’ even though it seems to disappear.

    Or you can just change the Cname to an A record where you’ll need to fix the server (via the cpanel) anyway. You can then change it back to a Cname to fix the canonization again.

    There’s a lot of terminology in this answer but I’m trying to cover the different terms to maybe help anybody with this same problem later.

    Thread Starter sschneikart

    (@sschneikart)

    A 500 error says the server doesn’t know what to do with that…

    So, I’d make sure that server knew what to do with that name it sees under HTTP 1.1 after the DNS tosses the Cname to the resolver because it looks like the server doesn’t quite know what to do when it is handed a ‘www’ well-known service name (you might call it a subdomain even though it’s not really).

    -Godaddy themselves were the ones to say it is a wordpress issue after going through my a and cname configurations. They then offered their premium “wordpress” support. Go figure!

    Also, the way that is handled in DNS, you should see the canonization of the root domain in place of the domain with ‘www’ so don’t be disappointed with that when it does begin to work… After you fix things.

    -Got that no problemo, expecting that. Good looking out though!

    I’d probably ask the host (GoDaddy?) for some help or else do what is needed to cause www + domain name to point to the WordPress directory where WordPress should know what to do next.

    -They were pointing the finger at WordPress last I talked to them on the phone. Said it was a fairly simple problem to fix but that they wouldn’t touch it without additional paid services.

    It still needs the control panel (server) to deal with the ‘www’ even though it seems to disappear.

    Or you can just change the Cname to an A record where you’ll need to fix the server (via the cpanel) anyway. You can then change it back to a Cname to fix the canonization again.

    -Concerned it may cause a problem with SEO, is that concern founded in any way? Thank you for all your responses ?? Lots of info to crunch.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Website only accessible via “xxxxxxx.com”; 500 error as “www.xxxxxx.com”’ is closed to new replies.