Google Chrome

[Pogo]

Okay I can see no option to allow me to Disable SSL Certificates.

I can find mine under Settings/Advanced, but I'd like to know more about what risks it puts on me for other sites

ED - actually I can find where to go into SSL settings but what to do once in there is not at all clear. It does however offer a "Learn more about certificates" box which opens up a three-year course on the arcanities of all kinds of crapola I had no intention of spending my Sunday learning....

Google stopped support for SSL 2.0 with Google 38, if 2.0 is selected that could be the problem but the primary trick (as one tech put it) is "update your $(&^%$#$^ browser......."

Thank you to ALL my shining Knights in the sexy armour yesterday this they for taking time to assist a girl in confusion about confusing situation in Google Chrome, I do love ALL of you

Also to Kat I thank for her saying to me to get Opera Browser.

Yeah but how'd you like the stripper pics?

I think the same thing is still going on. Had to navigate the error message again today when I first went on. I suspect if I don't post for a while it will reappear as it did yesterday.

Still curious that the site has nothing to say about it though.

It's your browser, not the site. Your browser is trying to redirect to a secure https connection that the site doesn't even use.

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

 

[Pogo]

Okay I can see no option to allow me to Disable SSL Certificates.

I can find mine under Settings/Advanced, but I'd like to know more about what risks it puts on me for other sites

ED - actually I can find where to go into SSL settings but what to do once in there is not at all clear. It does however offer a "Learn more about certificates" box which opens up a three-year course on the arcanities of all kinds of crapola I had no intention of spending my Sunday learning....

Google stopped support for SSL 2.0 with Google 38, if 2.0 is selected that could be the problem but the primary trick (as one tech put it) is "update your $(&^%$#$^ browser......."

Thank you to ALL my shining Knights in the sexy armour yesterday this they for taking time to assist a girl in confusion about confusing situation in Google Chrome, I do love ALL of you

Also to Kat I thank for her saying to me to get Opera Browser.

Yeah but how'd you like the stripper pics?

I think the same thing is still going on. Had to navigate the error message again today when I first went on. I suspect if I don't post for a while it will reappear as it did yesterday.

Still curious that the site has nothing to say about it though.

I use Chromium and no issues here plus I just logged in using Chrome, nope, nothing, no warnings.

I used Chromium once. Three lines and I saw God. Gave me a headache though.

 

[Lucy Hamilton]

I can find mine under Settings/Advanced, but I'd like to know more about what risks it puts on me for other sites

ED - actually I can find where to go into SSL settings but what to do once in there is not at all clear. It does however offer a "Learn more about certificates" box which opens up a three-year course on the arcanities of all kinds of crapola I had no intention of spending my Sunday learning....

Google stopped support for SSL 2.0 with Google 38, if 2.0 is selected that could be the problem but the primary trick (as one tech put it) is "update your $(&^%$#$^ browser......."

Thank you to ALL my shining Knights in the sexy armour yesterday this they for taking time to assist a girl in confusion about confusing situation in Google Chrome, I do love ALL of you

Also to Kat I thank for her saying to me to get Opera Browser.

Yeah but how'd you like the stripper pics?

I think the same thing is still going on. Had to navigate the error message again today when I first went on. I suspect if I don't post for a while it will reappear as it did yesterday.

Still curious that the site has nothing to say about it though.

I use Chromium and no issues here plus I just logged in using Chrome, nope, nothing, no warnings.

I used Chromium once. Three lines and I saw God. Gave me a headache though.

 

[Stormy Daniels]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

 

[Lucy Hamilton]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

ogo should I say to him to get Opera Browser, he say no he say if so then this is the forum Blackmailing him. I now have Opera Browser and this I am doing okay and happy with already.

 

[Darkwind]

Essentially, yes. However, google is now tying having a secure certificate with search engine rankings, along with your website being mobile friendly.

So, there is more to it than that, and google may be starting to penalize websites that don't have a certificate by not allowing their browsers to render them normally.

Yes, and they are also trying to enforce their demand by designing Chrome to automatically attempt secure connections irregardless (and making it difficult for users to figure out how to deactivate such default behaviors), and throwing error messages to end users, in hopes that they'll be scared away from the websites, thus creating a second avenue to punish websites who don't comply with Google's decrees.

But that is of no relevance to the end user here.

That isn't the case here, as I am currently using Chrome and I have zero issues with accessing this website on the browser.

If they get to the point that they enforce a certificate in the browser, I'll stop using the browser.

Hell, if I have to, I'll write one of My own. I just suck at the API functions for some of the browser features that stop advertisers. But I can prioritize that skill if I need to.

lol....

I didn't say Google is requiring certificates, just that they like to set default behaviors they want people to use, and try to press users to accept those defaults by making it difficult and complicated for users to change the settings that would modify those default behaviors.

Good luck building your own browser. At best, you might be able to slap your own clothes on chromium, but you're not going to code your own browser engine from scratch. Browser engines take man-years to develop.

I didn't say they were either. I said if they did.

Actually, coding a browser would take maybe a day to get it functioning. Depending on the platform. I could probably get one going inside a week using C#, maybe a couple of days using Java.

It would be very bare bones and basic, but it would be functioning and I wouldn't have to utilize anyone's kit.

To get it to spec for public use would take a year maybe. Security another year.

But if I wanted one that wasn't dependent upon anyone else, I could do it fairly quickly.

Okay, good luck with that. I believe I read somewhere that the simplest bare bones browser engine out there is some 50,000 lines of code. Blink is somewhere in the 4 million range, if I recall correctly.

You should read what is written, not what you think is written.

However, I was wrong. It wouldn't take a week to code a browser in C#. In fact, a functioning browser can be had in less than an hour.



This guy put one together in 15 minutes.

 

[Darkwind]

Essentially, yes. However, google is now tying having a secure certificate with search engine rankings, along with your website being mobile friendly.

So, there is more to it than that, and google may be starting to penalize websites that don't have a certificate by not allowing their browsers to render them normally.

Yes, and they are also trying to enforce their demand by designing Chrome to automatically attempt secure connections irregardless (and making it difficult for users to figure out how to deactivate such default behaviors), and throwing error messages to end users, in hopes that they'll be scared away from the websites, thus creating a second avenue to punish websites who don't comply with Google's decrees.

But that is of no relevance to the end user here.

That isn't the case here, as I am currently using Chrome and I have zero issues with accessing this website on the browser.

If they get to the point that they enforce a certificate in the browser, I'll stop using the browser.

Hell, if I have to, I'll write one of My own. I just suck at the API functions for some of the browser features that stop advertisers. But I can prioritize that skill if I need to.

lol....

I didn't say Google is requiring certificates, just that they like to set default behaviors they want people to use, and try to press users to accept those defaults by making it difficult and complicated for users to change the settings that would modify those default behaviors.

Good luck building your own browser. At best, you might be able to slap your own clothes on chromium, but you're not going to code your own browser engine from scratch. Browser engines take man-years to develop.

I didn't say they were either. I said if they did.

Actually, coding a browser would take maybe a day to get it functioning. Depending on the platform. I could probably get one going inside a week using C#, maybe a couple of days using Java.

It would be very bare bones and basic, but it would be functioning and I wouldn't have to utilize anyone's kit.

To get it to spec for public use would take a year maybe. Security another year.

But if I wanted one that wasn't dependent upon anyone else, I could do it fairly quickly.

Okay, good luck with that. I believe I read somewhere that the simplest bare bones browser engine out there is some 50,000 lines of code. Blink is somewhere in the 4 million range, if I recall correctly.

Maybe you should try and comprehend what you read?

With visual studio, a working web browser can be coded and working in less than 30 minutes.

Now, don't go and start with the, "But it isn't as secure or complete as the current browsers out there, or some such nonsense. Because that isn't what I said. I specifically said it wouldn't be as complete, but it would be a working browser.

No need for 4 million lines of code either.

 

[Pogo]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

Maybe you should actually read the thread before wandering in the woods. I've made clear that I am *NOT* "trying to access the site via a secure connection". I've never done that. What I did, same thing as Oosie did, same thing that others having the same issue did, was to simply navigate to a site (in my case already open in a tab) that suddenly, on a specific date, tells all of us that something "expired" on the USMB end, on a specific date. That ain't got nothing to do with me/us. I'm not buying that elves ran amok through the night changing people's computers from here to Austria.

And my URL does not say "https". It never has. I posted that yesterday too.

In other words, I (we) changed nothing. USMB changed something, or it looks like, let something expire. And before you dig further, we already tried to dig into my settings for SSLs, SSTs, DMTs, LSDs, whatever else, and could not find anything that applied, and then later in the day it came down that changing whatever it was was NOT advisable after all, so, no, we're absolutely not going there.

Oosie escaped to Opera because USMB wimped out rather than address it. Now she's gotta change all her bookmarks, passwords, etc, tweak her settings and get used to a new format.

But no, I'm not about to change MY shit just because USMB fucks up. That ain't gonna happen. I won't be railroaded because of some outside entitiy's negligence.

 

[Stormy Daniels]

Yes, and they are also trying to enforce their demand by designing Chrome to automatically attempt secure connections irregardless (and making it difficult for users to figure out how to deactivate such default behaviors), and throwing error messages to end users, in hopes that they'll be scared away from the websites, thus creating a second avenue to punish websites who don't comply with Google's decrees.

But that is of no relevance to the end user here.

That isn't the case here, as I am currently using Chrome and I have zero issues with accessing this website on the browser.

If they get to the point that they enforce a certificate in the browser, I'll stop using the browser.

Hell, if I have to, I'll write one of My own. I just suck at the API functions for some of the browser features that stop advertisers. But I can prioritize that skill if I need to.

lol....

I didn't say Google is requiring certificates, just that they like to set default behaviors they want people to use, and try to press users to accept those defaults by making it difficult and complicated for users to change the settings that would modify those default behaviors.

Good luck building your own browser. At best, you might be able to slap your own clothes on chromium, but you're not going to code your own browser engine from scratch. Browser engines take man-years to develop.

I didn't say they were either. I said if they did.

Actually, coding a browser would take maybe a day to get it functioning. Depending on the platform. I could probably get one going inside a week using C#, maybe a couple of days using Java.

It would be very bare bones and basic, but it would be functioning and I wouldn't have to utilize anyone's kit.

To get it to spec for public use would take a year maybe. Security another year.

But if I wanted one that wasn't dependent upon anyone else, I could do it fairly quickly.

Okay, good luck with that. I believe I read somewhere that the simplest bare bones browser engine out there is some 50,000 lines of code. Blink is somewhere in the 4 million range, if I recall correctly.

Maybe you should try and comprehend what you read?

With visual studio, a working web browser can be coded and working in less than 30 minutes.

Now, don't go and start with the, "But it isn't as secure or complete as the current browsers out there, or some such nonsense. Because that isn't what I said. I specifically said it wouldn't be as complete, but it would be a working browser.

No need for 4 million lines of code either.

You're the one who said "I wouldn't have to utilize anyone's kit." But you're video does exactly what I said you'd be doing--slapping your own clothes on an existing engine. In that video, he's just dressing up Trident, so he really just has Internet Explorer with different aesthetics.

So, is that what you're going to do? If Google changes Chromium to mandate https you're going to slap new clothes on Trident or EdgeHTML? May as well just switch to Edge outright.

 

[Stormy Daniels]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

Maybe you should actually read the thread before wandering in the woods. I've made clear that I am *NOT* "trying to access the site via a secure connection". I've never done that. What I did, same thing as Oosie did, same thing that others having the same issue did, was to simply navigate to a site (in my case already open in a tab) that suddenly, on a specific date, tells all of us that something "expired" on the USMB end, on a specific date. That ain't got nothing to do with me/us. I'm not buying that elves ran amok through the night changing people's computers from here to Austria.

And my URL does not say "https". It never has. I posted that yesterday too.

In other words, I (we) changed nothing. USMB changed something, or it looks like, let something expire. And before you dig further, we already tried to dig into my settings for SSLs, SSTs, DMTs, LSDs, whatever else, and could not find it.

But no, I'm not about to change MY shit just because USMB fucks up. That ain't gonna happen. I won't be railroaded because of some outside entitiy's negligence.

Alright, then explain why you are able to be on and posting now? Use a different device? Different browser? You had to do something, obviously.

And while you're at it, why don't you go ahead and post a screenshot of exactly what you're seeing.

 

[Pogo]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

Maybe you should actually read the thread before wandering in the woods. I've made clear that I am *NOT* "trying to access the site via a secure connection". I've never done that. What I did, same thing as Oosie did, same thing that others having the same issue did, was to simply navigate to a site (in my case already open in a tab) that suddenly, on a specific date, tells all of us that something "expired" on the USMB end, on a specific date. That ain't got nothing to do with me/us. I'm not buying that elves ran amok through the night changing people's computers from here to Austria.

And my URL does not say "https". It never has. I posted that yesterday too.

In other words, I (we) changed nothing. USMB changed something, or it looks like, let something expire. And before you dig further, we already tried to dig into my settings for SSLs, SSTs, DMTs, LSDs, whatever else, and could not find it.

But no, I'm not about to change MY shit just because USMB fucks up. That ain't gonna happen. I won't be railroaded because of some outside entitiy's negligence.

Alright, then explain why you are able to be on and posting now? Use a different device? Different browser? You had to do something, obviously.

And while you're at it, why don't you go ahead and post a screenshot of exactly what you're seeing.

I cut-and-pasted the message yesterday, as did others (Oosie did I believe, with her Chrome, early in the thread), but yes I can do that if I let some time go by to recreate it. The way it works is, if I go immediately from one post to another it's normal. If I let the page sit and come back to it later, it puts up the error message which I have to override, and then I'm in.

Same thing happens (or was happening yesterday) when either of us tried to post a video. Refresh the page and override the error message, and you can continue. For me I was unable to post ANY link. Haven't posted a video today but did post a link, and it worked normally.

The poster who reported the same thing in Firefox got a very similar message, saying a certificate had expired on Apirl 28 2019 and that he should check his computer clock. Lucy on Chrome and I on Brave were told the same thing.


EDIT - OK here we go. Just now when I tried to edit this in I got the screen below. Clicked "Advanced" to open it up, then took the option at the lower left.

 

[Lucy Hamilton]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

Maybe you should actually read the thread before wandering in the woods. I've made clear that I am *NOT* "trying to access the site via a secure connection". I've never done that. What I did, same thing as Oosie did, same thing that others having the same issue did, was to simply navigate to a site (in my case already open in a tab) that suddenly, on a specific date, tells all of us that something "expired" on the USMB end, on a specific date. That ain't got nothing to do with me/us. I'm not buying that elves ran amok through the night changing people's computers from here to Austria.

And my URL does not say "https". It never has. I posted that yesterday too.

In other words, I (we) changed nothing. USMB changed something, or it looks like, let something expire. And before you dig further, we already tried to dig into my settings for SSLs, SSTs, DMTs, LSDs, whatever else, and could not find anything that applied, and then later in the day it came down that changing whatever it was was NOT advisable after all, so, no, we're absolutely not going there.

Oosie escaped to Opera because USMB wimped out rather than address it. Now she's gotta change all her bookmarks, passwords, etc, tweak her settings and get used to a new format.

But no, I'm not about to change MY shit just because USMB fucks up. That ain't gonna happen. I won't be railroaded because of some outside entitiy's negligence.

"Oosie escaped to Opera because USMB wimped out rather than address it. Now she's gotta change all her bookmarks, passwords, etc, tweak her settings and get used to a new format."

Yes ogo I do ALL of that and the time to do approx 20 minutes. Now all is okay and I am happy with the situation. Also not change bookmarks or passwords I just Import ALL of them from Google Chrome in ONE click and then in approx 5 seconds ALL now in Opera for me.

 

[Lucy Hamilton]

Most of these browsers, always say Not secure. I am using Opera, which I love (for a browser), and I get no errors at all, but it does say Not secure.

Opera also has own built in Screen Shoot, I also already have Lightshot but think I attempt the Opera one also.

 

[Stormy Daniels]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

Maybe you should actually read the thread before wandering in the woods. I've made clear that I am *NOT* "trying to access the site via a secure connection". I've never done that. What I did, same thing as Oosie did, same thing that others having the same issue did, was to simply navigate to a site (in my case already open in a tab) that suddenly, on a specific date, tells all of us that something "expired" on the USMB end, on a specific date. That ain't got nothing to do with me/us. I'm not buying that elves ran amok through the night changing people's computers from here to Austria.

And my URL does not say "https". It never has. I posted that yesterday too.

In other words, I (we) changed nothing. USMB changed something, or it looks like, let something expire. And before you dig further, we already tried to dig into my settings for SSLs, SSTs, DMTs, LSDs, whatever else, and could not find it.

But no, I'm not about to change MY shit just because USMB fucks up. That ain't gonna happen. I won't be railroaded because of some outside entitiy's negligence.

Alright, then explain why you are able to be on and posting now? Use a different device? Different browser? You had to do something, obviously.

And while you're at it, why don't you go ahead and post a screenshot of exactly what you're seeing.

I cut-and-pasted the message yesterday, as did others (Oosie did I believe, with her Chrome, early in the thread), but yes I can do that if I let some time go by to recreate it. The way it works is, if I go immediately from one post to another it's normal. If I let the page sit and come back to it later, it puts up the error message which I have to override, and then I'm in.

Same thing happens (or was happening yesterday) when either of us tried to post a video. Refresh the page and override the error message, and you can continue. For me I was unable to post ANY link. Haven't posted a video today but did post a link, and it worked normally.

The poster who reported the same thing in Firefox got a very similar message, saying a certificate had expired on Apirl 28 2019 and that he should check his computer clock. Lucy on Chrome and I on Brave were told the same thing.


EDIT - OK here we go. Just now when I tried to edit this in I got the screen below. Clicked "Advanced" to open it up, then took the option at the lower left.

View attachment 258492​

Congratulations, you've proven that you have been wrong all along. That message indicates a missing SSL certificate. The browser is looking for an SSL certificate for a secure connection, and is not finding one. The certificate is "missing." By the way, Chrome and Brave are both Chromium browsers. They're basically the same thing, just tweaked a bit differently for aesthetics and a few minor operational variations.

 

[Pogo]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

Maybe you should actually read the thread before wandering in the woods. I've made clear that I am *NOT* "trying to access the site via a secure connection". I've never done that. What I did, same thing as Oosie did, same thing that others having the same issue did, was to simply navigate to a site (in my case already open in a tab) that suddenly, on a specific date, tells all of us that something "expired" on the USMB end, on a specific date. That ain't got nothing to do with me/us. I'm not buying that elves ran amok through the night changing people's computers from here to Austria.

And my URL does not say "https". It never has. I posted that yesterday too.

In other words, I (we) changed nothing. USMB changed something, or it looks like, let something expire. And before you dig further, we already tried to dig into my settings for SSLs, SSTs, DMTs, LSDs, whatever else, and could not find it.

But no, I'm not about to change MY shit just because USMB fucks up. That ain't gonna happen. I won't be railroaded because of some outside entitiy's negligence.

Alright, then explain why you are able to be on and posting now? Use a different device? Different browser? You had to do something, obviously.

And while you're at it, why don't you go ahead and post a screenshot of exactly what you're seeing.

I cut-and-pasted the message yesterday, as did others (Oosie did I believe, with her Chrome, early in the thread), but yes I can do that if I let some time go by to recreate it. The way it works is, if I go immediately from one post to another it's normal. If I let the page sit and come back to it later, it puts up the error message which I have to override, and then I'm in.

Same thing happens (or was happening yesterday) when either of us tried to post a video. Refresh the page and override the error message, and you can continue. For me I was unable to post ANY link. Haven't posted a video today but did post a link, and it worked normally.

The poster who reported the same thing in Firefox got a very similar message, saying a certificate had expired on Apirl 28 2019 and that he should check his computer clock. Lucy on Chrome and I on Brave were told the same thing.


EDIT - OK here we go. Just now when I tried to edit this in I got the screen below. Clicked "Advanced" to open it up, then took the option at the lower left.

View attachment 258492​

Congratulations, you've proven that you have been wrong all along. That message indicates a missing SSL certificate. The browser is looking for an SSL certificate for a secure connection, and is not finding one. The certificate is "missing." By the way, Chrome and Brave are both Chromium browsers. They're basically the same thing, just tweaked a bit differently for aesthetics and a few minor operational variations.

How exactly am I "wrong" when the screenshot shows exactly what I said it did? I already noted the expired certificate, and I proved it. Also mentioned in my first post here that Brave is based on Chrome. The fact remains --- I made no changes; LucyHamilton made no changes; the Firefox user we quoted made no changes. This just popped up at the same time for everybody. I assure you we did not all conspire on Saturday night and decide "hey let's tweak our SSL thingies and blame USMB". That never happened. K?

 

[Pogo]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

Maybe you should actually read the thread before wandering in the woods. I've made clear that I am *NOT* "trying to access the site via a secure connection". I've never done that. What I did, same thing as Oosie did, same thing that others having the same issue did, was to simply navigate to a site (in my case already open in a tab) that suddenly, on a specific date, tells all of us that something "expired" on the USMB end, on a specific date. That ain't got nothing to do with me/us. I'm not buying that elves ran amok through the night changing people's computers from here to Austria.

And my URL does not say "https". It never has. I posted that yesterday too.

In other words, I (we) changed nothing. USMB changed something, or it looks like, let something expire. And before you dig further, we already tried to dig into my settings for SSLs, SSTs, DMTs, LSDs, whatever else, and could not find anything that applied, and then later in the day it came down that changing whatever it was was NOT advisable after all, so, no, we're absolutely not going there.

Oosie escaped to Opera because USMB wimped out rather than address it. Now she's gotta change all her bookmarks, passwords, etc, tweak her settings and get used to a new format.

But no, I'm not about to change MY shit just because USMB fucks up. That ain't gonna happen. I won't be railroaded because of some outside entitiy's negligence.

"Oosie escaped to Opera because USMB wimped out rather than address it. Now she's gotta change all her bookmarks, passwords, etc, tweak her settings and get used to a new format."

Yes ogo I do ALL of that and the time to do approx 20 minutes. Now all is okay and I am happy with the situation. Also not change bookmarks or passwords I just Import ALL of them from Google Chrome in ONE click and then in approx 5 seconds ALL now in Opera for me.

I understand I can import all that stuff easily. Have done it before. I'm just not willing to expend my time and trouble for a situation I didn't create, and in the process sacrifice a browser I'm perfectly happy with. USMB made the mess, let USMB clean it up.

 

[Kat]

Would you guys PLEASE chill, and calm down? Can anything ever be discussed without the attacking??

 

[MisterBeale]

Would you guys PLEASE chill, and calm down? Can anything ever be discussed without the attacking??

 

[MisterBeale]

It's other people's browsers too. When you have the same thing going on to multiple people using different browsers, and none of those users report anything similar going on with any other site, that kinda points to the specific site.

I've been into my bank, my PayPal, my sports sites, etc, all the usual haunts, and only here does that error show up, and only since yesterday, and with the very specific dated message. Firefox reported the same message. Meanwhile I updated my browser and nothing changed. So no it doesn't appear to be my (Lucy's, others) browser.

You really don't have any idea what you're complaining about, of what is happening. I've already explained it, why are you not listening?

"Non-secure" warnings occur when navigation is attempted to a https connection (i.e. an encryption secured connection) but the browser is unable to identify an SSL certificate located where it ought to be on the website's servers. An SSL certificate provides secure https connections. When that certificate is absent (or expired) the https connection fails and only a plain http connection is possible. In essence, your broswer is saying "Hey stop! I'm being told to locate an SSL certificate but I can't find it!"

Secured https connections are valuable when you are transmitting sensitive data that you wouldn't want intercepted. For example, if you order a pizza online you have to transmit your credit card information. You wouldn't want that to be intercepted by a third party. In fact, secure https connections are required by US law for online payments. It can even be useful when you are transmitting other quasi-sensitive data. If you were planning a wedding and using photographers' websites to request information on pricing, you might be including things like your email and telephone number, which you might want to avoid having intercepted by spammers who will then call you 20 times a day to offer you medical knee braces. However, when you're simply viewing websites, or posting comments on publicly available messageboards, you aren't transmitting sensitive information. So an https connection offers nothing to you in such circumstances.

So, the only question right now is why you are attempting to access this site through an https connection. Chances are, it's simple user error associated with the settings on your browser. Sometimes a browser is set to automatically attempt https connections by default. So if you type "usmessageboard.com" into the address bar it automatically reaches out to "https://www.usemessageboard.com" to find the website you're looking for. These browser settings may be the default setting, or they may have been turned on by you. A recent update might override the user's previous settings to a new default mode.

Whatever the case, the solution to what you are experiencing can only be made on your end. You can manually change the url from https to http, or you can change your browser settings, or you can "create an exception" for the website in question. If none of that works easily for you, you can use a different browser that has controls and settings that you find easier to manage. Or, you could simply choose to stop using websites that don't provide https connections.

Maybe you should actually read the thread before wandering in the woods. I've made clear that I am *NOT* "trying to access the site via a secure connection". I've never done that. What I did, same thing as Oosie did, same thing that others having the same issue did, was to simply navigate to a site (in my case already open in a tab) that suddenly, on a specific date, tells all of us that something "expired" on the USMB end, on a specific date. That ain't got nothing to do with me/us. I'm not buying that elves ran amok through the night changing people's computers from here to Austria.

And my URL does not say "https". It never has. I posted that yesterday too.

In other words, I (we) changed nothing. USMB changed something, or it looks like, let something expire. And before you dig further, we already tried to dig into my settings for SSLs, SSTs, DMTs, LSDs, whatever else, and could not find anything that applied, and then later in the day it came down that changing whatever it was was NOT advisable after all, so, no, we're absolutely not going there.

Oosie escaped to Opera because USMB wimped out rather than address it. Now she's gotta change all her bookmarks, passwords, etc, tweak her settings and get used to a new format.

But no, I'm not about to change MY shit just because USMB fucks up. That ain't gonna happen. I won't be railroaded because of some outside entitiy's negligence.

"Oosie escaped to Opera because USMB wimped out rather than address it. Now she's gotta change all her bookmarks, passwords, etc, tweak her settings and get used to a new format."

Yes ogo I do ALL of that and the time to do approx 20 minutes. Now all is okay and I am happy with the situation. Also not change bookmarks or passwords I just Import ALL of them from Google Chrome in ONE click and then in approx 5 seconds ALL now in Opera for me.

I understand I can import all that stuff easily. Have done it before. I'm just not willing to expend my time and trouble for a situation I didn't create, and in the process sacrifice a browser I'm perfectly happy with. USMB made the mess, let USMB clean it up.

Yes, that time could definitely be put to better use arguing about it!

 

[Kat]

Would you guys PLEASE chill, and calm down? Can anything ever be discussed without the attacking??