Just checking to see if this is a new permanent condition because of the new hosting servers, or if it can be corrected.
Some of my posts actually time out—"Server Not Responding"—but still seem to get posted. Others just take a looooong time.
Ha! I searched to see if tacit has been MIA because he's been caught up in a publisher's deadline, and I found
BLACK IRON by Franklin Veaux , Eve Rickert | Kirkus Reviews. (Publish date 10-26...review posted on 11-5) Congrats to tacit and Eve!
Hopefully he'll have some time to deal with this problem now.
I'm experiencing delays similar to yours, plus "Gateway" time outs.
Aaargh!
Hmm.
Real Life vs. FineTunedMac Uploads
We all know where the real priority lies.
My experience would seem to indicate there is no undue delay in the actual posting. The delay is in the singular instance of refreshing the screen after a new post.
I have experimented with two FTM sessions in different tabs viewing the same thread. Make a post in one tab and it goes into the interminable hang, but if I refresh the display in the second tab — after a reasonable delay — the new post is there. Eventually the first tab will reload or the connection time out, but the post had already been completed. This does not happen when editing an existing post. Occasionally I run into another related issue where a new post hangs and after a long delay I backspace to the previous screen and click SUBMIT only to be told the post has already been made.
I concur that the postings always seem to happen. So a screen refresh is the culprit? What's the root of that problem? I'm reluctant to say it's on the users' end (ISP?) since personally, the problem did not exist prior to the FTM hosting change.
I've never lost a post, and the current problem seems to be similar to the one we experienced some time ago in that despite how long it takes for a post to appear, the page shows "Generated in n seconds....", n being less than 2.
I concur that the postings always seem to happen. So a screen refresh is the culprit? What's the root of that problem? I'm reluctant to say it's on the users' end (ISP?) since personally, the problem did not exist prior to the FTM hosting change.
FWIW my personal guess is the problem is in the database server. Either a delay in acknowledging the database update or sending the new record back to UBB Threads for display. But it could be on UBB Threads end or it could be a compatibility issue between UBB Threads 7.5.8 and the database server software.
There are too many people, networks, browsers, and browser versions affected for the problem to be local to the user's computers. It has to be something to do with the hosting site — which would include their servers.
The Gateway timeouts seem to be happening more frequently lately.
The Gateway timeouts seem to be happening more frequently lately.
I'm not finding that, at least over the past while ... which is unusual given my slow-as-molasses internet connection.
Moreover, after submitting a reply or new post, it's skipping right on by the interim message and returning me to the forums posthaste.
Maybe it is a time of day situation I am seeing it most often before 9:00 AM CST or maybe eastern United States vs. south or southwest.
My postings are still slow to occur.
I'm seeing "Gateway" pop-ups, slow posts, and almost immediate posts; I'll try to pay attention to see if I can distinguish a time pattern.
More: This post took 35 seconds.
Since I began time stamping my posts I've clocked 20 of them, 18 of which took a maximum of 50, but mostly less than 30, seconds to post; they were all posted between early afternoon and early evening.
The final two posts, one at 3 AM...the other at 4 AM, ended with Gateway time outs.
(Is tacit still with FTM? His last post, in which he said he'd continue tinkering with this problem, was on July 7th...six months ago. Even allowing for a publisher's deadline and book signing tour, that's an awfully long time for him to have been out of contact.)
(#21: 5 AM, and 50 secs to post)
Is tacit still with FTM? His last post, in which he said he'd continue tinkering with this problem, was on July 7th...six months ago. Even allowing for a publisher's deadline and book signing tour, that's an awfully long time for him to have been out of contact.
Hmmm...!
(55 secs)
Roger, bump noted.....trust me when I tell you that we are ALL aware of the issue and that we have attempted to resolve it in as many ways as possible short of the nuclear option. If it were an uncomplicated and simple fix, it would already have been implemented but it is not and we are continuing to work the issue in the background. It WILL be resolved!
"Hmmm...!" wasn't intended as a bump; it was - I thought, anyhow - a more polite form of "Response duly noted."
But since you mentioned it, what might "the nuclear option" be in this instance?
I've certainly got my fingers crossed...for you guys in particular; your diligence is appreciated.
FWIW, my reference to nuclear involves packaging up the entire site, negotiating the contract issues (at both ends) for moving to a new hosting service, installing / debugging / re-linking software components to play nice with the new host security requirements....and taking the FTM Forums down while performing the above actions, i.e., nuclear is the term I chose. FWIW, that option is the last on the list if at all possible.....the number of man-hours invested to execute that is huge.
"Pay no attention to the little man behind the green curtain...." for that one-armed paper hanger is named Tacit!
.... FWIW, that option is the last on the list if at all possible.....the number of man-hours invested to execute that is huge.
OUCH!!!
Fingers crossed that it doesn't come to that... Good luck!
More: Good imagery!
I hope it doesn't come to the nuclear option either!
Just wanted to note, I posted a few minutes ago in the Mac OS X System forum and got a "504 Bad Gateway" error, but the post did go through.
RE "504 Bad Gateway" error
Consistently on new topic posts. But they do get posted.
Together with 'disconnects'*, often on replies or edits. But, again, they do get posted.
(* Secure Connection Failed — The connection to
www.finetunedmac.com was interrupted while the page was loading.)
Mostly an annoyance.
That said, I had to submit this twice to get it to take, despite 'assurance' that the first attempt was being submitted and therefore that the Submit button was disabled.
HEY! For the first time in months my reply (in The Lounge) was posted lickety-split, with no intermediate steps, including gateway error collapses.
Dare I conjecture that previous problems have been resolved?!
If so, then
EDIT: And the same for this!
Sorry, I'm still not seeing speedy postings. In fact, my just previous one froze, but did get posted.
My experience is all over the map and I have yet to identify a pattern
My experience is all over the map and I have yet to identify a pattern
Same!
Sometimes my posts are up instantly, sometimes they take a while, and sometimes I get the Gateway error.
The closest I can come to discerning a pattern is that the randomness
may be in terms of longer increments of time rather than shorter ones.
Sometimes my posts are up instantly, sometimes they take a while, and sometimes I get the Gateway error.
Ditto.
Sometimes my posts are up instantly, sometimes they take a while, and sometimes I get the Gateway error.
Ditto.
Double ditto.
Tonight it seems pretty fast and reliable — so far.
I learned something new last night; I hope it's helpful.
My usual procedure for dealing with a Gateway time out is to back-click to the page on which I originally clicked on "Reply," hit command-R, and wait a few seconds, after which my screen refreshes and my post appears.
Last night, I walked away from a time out, and when I returned, I spaced, and rather than following my usual procedure, I clicked on a bookmark I had saved for the post to which I was replying, hit command-R, and...my screen didn't update.
I repeated, again with no luck, clicked on "Index" at the bottom of the page, clicked on "Forums" at the top of the next page (unfortunately, without first looking closely at it), and when I got to the Forums index found that the last post in the thread in question had been updated to mine.
My question, then, is why didn't simply refreshing the page result in the appearance of the new post?
It seem as if posting, at least for me, is back to "normal" in terms of time. Other than Mojave updates, nothing has changed on my end.
UPDATE: I spoke too soon. After almost 3 minutes (really? Unacceptable!) the gateway timed out. And as we have all observed, the posting still gets posted. I think two consecutive "normal" posts fooled me.
Just tired to post on latpop which having issue. Timed out. Should I wait till midnight? /any tips?
Just tired to post on latpop which having issue. Timed out. Should I wait till midnight? /any tips?
Part of the difficulty in attempting to fix this problem is that it is not reliably repeatable and there is no apparent pattern to the slow posting. It is as likely to Time out at midnight as it is at any other time of day. It is also as likely to go quickly and smoothly at any time of day or night. 🤷â€â™‚ï¸
FYI:
Since my last post on the topic a couple months ago, my posts in various forums have continued to be rapid, with no gateway error issues.
My post to Networking a couple minutes ago went through instantaneously without any intermediate steps (apparent).
Same for this one.
FYI:
Since my last post on the topic a couple months ago, my posts in various forums have continued to be rapid, with no gateway error issues.
You've been luckier than I"ve been.
My posts still range between instantaneous and "Gateway Error."
Perhaps you've discovered dial-up's silver lining?
My posts had been going well for the last week or so, but yesterday I had two timeouts. â“â“ⓠ🤷â€â™‚ï¸