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)
Thanks, all those errors appear to be third party. Anyone else having this issue?
I will investigate further this morning on my side. I am going to flush the entire cache of the site as well, as that could be causing part of the problem.
The new server will become the primary server this morning. Please continue to report any problem, and apologies for brief outages and service disruptions on the site.
pegasus is now primary as of this post. Please report any issues. Performance will improve as DNS changes propagate and your frontend server changes as well, right now phoenix is forwarding everything to pegasus.
in the "Thread Subscription Notification" email it says "You will not receive additional email updates until you read the thread on futures io.". It appears that now a new mail comes following a new post even if the thread isn't read, but futures.io was visited since the last mail. I am not sure if it always has been like that, but if I correctly recall it I had to visit the thread again at some point in order to receive a mail again.
Patch in place to get things back up for now by relaying via our old server, but I need to solve a problem for a more permanent solution.
From user perspective, shouldn't notice anything. No emails have been lost (just delayed the last hour or two). I'll make another note here once my permanent solution is in place, for the record in changelog.