ASMO help!

[Slick]

Hi mate,

For some reasons, right after ER started his bitchmoaning for some reason, my WiFi won’t let me onto NPR.

I know you sent some stuff to Inactionman to pass on to me, thank you very much, but he is a useless cunt and I’ve no idea where he has put it.

Any ideas greatly appreciated- I’ve tuned the router on and off and hit it gently, and quite hard, on the shelf, but no luck

[inactionman]

Hi mate,

For some reasons, right after ER started his bitchmoaning for some reason, my WiFi won’t let me onto NPR.

I know you sent some stuff to Inactionman to pass on to me, thank you very much, but he is a useless cunt and I’ve no idea where he has put it.

Any ideas greatly appreciated- I’ve tuned the router on and off and hit it gently, and quite hard, on the shelf, but no luck

link was in the PM, you need to whitelist - https://uk.pcmag.com/wireless-routers/8 ... s-settings to add the NPR URL to the router whitelist pages.

eta: ah. Looks like PM did not, in fact, go. I'll send now but it's the same link.

[JM2K6]

Malwarebytes was causing me issues the other day with the site - wonder if NPR is on a blacklist somewhere

[Ymx]

I said I hoped you crashed not your system Slick

[Slick]

I said I hoped you crashed not your system Slick

[Paddington Bear]

Happens on one of my devices every couple of months then weirdly resolves itself, no idea why.

[Slick]

Just got a FORBIDDEN message when trying to reply to inactionaman. Getting suspicious now

[Slick]

Hi mate,

For some reasons, right after ER started his bitchmoaning for some reason, my WiFi won’t let me onto NPR.

I know you sent some stuff to Inactionman to pass on to me, thank you very much, but he is a useless cunt and I’ve no idea where he has put it.

Any ideas greatly appreciated- I’ve tuned the router on and off and hit it gently, and quite hard, on the shelf, but no luck

link was in the PM, you need to whitelist - https://uk.pcmag.com/wireless-routers/8 ... s-settings to add the NPR URL to the router whitelist pages.

eta: ah. Looks like PM did not, in fact, go. I'll send now but it's the same link.

Fucks sake, have to looked at that link? No chance

[Jock42]

Just got a FORBIDDEN message when trying to reply to inactionaman. Getting suspicious now

Take the dick pic out and try again.

[Slick]

Got into my router believe it or not. Too scared to click on anything though

[SaintK]

Got into my router believe it or not. Too scared to click on anything though

You sound just like me 30 seconds before I call my son!!!

[Ymx]

Got into my router believe it or not. Too scared to click on anything though

Looks like you’ve nearly done it! You’re doing well Slick, you are doing well.

Now shake it violently 3 times.

[Uncle fester]

This is getting out of hand.
My desktop PSU blew up last night.

[SaintK]

Got into my router believe it or not. Too scared to click on anything though

Looks like you’ve nearly done it! You’re doing well Slick, you are doing well.

Now shake it violently 3 times.

[Slick]

Happens on one of my devices every couple of months then weirdly resolves itself, no idea why.

This is my only hope now

[TB63]

Got into my router believe it or not. Too scared to click on anything though

Looks like you’ve nearly done it! You’re doing well Slick, you are doing well.

Now shake it violently 3 times.

FKS9BU1YypbHe4yciRp0t1_STX51xltTSsRH1aaegBY.jpg (242.39 KiB) Viewed 1536 times

]

[ASMO]

Honestly i have checked all the settings here, the SSL cert and everything and its all in order, if it was systemic it would be impacting nearly everyone which puts me down the road that it is a local environmental issue.

I understand you have tried it on several different browsers and all the same issue, however, you use your phone and it works fine on 5g. Another thing to try to would be to tether your computer to your phone and see if that works, if it does then it points strongly to your ISP/Router settings as if it was your firewall, it would still be blocked even on tethering.

You could try going into your routers settings and as suggested earlier, whitelist this site so that should prevent any blocking from that area.

[sockwithaticket]

Malwarebytes was causing me issues the other day with the site - wonder if NPR is on a blacklist somewhere

How did you get round it? I have Malwarebytes and trying to access the bored via Firefox on my desktop produces error code: SSL_ERROR_RX_RECORD_TOO_LONG while Chrome just says site can't provide a secure connection. Works fine on my phone, though.

Have cleared browser and cache data and history, checked Firefox is up to date, but that's about the limit of what I comfortably know to do without wondering whether I'm fucking something up.

[Ymx]

TLS version??

Not my field of expertise unfortunately

Let’s start by covering the two most predominant causes of the SSL_ERROR_RX_RECORD_TOO_LONG message from the server side:

You’ve got the listening port misconfigured – If you want your website to establish secure connections you must configure it to use Port 443.
You don’t support an adequate TLS version – This problem arose ten years ago with the advent of TLS 1.2 and is appearing again with TLS 1.3.
The vast majority of the time, the SSL_ERROR_RX_RECORD_TOO_LONG message occurs because of one of those two issues on the server-side. Let’s go over how to fix both of these, and then we’ll go over some possible other fixes from the client side—as well as what not to do from the client side. Let’s start with the simplest of the two…

Download: Certificate Lifecycle Management 15 Best Practices Guide Free PDF.
Upgrade TLS Version Support to fix SSL_ERROR_RX_RECORD_TOO_LONG

TLS 1.3 was formally published in the middle of August as RFC 8446. It’s not exactly new though, over about 28 drafts the standard was debated and refined, but plenty of major industry players knew enough of what would be in the standard to begin rolling out support for it. As such, most major browsers already have TLS 1.3 active and many servers have already begun to upgrade.

So, what do you need to do to improve TLS version support? You’re going to need to update your SSL/TLS library. The majority of servers and systems use the Open SSL library, which pushed out its 1.1.1 update in September and supports TLS 1.3.

If you’re not ready to support TLS 1.3 for whatever reason, at least make sure you’re supporting TLS 1.2. Support for TLS 1.0 and SSL 3.0 should now be fully deprecated and disabling TLS 1.1 is also strongly advised. So, to recap:

Add support for TLS 1.3 as soon as possible
Make sure you’re supporting TLS 1.2 at the very least
Turn off support for SSL 3.0, TLS 1.0 and (highly suggested) TLS 1.1
Upgrading Open SSL is going to vary from server to server, but there’s plenty of documentation to help you with it.

[Ymx]

This says it’s very up to date for npr

[JM2K6]

Malwarebytes was causing me issues the other day with the site - wonder if NPR is on a blacklist somewhere

How did you get round it? I have Malwarebytes and trying to access the bored via Firefox on my desktop produces error code: SSL_ERROR_RX_RECORD_TOO_LONG while Chrome just says site can't provide a secure connection. Works fine on my phone, though.

Have cleared browser and cache data and history, checked Firefox is up to date, but that's about the limit of what I comfortably know to do without wondering whether I'm fucking something up.

I had to add it to the whitelist (Settings -> Allow List -> Add). I did check this morning to see if it was on a blacklist but couldn't find anything. Malwarebytes seems to be _very_ aggressive in blocking sites for dubious reasons tbh.

[JM2K6]

It's nothing to do with TLS - the "record too long" is the result of Malwarebytes deciding the site needs to be blocked.

[ASMO]

Malwarebytes was causing me issues the other day with the site - wonder if NPR is on a blacklist somewhere

How did you get round it? I have Malwarebytes and trying to access the bored via Firefox on my desktop produces error code: SSL_ERROR_RX_RECORD_TOO_LONG while Chrome just says site can't provide a secure connection. Works fine on my phone, though.

Have cleared browser and cache data and history, checked Firefox is up to date, but that's about the limit of what I comfortably know to do without wondering whether I'm fucking something up.

I had to add it to the whitelist (Settings -> Allow List -> Add). I did check this morning to see if it was on a blacklist but couldn't find anything. Malwarebytes seems to be _very_ aggressive in blocking sites for dubious reasons tbh.

Bin it and get defender, free and a much better product

[JM2K6]

Nah, I'm good.

[Torquemada 1420]

This says it’s very up to date for npr

Who has TLS 1.0 or 1.1 still enabled?

[Torquemada 1420]

Malwarebytes was causing me issues the other day with the site - wonder if NPR is on a blacklist somewhere

How did you get round it? I have Malwarebytes and trying to access the bored via Firefox on my desktop produces error code: SSL_ERROR_RX_RECORD_TOO_LONG while Chrome just says site can't provide a secure connection. Works fine on my phone, though.

Have cleared browser and cache data and history, checked Firefox is up to date, but that's about the limit of what I comfortably know to do without wondering whether I'm fucking something up.

That one is a Firefox specific problem which comes up all too often. Requires a bit of fault diagnosing.

Try connecting to http://notplanetrugby.com (NO s). If it works then it's a security f**k up within Firefox.

Sadly, after here it can get complex. The simplest things to do are
1) In Firefox, disable and re-enable your extensions to see if one is causing the problem. Obviously, don't kill your AV!
2) If it's global (which yours appears to be), add NPR as a trusted site in Whinedoze. Look it up if you aren't sure.

[sockwithaticket]

Thanks Torq and JMK. Eventually the thing that's worked was adding it as a trusted site to windows.

[JM2K6]

Malwarebytes was causing me issues the other day with the site - wonder if NPR is on a blacklist somewhere

How did you get round it? I have Malwarebytes and trying to access the bored via Firefox on my desktop produces error code: SSL_ERROR_RX_RECORD_TOO_LONG while Chrome just says site can't provide a secure connection. Works fine on my phone, though.

Have cleared browser and cache data and history, checked Firefox is up to date, but that's about the limit of what I comfortably know to do without wondering whether I'm fucking something up.

That one is a Firefox specific problem which comes up all too often. Requires a bit of fault diagnosing.

Try connecting to http://notplanetrugby.com (NO s). If it works then it's a security f**k up within Firefox.

Sadly, after here it can get complex. The simplest things to do are
1) In Firefox, disable and re-enable your extensions to see if one is causing the problem. Obviously, don't kill your AV!
2) If it's global (which yours appears to be), add NPR as a trusted site in Whinedoze. Look it up if you aren't sure.

Again, it's not a firefox problem. It's not even actually a problem as such. It's the consequence of how Malwarebytes handles sites it thinks need to be blocked.

[Slick]

Happens on one of my devices every couple of months then weirdly resolves itself, no idea why.

This happened.

[Tichtheid]

In the address bar up top there ^ it says "Not Secure - notplanetrugby.com"

Is it something to do with that?

[Ymx]

In the address bar up top there ^ it says "Not Secure - notplanetrugby.com"

Is it something to do with that?

You’ve just got the wrong link to http rather than https

Use this one
Secure link

[Tichtheid]

In the address bar up top there ^ it says "Not Secure - notplanetrugby.com"

Is it something to do with that?

You’ve just got the wrong link to http rather than https

Use this one
Secure link

I usually get here from google if I've cleared history/cookies/cache which is about once a week if I remember, or from a "frequently visited" thumbnail if not - is there a way to ensure I get the secure link every time?

[Ymx]

In the address bar up top there ^ it says "Not Secure - notplanetrugby.com"

Is it something to do with that?

You’ve just got the wrong link to http rather than https

Use this one
Secure link

I usually get here from google if I've cleared history/cookies/cache which is about once a week if I remember, or from a "frequently visited" thumbnail if not - is there a way to ensure I get the secure link every time?

Yeah, for some reason google has indexed the http version rather than https.

Asmo you might be able to fix this through

https://search.google.com/search-consol ... esource_id

[Ymx]

In the address bar up top there ^ it says "Not Secure - notplanetrugby.com"

Is it something to do with that?

You’ve just got the wrong link to http rather than https

Use this one
Secure link

I usually get here from google if I've cleared history/cookies/cache which is about once a week if I remember, or from a "frequently visited" thumbnail if not - is there a way to ensure I get the secure link every time?

Though can’t you just add it to your favourites/bookmark it, depending upon the browser you use.

Clearing history won’t erase favourites/bookmarks

[ASMO]

You’ve just got the wrong link to http rather than https

Use this one
Secure link

I usually get here from google if I've cleared history/cookies/cache which is about once a week if I remember, or from a "frequently visited" thumbnail if not - is there a way to ensure I get the secure link every time?

Yeah, for some reason google has indexed the http version rather than https.

Asmo you might be able to fix this through

https://search.google.com/search-consol ... esource_id

that has beeen done thanks

[Tichtheid]

This is the first "Help" page I found in the site search, so..

Has there been a security update or some such? When I try to log in I get a red message in the address bar and my log in details don't come up automatically, in fact they are just not available at all.

I logged in this time via my browser history.

How do I find the secure version of the site? I don't get directed to it from my "frequently visited" option on my front page

Thanks.

edit - I can see a link to the secure version of the site from YMX's post above, but how do I get there on my own? Both addresses say "notplanetrugby.com"

[ASMO]

https://www.notplanetrugby.com

[Tichtheid]

https://www.notplanetrugby.com

Cheers.

It looks like I need to make sure I have the https at the start of the address.

I don't really know why the link on my front page would start taking me to an unsecure version of the site when it had been taking me to the secure version before hand