Accessing JASPP forums

Hi,

Is anyone else having issues accessing the JASPP forums via RISC OS browsers like Netsurf and IRIS.

JASPP

I tried from various RISC OS machines over the passed few days, rebooted the router etc and 8 times out of 10 I either get unable to establish connection , timeout or a simple page that looks like the CSS has been disabled.

The Windows PC and my phone connect ok all the time.

If someone else can test it out then it may point to an issue at my end , though not sure why all the RISC OS systems would give the same even though some are on the ROD stack and others on the ROOL one.

Confirmed. NetSurf (3.11 ##5312, not the latest!) spends ages on the “Fetching, processing” only to eventually show something that looks like it’s from the HTML 2.0 era.

Trying to load the CSS files individually results in either a long time to fetch a small file, or a timeout.

My phone loads it correctly in about 3-4 seconds, as does Iris – although it took a long time to do so (tested twice).

However, I then ran an SSL test on it, just in case the SSL had been updated to something that RISC OS didn’t like…

…and it gave up saying “Unable to connect to server”.

So it seems as if there may be issues with the server. It’s not just you, and it’s not just RISC OS.
<phew!>

Later: Here’s a log of Iris fetching the main page. It takes nearly two minutes to completely fetch it. And, um, it appears to be running on a Pi?!? The server identifies as Apache on Raspbian.
https://heyrick.eu/blog/files/iris_jaspp.txt

So it seems as if there may be issues with the server. It’s not just you, and it’s not just RISC OS.
<phew!>

Thanks Rick.

I’ll let Jon know as I’m in correspondance with him testing ADFFS.

I thought it was the server being as all my other sites connect OK.

I then ran an SSL test on it

I suspect an SSL test might cause the connection to be blocked. Every IP and email address is cross-checked against both an internal list and Stop Forum Spam so hitting it with a lot of requests from one IP in a short time period might trigger a block from SFS, which in turn will block the response from the server.

Its also possibly SFS have changed their API, and the way RISC OS browsers connect is somehow triggering slow or blocked responses?

The Certs are checked daily and update at least once a month, so its also possible its now using a Cert that somehow affects RISC OS due to the Cert tree? I’ve not looked to see how many Certs actually need checking for each page.

there may be issues with the server

I can’t see any issues, there’s nothing in any of the logs and the server appears responsive. I’ve checked it remotely via a variety of (non-RISC OS) sources and don’t see any response issues.

That all said, I’ve yet to perform the yearly maintenance. I’ll take it offline over the weekend and update the OS, forum software etc and we’ll have to see if that helps or makes things worse.

so hitting it with a lot of requests from one IP in a short time period might trigger a block

How literal is this “everything”, as there are quite a number of requests necessary just to fetch the index page (a quick look at the log I posted above suggests 23 requests in a short time frame).

I’ve not looked to see how many Certs actually need checking for each page.

You’re using Let’s Encrypt, so it’ll be your cert, their cert, and the root cert.
Likely the latter two will already be known to the system as Let’s Encrypt is hardly an unknown provider.

and don’t see any response issues.

I see largely the same on my phone. I would have said it’s RISC OS specific, except the SSL Labs test threw in the towel as well (though your server might have simply blocked it for too many requests).

I’ve just tried a random selection of SSL checking sites, some worked consistently, some consistently report a connection issue. All that tells me is you can’t rely on them working for all sites.

Looks like there’s a real name and and alias

If it’s a long term redirect then a 301 would perhaps be better than a 302, then the likes of Google index it instead of rescanning at regular intervals.

Does that help?

Please remove all that info, it gets attacked enough without you putting it on a public site for easy trawl.

PM me if you want to discuss how the aliasing and redirects work.

I’ll take it offline over the weekend and update the OS, forum software etc and we’ll have to see if that helps or makes things worse.

That’s done if you want to see if it made any difference to load times. Edge loads it in 175ms.

Thanks Jon, loads virtually in an instance with Netsurf 3.11.