Proboards has been down for the last hour or so but is now up again but is still a bit flakey!
We continue to lose connection (the proboards forum also reports similar experiences with other users) so if you too are having problems then continue to have patience and hopefully proboards will get it sorted soon.
Depending on which browser you use, you may have seen a “not secure” notice in your address bar. Our Support Forum tells us that are no security issues. They explained that:
That is a function of the browser which indicates that the page has not been delivered on a https:// secure connection. An https:// is essential for pages where you submit sensitive information, such as payment details, or login information, etc. On the forum, you will find that if you click 'login', or attempt to make a purchase then the pages will indicate they are 'secure'.
This has always been the case, but recently there has been a push to get all pages on the internet delivered over an https:// connection, and so browsers have made the secure/not secure notification more prominent, thus why people are now noticing it more.
Whilst ProBoards already delivers pages which handle sensitive information on a secure connection, they will be implementing https:// across all pages in the future, most likely inline with the forthcoming version upgrade. In the meantime, however, members shouldn't be concerned by the 'Not Secure' notice, but as with all websites, ensure that they are not submitting sensitive information on pages which aren't secure.
Yes, it's been a struggle for the last month or so, even moreso because of the hosting company's server move and outages, at a time when I needed to update the website to more modern standards. As you know, standards keep changing in the internet world and when they do, things can and do break. But also, the recent server issues broke the website comments spam protection so I had to spend hours last night removing nearly 2,000 spam comments that I couldn't get at or block last month.
However, it now seems to be fixed, so my updating work can continue. Hopefully!