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)
I'm getting a lot of this timeout error message when I try to get to a FIO page. Generally the connection comes up after a while if I wait, and the page eventually shows up, but with sometimes a good delay (can be 30-60 sec or more.)
It's intermittent, coming and going. Sometimes it's just a little delay, sometime none, sometimes a big one. Retrying often helps.
This started some time yesterday, especially last night, and is continuing today.
*** Edit: I'm noticing some issues now with other sites, so it may not be FIO after all. I"ll leave this up just in case there is some more input from other users, but if no one else is having it, never mind....***
I am testing some backend infrastructure changes. Limiting testing to night (off-peak). Each test can take around 30 minutes.
If you receive a "forum is in maintenance mode" error message, this is the reason. I apologize for the inconvenience.
I'll provide a full update at a later date when I have everything worked out. There is no impact to users at this time except for the occasional short downtime. No persistent changes to the site config are being made. Unfortunately, my tests do require a live production database -- hence the need to "stop" the site so that nothing is lost during the testing.
@srgtroy reporting chatbox pop-out isn't working. I've noticed this for a while, and tried to fix it a while back, but the problem is not obvious to me. I'll add to my list to investigate.