|
|
Cisco Umbrella protecting me from myself... |
Towards the end of August,
my ten year old modem
gave out and off we went on a wild ride to get a new one installed. I won't
bother with details of the assorted issues that we had to deal with to get
up and running again, but midway through the process, I found myself blocked
from my own blog. What?!
A message of "Your connection is not private. Attackers might be trying to steal your
information from esheepdesigns.blogspot.com (for example, passwords,
messages, or credit cards). Learn more about this warning
net::ERR_CERT_AUTHORITY_INVALID" came up and stopped me in my tracks when I typed my URL into my browser.
To make matters worse, while I've encountered similar notices on other sites
in the past, there had always been an option to "proceed at your own risk," so
to speak. None here; no button to click to go any further. The only way to
bypass the actual screen was to change https to http in the URL,
but that only gave me the screen that you see above.
I'm not here to give a lengthy technical explanation on what the problem was and what the eventual solution entailed. Let me just say that it came with our new modem, which apparently was configured to go through Cisco Umbrella, which is a DNS-layer protection service that identifies and blocks potentially "bad" internet traffic before a connection is made.
Services like this have both positive and negative results. On the positive side, most of us want to have malware and phishing sites identified so that they don't harm us; I get that. But inaccurate flagging can wreak havoc with legitimate businesses – with actual financial consequences – which is decidedly negative. Luckily I am not in this to make a living, but I can imagine how someone who is might react to being arbitrarily blackballed by such a service.
|
| Had to submit a trouble ticket to try to reverse this decision... |
I'm not sure how a site gets identified by Cisco, especially small-time
entities like my blog (which is hosted by blogger.com; I don't even have my own domain), but ordinary folks like you and me can
report a site to them. Which then begs the question: did someone
maliciously report my blog?
If Cisco itself actually goes out and parses random code, might it have
stumbled onto my blog and found some tiny script somewhere that it determined
to be potentially harmful? I don't know. I do know that my blog makes
use of widgets written by others (if you view my blog on a desktop, you'll see
the left sidebar where they all reside), but they are all innocuous things
that have been used since forever and are in no way employed for phishing
purposes. The two widgets that actually ask for an email address are the ones
for subscribing to my blog and for contacting me. They aren't being used in
any devious fashion to try to trick visitors into giving up their information
to a bogus site. (They aren't even "in your face" the way some sites are;
i.e., the ones that use pop-ups to get you to sign up upon entering.)
Three days after encountering this difficulty, I registered an account on
Cisco, just so I could submit a trouble ticket. (Merely clicking on the link
to "Report an incorrect block" – that is clearly shown in the middle of the
screenshot at the top of this post – just results in an error message.) In the
meantime, my site currently has a web reputation of "untrusted"... somewhat
ironic considering
what AI came up with several weeks ago.
Of course, I still had the problem of not being able to load up my own site.
😖
I had already established that not being able to see the site wasn't a blanket issue. My Google Analytics stats were still showing visits during the entire time that I was blocked, so I knew that it wasn't affecting everyone. Still, the fact that it was affecting anyone was a concern; therefore, I made it a priority to log the issue with Cisco first before I took time out to look into how to fix my own problem.
After I submitted my ticket, I did some digging online and arrived at a
solution to my dilemma. By changing DNS settings on the modem, I was able to
circumvent Cisco's flagging of my blog on my own devices. It was a happy
moment when I saw my blog load up again. (For the sake of anyone coming to
this post in future to seek an answer to this issue, if your modem DNS
settings cannot be changed, apparently if you change your
device's DNS settings, they will override whatever is on the
modem. I will not get any more detailed than that since there several online
sources that will guide you through the required process.)
|
| Cisco's resolution of my ticket... |
It was Labour Day weekend when I submitted, so I did not get a response until
the Tuesday following. It appears as though at some point, everything will be
well again. The resolution does not indicate how the situation originally came
to be, so there is no guarantee that this won't happen again.
Knowing that there are others who are locked out by a security application
that they may not have chosen to employ is frustrating to say the least. To
answer my own question from the top of this post, this was definitely too much
protection, being done for seemingly arbitrary reasons.
And Now for Some Good Stuff...
Amazingly enough, during the time that I was having these technical issues, I had a couple of good surprises. (It actually took ten days for us to be up and running with a new modem. Fortunately – unlike ten years ago when we had limited alternatives when it comes to internet access – the data allotment on hubby's and my cell phone plans were sufficient to keep us comfortably functioning.)
The first "wow" came from finding out that I had sold eleven rolls (!) of wallpaper via Spoonflower. Then it was discovering the most heart-warming detail about the two transactions: the designs...
![]() |
| Mockup images of Just Sheep wallpaper courtesy of Spoonflower... |
For those of you who weren't around when I created Just Sheep over five years ago, it was the ultimate realization of a goal that I had had since I first dabbled in surface design: a representation of sheep that had nothing to do with wool and knitting that could be the thematic marker for my "brand". I've been pleasantly surprised by its reception, since I've sold some of it as fabric, but nothing has approached this level of appreciation.
Two days later, I received notice of another surprise purchase that was similarly gratifying: seven yards (!) of my original Pride & Prejudice fabric in organic cotton sateen via Etsy. Needless to say, I am extremely curious as to what these items will ultimately look like/be turned into, but unfortunately, it's not common for folks to contact me after such purchases. 😞
But it's always nice to have my work be supported. Many thanks to anyone and everyone who has done so over the years!
Oh, and to my handful of Canadian readers, have a peaceful Thanksgiving weekend. 🥰





























