Hmm, just checking the forum and seeing there were posts made in the days the website was down. So that's weird. Was it down for some people but not others?
it worked for me, but some people said it didn't work via http (an unencrypted connection)
That might have been it! Weird, I thought my internet automatically went to https when I go to a website but I just checked and somehow that wasn't happening for libcom :(
I better remember to pay attention to that in the future, don't want to be using http when logging in
Our blogs had similar issues recently and I don't know if it applies but it's down to that some
browsers warning the user whenever they visit a website via HTTP instead of HTTPS.
I had to configure the blog to redirect HTTP traffic to HTTPS. This was a simple matter on Blogger in changing the settings for the blog. Don't know for yourselves.
hmm it was okay for us. Sorry about that. The main thing is to always make sure you visit the secure HTTPS version of the site: https://libcom.org
and if you ever want to check if the site is down for everyone or just you, you can go to: https://downforeveryoneorjustme.com/
I think, as has been said before, the server was rejecting connections via unsecure HTTP but accepting them via secure HTTP.
I also thought my browser automatically connected to HTTPS but that was not the case, so I installed this browser extension from the Electronic Frontier Foundation. May be useful for others too.
Yes http was down, but https was up - and it took a while for us to notice sorry (probably because most people are using https these days, but google hasn't always caught up).
On the http/s stuff, how does it work with phones? Idk about anyone else, but I tend to assume that phone browsers are less likely to be customised, I have various adblocks and other plugs for my laptop browser but just running the basic on my mobile. Am I right in thinking that the majority of phone traffic would probably be http rather than s?
I think it depends where the phone traffic comes from, whether someone follows an https link or not.
New version of the site (extremely slow progress, but actively being worked on and pace is picking up finally) will be all-https and on different hosting entirely, so this problem will go away although I'm sure we'll find some new ones.
When you start your browser and attempt to access Libcom are you coming from a saved bookmark? Is this bookmark older? Possibly from before Libcom was using https encryption? If so, then you might want to check and see if the bookmark that you are using to attempt to access the site is not written using an unencrypted referer header http as opposed to https, and if the bookmark is saved as an http rather than an https link then you might be able to solve the problem by editing the bookmark and retyping and saving it as https://libcom.org
Now if I try to access via https, I'm currently getting a message saying "Bitdefender has blocked this page. Your connection to this website is not safe due to expired certificate and was blocked. Attackers might try to steal sensitive information from you, such as passwords or credit cards." Which doesn't come up using the non-https route.
Hmm, just checking the forum
Hmm, just checking the forum and seeing there were posts made in the days the website was down. So that's weird. Was it down for some people but not others?
It was down for me too. What
It was down for me too. What day/s did you notice it?
I had an issue connecting for
I had an issue connecting for a few days using my usual bookmarks and cached links.
But I googled Libcom and got in that way.
Seems fine now.
A bit odd.
I forget when I first noticed
I forget when I first noticed it but I think from about the middle of the week until yesterday.
Yeah, was down for me too.
Yeah, was down for me too.
it worked for me, but some
it worked for me, but some people said it didn't work via http (an unencrypted connection)
radicalgraffiti wrote: it
radicalgraffiti
That might have been it! Weird, I thought my internet automatically went to https when I go to a website but I just checked and somehow that wasn't happening for libcom :(
I better remember to pay attention to that in the future, don't want to be using http when logging in
I could log in on Firefox but
I could log in on Firefox but not Chrome.
Our blogs had similar issues
Our blogs had similar issues recently and I don't know if it applies but it's down to that some
browsers warning the user whenever they visit a website via HTTP instead of HTTPS.
I had to configure the blog to redirect HTTP traffic to HTTPS. This was a simple matter on Blogger in changing the settings for the blog. Don't know for yourselves.
hmm it was okay for us. Sorry
hmm it was okay for us. Sorry about that. The main thing is to always make sure you visit the secure HTTPS version of the site: https://libcom.org
and if you ever want to check if the site is down for everyone or just you, you can go to: https://downforeveryoneorjustme.com/
I think, as has been said
I think, as has been said before, the server was rejecting connections via unsecure HTTP but accepting them via secure HTTP.
I also thought my browser automatically connected to HTTPS but that was not the case, so I installed this browser extension from the Electronic Frontier Foundation. May be useful for others too.
https://www.eff.org/https-everywhere
Just installed it. Thanks,
Just installed it. Thanks, Darren. I notice "Encrypt All Sites Eligible" is off by default. Would you recommend turning it on or no?
Yes http was down, but https
Yes http was down, but https was up - and it took a while for us to notice sorry (probably because most people are using https these days, but google hasn't always caught up).
On the http/s stuff, how does
On the http/s stuff, how does it work with phones? Idk about anyone else, but I tend to assume that phone browsers are less likely to be customised, I have various adblocks and other plugs for my laptop browser but just running the basic on my mobile. Am I right in thinking that the majority of phone traffic would probably be http rather than s?
I think it depends where the
I think it depends where the phone traffic comes from, whether someone follows an https link or not.
New version of the site (extremely slow progress, but actively being worked on and pace is picking up finally) will be all-https and on different hosting entirely, so this problem will go away although I'm sure we'll find some new ones.
Lucky Black Cat wrote: I
Lucky Black Cat
What I found out through Reddit: "If you don't check, you can visit both HTTP and HTTPS sites. If you check, you can only visit HTTPS sites"
darren p wrote: Lucky Black
darren p
what actually happens is if you try to visit a site and it cant find a https version it warns you and asks you if you really want carry on
I installed it but it isn't
I installed it but it isn't working for me, even with the "Encrypt All Sites Eligible" checked. Oh well. Thanks anyways.
Sorry do you mean that libcom
Sorry do you mean that libcom still isn't working? Or wasn't again for a time?
When you start your browser
When you start your browser and attempt to access Libcom are you coming from a saved bookmark? Is this bookmark older? Possibly from before Libcom was using https encryption? If so, then you might want to check and see if the bookmark that you are using to attempt to access the site is not written using an unencrypted referer header http as opposed to https, and if the bookmark is saved as an http rather than an https link then you might be able to solve the problem by editing the bookmark and retyping and saving it as https://libcom.org
Steven. wrote: Sorry do you
Steven.
I meant the browser extension HTTPS Everywhere. (Though now the extension is working for me.)
Okay thanks for clarifying!
Okay thanks for clarifying!
Now if I try to access via
Now if I try to access via https, I'm currently getting a message saying "Bitdefender has blocked this page. Your connection to this website is not safe due to expired certificate and was blocked. Attackers might try to steal sensitive information from you, such as passwords or credit cards." Which doesn't come up using the non-https route.
We did have a problem with
We did have a problem with the secure site briefly, but hopefully that should now be fixed