Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
NexusFi site changelog and issues/problem reporting
HTTP/2 support enabled today, but without ALPN (NPN only) so only for Firefox users and not Chrome. Waiting for a backport of OpenSSL 1.0.2+ before I can enable ALPN for Chrome on this server.
Was able to get full HTTP/2 with ALPN on the beta site (new framework), since it's running a newer distribution with no openssl library backport issue.
HTTP/2 is up and working on the beta site (new framework). Seems to be considerably faster. Not sure if it will be possible to get HTTP/2 on the old site or not, there is a backport issue for the openssl library.
I'm slowly putting together a serious plan for an autumn restart and have come across a couple of 100% reproducible issues in trying to resume use of FIO.
1) Chrome/W10 currently retains my non-elite status across browser sessions, but loses my elite status, asking me to login again, - assuming (?) cookies are used to hold the login/pass for both this seems weird (and a tad inconvenient..) to me. May be old but I haven't seen this before.
2) Some elite threads give me instant access after the second level login, some don't, see examples provided. E.g. Two Pints and Extend Rects both get kicked out, Ratcave is fine, all three are elite. If I can get in through one then I can get to the others. All using standard stored .../new-post.html type link.
3) Because of the difficulty I am currently having in getting to my own elite thread areas (esp Two Pints) I also seem to have uncovered a strange (but again 100% reproducible) relationship between logins and our historic world famous 'missing images' problem - which may or may not have any bearing on the more global manifestations of such.
- if I first try to access my Two Pints elite thread and successfully go through the login and get to the thread then I always see the classic missing images icons in the last post in that thread.
- if I then subsequently try to access any non-elite level thread or the forum top-level and go through the normal level login I can then return to Two Pints and see the full images in all their glory.
No priority compared to weddings and funerals but I've logged it as best I can, hope it sheds some light, doubt it's related to the stuff you're currently changing as I think I've seen the login/missing image thing before but hadn't found the reproducible sequence until now. Clearing all browser data (e.g. cookies/cache/etc) doesn't clear the issues and I'm not seeing anything weird on any other sites that I'll admit to.
Cheers
EDIT: NB Just tried a full 'Reset Settings' in Chrome and that does seem to have cleared it, wasn't aware I had anything special set but maybe ignore for now. Fyi the missing images login sequence problem does show the same in Edge from a ground zero start, but also seems fine once the two logins have been done and cookies retained so may also be trivial/irrelevant.
Was going to suggest deleting cookies for FIO * and clearing cache, those problems are cookie related and their are no known issues there. Also make sure you aren't using any content blockers.
I just started getting this https error every time I try to access any forum post from an email notification. It began maybe 10 or 15 minutes ago (~3:15 ET or so.)
There's no issue in going to the post from within the forum itself.
All domain SSL certificates were renewed and replaced today (they were set to expire in September). I also converted our short url handler (on.futures.io) to SSL only, so any short links like on Twitter or for webinars should now automatically redirect to HTTPS.
Since now all domains *.futures.io are forced SSL, I've enabled HSTS preloading and submitted to Google for approval. It may take a couple weeks to get approved on the preload list.
dont believe anything you hear and only half of what you see 
