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
Hmm, odd that @xplorer got it too. I could reproduce this even after a full manual clearout and full factory reset in Chrome, but have been using Edge lately, will update. No known 3rd party blockers, any chance an F-Secure issue? Nothing reported.
OK, I just checked again and I see the issue. Not sure what caused it, but I will work to fix it shortly. The problem is that the URL contains www, and our site should be redirecting to non-www (just futures.io, not https://www.futures.io/). You don't have a cookie for the www domain, because that domain should never serve a page but instead redirect everything to non-www.
Not sure at what point that broke or why, but will check our nginx config for solution.
The problem originated when our old futures.io SSL certificate expired a few weeks ago, and a new wildcard certificate was put in its place. The existing www redirect was serving up the old bigmiketrading SSL certificate instead of the new one, causing an issue with the redirect.
The X_Trader subforum has been renamed to Trading Technologies, to better describe the current products available from TT (X_Trader/MD Trader/ADL/TT web).
Just noticed a way to generate the seemingly permanent last post flickering issue - I had to edit a post to correct a member's username so that he got 'mentioned' properly. Just this action set off the repeated flickering. Really interesting (to us saddos) is that it is cross-browser (in this case triggered in Edge, visible in Chrome, Firefox and Edge) so please don't say it's my fat cookies unless the rabbit hole is even deeper.
