Mint Forum

I want to start out by saying that I love Mint. I bought the original as soon as it was released, and upgraded to the new version as soon as it was available.

However, Mint V2 has absolutely wreaked havoc on my website.

When I first installed it I had the issue with IE 6 sp2 users getting TOTALLY BLOCKED from the website. I spend 2 days trying to figure out why a seemingly random 40% of my customers were unable to see the website. I never suspected Mint because the error was so weird, but sure enough it was the culprit.

Now I have just spent 2 more days trying to find the source of the ‘Domain Name Mismatch’ error that people were seeing on IE6 IE7 and FF 2.0 when they entered the secure part of my site.

They would hit https://domain.com and receive the error - “You are trying to establish a connection with domain.com when the certificate is issued to domain.com”. The url had no www in it but the browser was calling the page domain.com. I went through my code, my server setup, and my collocated facility configuration trying to find somewhere, anywhere where my site was called domain.com.

Just now I looked in my Mint prefs and found that I had called the root of my site domain.com. I removed it and the problem is gone. Sure I entered it, but never in a million years would I think that could cause such a major problem.

The only reason I am taking the time to type this up is because I really like Mint, I love the price, and I want to see it succeed. But I am removing it from all serious websites, and recommending to my developer friends that they do the same until the code gets tightened up a bit.

-Mike Swimm

An outrageously over-the-top action.

Sam, I notice you do not even comment on the first issue. I think most business owners would consider blocking out 40% of their customers a pretty major problem.

Sounds like a simple user error, SSL certs have always been very pernickety about things like this. One would have assumed this would have been easy to spot considering you are more than likely calling Mint from the unsecure location in the HTTP as opposed to a secure version in HTTPS.

Did you even read my post? The error was not the “this page contains both secure and unsecured items” error. That would have been extremely obvious.

Accidentally adding ‘www’ to the url in my prefs caused the site to display itself to browsers as ‘www’ domain.com instead of domain.com. That caused the certificate (registered to domain.com without the www) to not match and IE to throw all kinds of nasty errors.

I will happily demonstrate this to anyone who would like to see it in action.

It seems the text filter on this forum cut all the ‘www’s’ off my first post making it difficult to understand.

The past months I got various complaints from people not being able to reach my site. They got the error “could not connect” and couldn’t reach any page of my site. Today I discovered this was caused by Mint. After I removed Mint (the javascript call) all problems where gone.

Wizard, I don’t know if this is a major overreaction. Every visitor Mint blocks, is a visiter less, which means, less profits for your site.

At this moment I’ve disabled Mint and I’ll be installing a fresh install soon.