Looks good, & seems quicker to me :-)

I did get a certificate error when following the 'edit car' link.



There is a problem with this website's security certificate.


The security certificate presented by this website was issued for a different website's address.

Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.
We recommend that you close this webpage and do not continue to this website.
Click here to close this webpage.
Continue to this website (not recommended).
More information


If you arrived at this page by clicking a link, check the website address in the address bar to be sure that it is the address you were expecting.
When going to a website with an address such as https://example.com, try adding the 'www' to the address, https://www.example.com.
If you choose to ignore this error and continue, do not enter private information into the website.

For more information, see "Certificate Errors" in Internet Explorer Help.



(Naturally IE is unhelpful and doesn't show the key certificate details).

pb
May 30, 2012
10:04 AM

hmm, I'm not seeing certificate problems. I tested in IE9 on Windows 7 and all is well. What browser/OS combo are you using? Have you tried clearing your cache?

This is IE8 on XP, via a corporate network.

I've tried refreshing (F5) both the start page & the destination page.

The certificate details are:
Issued to: ask.metafilter.com
Issued by: COMODO Extended Validation Secure Server CA
Valid from 15/12/2011 to 15/12/2013

Both pages show the '*' on the right-hand edge of the copyright line.

pb
May 30, 2012
10:51 AM

Thanks, I'm seeing the same problem in IE8 on XP too. Looking into it.

pb
May 30, 2012
11:32 AM

The technical reason for this problem is that IE8 and below on XP do not support Server Name Indication for secure connections. We're talking about potential solutions, but nothing will be a quick fix.

In the meantime, if you want to use Fuelly without certificate errors you can disable domain mismatch errors. You get there through Tools » Internet Options » Advanced » Security heading. And then uncheck "Warn about certificate address mismatch". Restart IE.

That will stop the errors, but it also makes your browsing slightly less secure. You have to take our word that we have the proper certificates, and you shouldn't have to do that. So we'll get this sorted out but there isn't a quick way to solve it.

pb
May 30, 2012
2:05 PM

For the time being we're not going to serve secure pages to IE on Windows XP. We don't have a way to fix this problem on our end without downgrading to a less secure certificate, which we don't want to do at this time. We're exploring some other options, but in the meantime just be aware that if you're using IE on XP you won't bet getting SSL pages for logging in or adding fuel-ups.

If possible, I'd recommending switching over to a newer version of Firefox on XP.

Normally I would be using opera, no certificate issues there

Possibly related to the recent server move... The past few days while using Android 2.3 on my smartphone, when navigating to m.fuelly.com I am redirected to the metafilter.com homepage.

pb
Jun 4, 2012
10:36 PM

Are you sure you have the right URL, RxZ? You'll get bounced to metafilter.com if you have an unmapped subdomain, like asdf.fuelly.com. But m.fuelly.com should be coming up fine. If you accidentally hit n.fuelly.com or mm.fuelly.com, that will bounce. But m.fuelly.com should work.

If it helps, m.fuelly.com works ok on my android (4.0.3) with Opera mobile & also the built-in browser.

That was with http://, I didn't try https://

pb
Jun 5, 2012
6:44 AM

We don't have a secure version of m.fuelly.com, so https:// isn't going to work. No need to try it.

Thanks for the suggestions. To clarify, I had a bookmark saved in my phone's browser that always worked, and I noticed about the end of last week that the bookmark started sending me to the metafilter.com homepage. When physically typing the address I got the same result.

However, I just cleared all the browser cache, and tried again, and it worked. So, problem solved, I just do not know why the previous link stopped working, unless the address changed when the server moved. In any event, it is a non issue for me now.

Thank you for putting together a great site, and for having excellent customer service!