Something on your mind? Want to give us feedback on something in particular or everything in general? Tell us how we are doing!
#12772 by Groundhound
Wed Jul 08, 2009 11:57 am
dmlanger wrote:Oh ok. It could be that your proxy server does not fetch pages that dont start with an <html> tag. What browser have u tried this in?

That frame is missing both the <html> tag and the <head> tag. Firefox renders it OK from behind the hub but Chrome does not.
#12774 by dmlanger
Wed Jul 08, 2009 12:10 pm
Yea ok same thing. It has nothing to do with your local proxy then, it's just the incorrect coding.
#18568 by dmlanger
Tue Sep 01, 2009 10:19 am
This has been almost a year since this bug and i have provided the 2 line solution! Why hasn't it been fixed yet?!
#18582 by ggilman
Tue Sep 01, 2009 11:57 am
Not disagreeing that it should get fixed, but where do you get the year from? The original post was just over 2.5 months ago & Google Chrome was released to the public less than a year ago.
#18592 by dmlanger
Tue Sep 01, 2009 1:59 pm
it was in another thread before that as well as private messages with the mods and documented over the phone and through email customer service.
#20388 by MWPollard
Tue Sep 15, 2009 8:30 pm
Ummm, I've been using ooma on Chrome for some time. I get errors that Chrome can't verify the security certificate (very annoying), but the page loads.

Might want to make sure you're using the latest Chrome build. Go to Tools (wrench) and About Google Chrome; if there's a new version, it'll tell you. Speaking of which, a new update just came out, so it should tell you.
#20394 by dmlanger
Tue Sep 15, 2009 8:43 pm
Nope. Have the update, i never get a security error. I just get the page missing the <html> and <head> tags. U can verify this by checking source as well as in other browsers.
#23851 by tailwheel
Sat Oct 03, 2009 5:43 pm
MWPollard wrote:I get errors that Chrome can't verify the security certificate (very annoying), but the page loads.

I get this message on every page load in my ooma. Pages seem to load and work properly but annoying. I can disable "Check for server certificate revocation" in options and the message goes away but doubt it's a good/secure way to run. I've been using Chrome quite a bit since 3.0 came out and I don't think I've seen this message pop up anywhere else.
#27815 by dmlanger
Tue Oct 20, 2009 1:19 pm
Seriously this is absolutely ridiculous. This bug has been here since day 1. I've even posted a solution/fix. How hard is it to implement it? If no one at ooma wants to do it, send me the firmware code and i'll do it myself.

Who is online

Users browsing this forum: No registered users and 7 guests