non www works fine but www does not…

I searched and searched and maybe I set this up wrong… was I suppose to start with www and redirect to non www… I’m a bit confused.

I’m using server IP instead of cname, is that a poroblem?

I’m using server IP instead of cname, is that a poroblem?

No. Can you describe how it “breaks”?

i get the following error in chrome: Err name not resolved, page cannot be found…

to be more specific, when i go to the domain with www I get the error: Err name not resolved, page cannot be found… when I go to the domain without the www it works just fine…

Name not resolved means that the www is not set up in your DNS.

Hi Ron,

I think there’s a big issue since the last update of Google Chrome. With older versions there is no problem. When updating Google Chrome to the latest version (44.0.2403.89 (64-bit) i get an error that the name is not resolved, and the page cannot be fount.

Also when i try to log-in at a site i get the message that i doesn’t use a private connection.

Serious troubles. Many of our clients aren’t happy. Our DNS settings haven’t change and are correct. Also www is configured correctly.

Note: This issue doenn’t show up in Safari, Firefox, Internet Explorer en some olders versions of Google Chrome.

In that case there probably isn’t anything you can do about it from the webserver end.

I was talking to someone else in the last day or so & they were having weird problems with Chrome as well (unrelated to DM). They restored a backup & that fixed it. That sounds to me like it might be an update that didn’t apply correctly or similar.

Thanks for your reply. We’ve found an fix; it’s a combination of WooCommerce with a change in Google Chrome. Fix: update WooCommerce, see here:

https://www.ads-software.com/support/topic/site-broken-in-chrome-ssl-issue?replies=63

Thanks for posting that. I handed the link to this thread on to the person I mentioned above.