Cloudflare DDoS Protection and now no graphics are loading.

With apologies for probably butting in, unasked, but that screenshot looks to me to be typically what a modern web-page would look like if the external .css file fails to load.

Though I've not had this particular site do this, it's something that happens more often than it should, for me (my link, which I already can't/don't use for streaming and Youtube, often has high latency). And these days web-page authors (or however much authorship the Content Management Systems takes control of) tend to separate content and style almost entirely, leaving you with the very "Web 1.0"-looking display¹, and possibly also without some .js file or other (which, when not run - which the author assumes is because an AdBlocker has blocked it - leaves the catch-all text moaning about your settings which you normally wouldn't see).

It'll have fixed itself as soon as you reload it and don't suffer the same service problems, as I think you found.

Of course, it could have been anything from actually Cloudflare issues (especially if you have had the other things you mention, although that might have just been the same as the "no .js file" issue, you seeing a 'catch-all' message), your ISP badly serving you or just a temporary local machine problem (e.g. other heavy downloading going on, temporarily causing some pull-connections to time-out/not establish).


I've a feeling you know at least some of this, and there could always be another problem that I somehow haven't covered, but I just found my fingers twitching to say something of what I think I know. Bad habit of mine, I know.


¹ Remove some items, like the images and form-elements and it looks like my very first personal web-page, with over-use of bullet-points containing just links to places!

That screenshot still says to me "The .css didn't load".

If you view the source HTML (best method varies, according to browser, but right-click on a non-advert part of the page and "view (page?) source" might work most consistently across them all) you should see a line somewhere in the header lines (definitely appears to be easily within the first page of any display, even with line-wrapping on) something like: <link rel="stylesheet" type="text/css" media="screen" href="....

Take the href (and if a 'relative' URI, integrate it onto the page URI minus the page-name to 'get there') and look at the .css directly.

In the case of this page (for me, at least!), that leads to d.storage.proboards.com/f/forum_209.css (cross-board forum behaviour, I'd guess, at a glance) with a second one of storage.proboards.com/5366296/c/6ihYrW8jkUxL8QY5ZIR8.css (at a guess, points to whatever the the board-owner's/reader's preferences allow to be configured...) and see if you can either click on the reference (might be "blue-underlined link") or copy and paste it into the Address bar. It might open (as unformatted text), or demand through an "open or save or cancel" dialogue that you do something else with it. (My machine has remnants of a long expired version of Dreamweaver, hooking .css documents for opening, and I just had to change it to use Notepad instead, as the simplest option.)

With that(/those) successfully opened, do a refresh (or, indeed, shift-refresh, to by-pass at least the local cache) and... if it all hasn't already, it might just have served to kick it into action again. Although in the last five hours I'd be surprised if it hadn't rectified again, anyway.