Kevin's Watch

^ What WF said!!

Vain wrote:Urgh! I got guilt-tripped by Avatar into lifting my lazy butt and getting things sorted so voila....the site is now secure!

The disk space was also used up - thanks to the 3Gb error log file! So it should theoretically work better now....

Woah, glad you caught that!

And THANK you for updating it to https, Vain!
(and thanks for guilt-tripping, Av)

I was chatting with a new acquaintance online, sent him here to show him something.
I was all prepared to tell him, "btw, if you get an error message, don't worry; it's just b/c the site doesn't have https" when...
...lo and behold, I tested it myself on a whim and it DID have https!

It's snaaaazzzzzy!

Welp, I retired, and I moved to Santa Fe, and now I have CenturyLink as my ISP, and I have now gotten a "NONE SHALL PASS" message from them that McAfee has listed the ihugny domain as malicious twice. And I've only been here for a few minutes. :\

Wish there was a way to disable that bloody warning or whitelist the Watch or something. Ugh.

Well hell, just wander in huh?

You should be able to whitelist it. (Or disable it, but that would disable for everywhere probably.) Don't think we can get them to remove it, since I suspect other (sub)domains on this server may have at some time been a bit dubious.

Will ask Vain.

--A

Avatar wrote:Well hell, just wander in huh?

You should be able to whitelist it. (Or disable it, but that would disable for everywhere probably.) Don't think we can get them to remove it, since I suspect other (sub)domains on this server may have at some time been a bit dubious.

Will ask Vain.

--A

I thought I'd stop by, yeah.

This ISP has this McAfee Secure Wifi thing built into their platform. If you're a customer, you get it whether you want it or not. I definitely don't; it's causing other problems for me. I called to get them to disable it and they deflected me by saying my service was slower than I was paying for, so they'd send out a tech. Well, the tech has come and gone, and presumably the speed issue is fixed, but of course that didn't fix my access issue because the problem is McAfee.

I could ask them to whitelist the Watch, but I'm guessing (based on what happened when I had the same issue at the office) that when McAfee updates, we'll get blacklisted again. No, the answer is to get the ISP to take this bloody thing off my service. If I wanted McAfee, I'd *have* McAfee and not AVG - which btw I can't get to update because (I'm pretty sure) their bloody McAfee virus thingum is blocking it.

I guess I get to call them again this week. Joy.

--A

Update: YAY! I just spent about 12 quality minutes on the phone with CenturyLink (5 minutes of which consisted of wading through their voicemail prompts ) and convinced the tech I spoke with to remove McAfee from my modem. Got to the Watch just fine just now, and Daz Install Manager is updating as we speak.

Cool.

Weird, never seen something like that built into the modem itself.

--A

So in theory there are no excuses now Ali?

Good point StevieG, good point.

--A

Sometimes I just do your work for you

At least somebody is doing it...

--A

Skyweir wrote:

Lazy Luke wrote:

Skyweir wrote:

wayfriend wrote:

Lazy Luke wrote:

Skyweir wrote:

Not sure if this is happening for anyone else, but Chrome is displaying this whenever I log in to kevinswatch.

As far as I can make out, this happens because somewhere http is used instead of https.

Some info is here: https://bugs.chromium.org/p/chromium/is ... id=1158169
It's new with Chrome 86. It may be a while before people hit it, depending on how fast they upgrade.

It seems that the issue is that the login.php response contains a Location header which indicates http.

Of course, I have no idea how to translate that into something you can do in php. Maybe someone does tho.