Topic: Bitcointalk: Error 504: Gateway time-out [Update: December 2, 2023] - page 2. (Read 989 times)

For server-side problems?

 Since we can't avoid this of the timeout from happening, isn't there a way to limit it's frequency? Things like this if not properly tended end up becoming big problems. Today's own lasted for an hour plus and it's becoming disturbing.

Well you can do early posting though and not to crunch everything, or maybe manager will be lenient because of this? I don't know.

---

Same here, I thought that I have problems with my internet connection again, but when I checked https://www.isitdownrightnow.com/bitcointalk.org.html, it says it's down so I have some time to do some errands and then go back to the gym.

It's that this error seems to be happening recently.

I think we need to take a nap at 6.00 AM UTC to 8.00 AM UTC since we're really active in this forum, maybe there's an user active for 24 hours everyday without a sleep.

It's possible run a bounty? although I didn't see there's a reward for someone to find an error about server.

theymos did mention a month back that he is planning to do some upgrading for the next few months, these gateway time-out errors that is happening recently could be related to that, though I am not completely sure if it is.

anyway, here is a quoted post from when he mentioned that upgrading he will do for the next few months.

Here we go again, that was roughly over 2hours of downtime...

Thought this was another attack but reading some of the responses in the thread, some users say its some routine maintenance going on and not an attack?

So how can we make the distinguishment between the two as we have no alerts on these technical changes as they happen??

I'd have so much more time to spend on other things Maybe things like creating a replacement forum, although I lack programming skills for that so I'd really hope someone else would do that. But that's all speculation, I assume both Admins of Bitcointalk keep a backup of the forum database, and I assume at least one of them will make sure the forum comes back up.

Time for an update (>5 minutes is bold, >30 minutes is red):
186 seconds between posts at 6300/63006744.html Tue Oct 17 00:08:26 UTC 2023
186 seconds between posts at 6300/63006749.html Tue Oct 17 00:17:02 UTC 2023
246 seconds between posts at 6300/63006776.html Tue Oct 17 00:42:50 UTC 2023
216 seconds between posts at 6300/63006959.html Tue Oct 17 02:07:19 UTC 2023
216 seconds between posts at 6300/63007520.html Tue Oct 17 05:34:25 UTC 2023
234 seconds between posts at 6301/63012218.html Wed Oct 18 00:22:49 UTC 2023
198 seconds between posts at 6301/63017579.html Wed Oct 18 22:06:37 UTC 2023
186 seconds between posts at 6301/63018064.html Thu Oct 19 00:02:49 UTC 2023
259 seconds between posts at 6301/63018293.html Thu Oct 19 01:45:32 UTC 2023
187 seconds between posts at 6301/63018547.html Thu Oct 19 03:50:50 UTC 2023
187 seconds between posts at 6302/63023712.html Fri Oct 20 00:52:02 UTC 2023
229 seconds between posts at 6302/63024251.html Fri Oct 20 04:21:56 UTC 2023
359 seconds between posts at 6302/63028944.html Sat Oct 21 00:42:55 UTC 2023
186 seconds between posts at 6302/63028967.html Sat Oct 21 01:01:20 UTC 2023
270 seconds between posts at 6302/63029016.html Sat Oct 21 01:38:08 UTC 2023
282 seconds between posts at 6303/63033797.html Sun Oct 22 01:44:31 UTC 2023
216 seconds between posts at 6303/63033842.html Sun Oct 22 02:16:13 UTC 2023
215 seconds between posts at 6303/63034137.html Sun Oct 22 04:37:55 UTC 2023
258 seconds between posts at 6303/63038660.html Mon Oct 23 00:17:25 UTC 2023
198 seconds between posts at 6304/63049868.html Wed Oct 25 01:16:19 UTC 2023
222 seconds between posts at 6305/63055527.html Thu Oct 26 00:10:50 UTC 2023
198 seconds between posts at 6305/63055614.html Thu Oct 26 01:09:49 UTC 2023
186 seconds between posts at 6305/63055827.html Thu Oct 26 03:04:44 UTC 2023
186 seconds between posts at 6305/63055901.html Thu Oct 26 03:47:56 UTC 2023
205 seconds between posts at 6306/63060564.html Fri Oct 27 01:12:20 UTC 2023
275 seconds between posts at 6306/63060578.html Fri Oct 27 01:22:25 UTC 2023
204 seconds between posts at 6306/63060666.html Fri Oct 27 02:04:43 UTC 2023
594 seconds between posts at 6306/63060861.html Fri Oct 27 03:54:43 UTC 2023
239 seconds between posts at 6306/63065809.html Sat Oct 28 02:07:43 UTC 2023
341 seconds between posts at 6307/63070434.html Sun Oct 29 00:54:31 UTC 2023
181 seconds between posts at 6307/63070449.html Sun Oct 29 01:08:20 UTC 2023
289 seconds between posts at 6307/63070585.html Sun Oct 29 02:43:38 UTC 2023
269 seconds between posts at 6307/63075227.html Mon Oct 30 00:09:37 UTC 2023
186 seconds between posts at 6307/63075426.html Mon Oct 30 01:55:37 UTC 2023
187 seconds between posts at 6308/63080180.html Mon Oct 30 22:50:02 UTC 2023
209 seconds between posts at 6308/63080470.html Tue Oct 31 00:58:43 UTC 2023
234 seconds between posts at 6308/63085944.html Wed Nov  1 03:05:07 UTC 2023
193 seconds between posts at 6308/63086275.html Wed Nov  1 05:25:32 UTC 2023
2334 seconds between posts at 6308/63086374.html Wed Nov  1 06:44:44 UTC 2023
198 seconds between posts at 6309/63091070.html Thu Nov  2 01:20:08 UTC 2023
311 seconds between posts at 6309/63091674.html Thu Nov  2 06:06:43 UTC 2023
181 seconds between posts at 6309/63091884.html Thu Nov  2 07:05:02 UTC 2023
205 seconds between posts at 6309/63096299.html Fri Nov  3 00:44:38 UTC 2023
228 seconds between posts at 6309/63096436.html Fri Nov  3 02:00:31 UTC 2023
185 seconds between posts at 6309/63096459.html Fri Nov  3 02:15:25 UTC 2023
186 seconds between posts at 6309/63096462.html Fri Nov  3 02:18:49 UTC 2023
197 seconds between posts at 6310/63101573.html Sat Nov  4 01:24:31 UTC 2023
197 seconds between posts at 6310/63101607.html Sat Nov  4 01:53:37 UTC 2023
204 seconds between posts at 6310/63101929.html Sat Nov  4 04:24:55 UTC 2023
276 seconds between posts at 6310/63106327.html Sun Nov  5 00:13:01 UTC 2023
329 seconds between posts at 6310/63106437.html Sun Nov  5 01:11:37 UTC 2023
264 seconds between posts at 6310/63106462.html Sun Nov  5 01:34:19 UTC 2023
193 seconds between posts at 6311/63111491.html Mon Nov  6 00:35:02 UTC 2023
227 seconds between posts at 6311/63111755.html Mon Nov  6 02:59:31 UTC 2023
185 seconds between posts at 6313/63132878.html Fri Nov 10 00:43:49 UTC 2023
185 seconds between posts at 6313/63132951.html Fri Nov 10 01:14:43 UTC 2023
6041 seconds between posts at 6313/63133565.html Fri Nov 10 07:45:31 UTC 2023
257 seconds between posts at 6313/63138069.html Sat Nov 11 00:10:55 UTC 2023
181 seconds between posts at 6313/63138152.html Sat Nov 11 00:57:56 UTC 2023
204 seconds between posts at 6313/63138272.html Sat Nov 11 01:56:55 UTC 2023
204 seconds between posts at 6314/63143036.html Sun Nov 12 00:47:07 UTC 2023
199 seconds between posts at 6314/63143656.html Sun Nov 12 05:15:20 UTC 2023
7836 seconds between posts at 6314/63149134.html Mon Nov 13 08:17:19 UTC 2023
(this only counts when there was at least 3 minutes between posts)

It looks like the downtime is increasing.

Thanks. It's an automated script though.

The last 3 longer down times all started around 6:05 AM UTC.

I guess we just have to hope that they're doing their best in regards to this issue, it definitely is an annoying thing but what can we do when we know that this situation is out of our hands, we can't really do a thing about besides talk about it and share our concerns to the administrators. And the problem is most likely a server issue which is a backend problem so let's just hold on to hope that it will eventually be fixed. I hope this isn't something that will happen and that we'd get used to it, I don't like the idea that part of my routine in exploring the forum is waiting for the server to go back up.

And again it started about 6 am UTC. It happens more often but each time about the same time. It should probably be related to some regular program action, because otherwise why at the same time? Internet provider on the server side?

At least we can make no plans on the forum at exact time.

Another day and another 504 error. Something really need a fix here.

Getting Downtime alert again today from 2023-11-13 | 13:07:39 to 2023-11-13 | 15:15:39
Downtime 2h 16m




Outage analysis of bitcointalk.org

Looks like it's becoming our new morning routine that the forum is unavailable for certain periods of time.

Today's downtime was between Post 63149133 und Post 63149134 - This means that a downtime of around 2 hours once again.
@LoyceV just as an info for you so you can embed it in your post.

I'm curious to see whether the error that causes this can be slowly identified....

What the hell.... another 2-hour downtime.

I'm going to try to talk to the admins about this.

Maybe yes maybe no. Also I may have used wrong set of words. I have been on bitcointalk for some times now. It became on of my daily routine. I am literally spending hours, going from one thread to another, replying, reading etc. Now imagine, if bitcointalk disappears, what do you think my reaction will be? Forget about me. What about you? What will be your reaction, will it miss it, if there were no bitcointalk? You have been in this forum for years. Surely you have some attachments towards it. I meant something like that. 

If any website make you worry IRL, you should reevaluate your priorities
Even if Bitcointalk disappears, something else will take it's place.

I just wait for no longer signature. I am sure you be 1st one to leave the forum.

If it was so then why each forum unavailability happens in the same time? About 6 am UTC? Hardly each time crowds of visitors come just at that time. It looks more like theymos said: some program starts working on the server in that time and overloads it. Main problem is to understand which program and why.

Afraid in what sense? That the forum might be taken down or that the police will come crashing down your door when you are sleeping? The forum isn't for anything illegal nor is it doing anything illegal, so no need to worry for your well-being. And if it's an attack of any sorts, there is nothing that you and me can do about it.

The reason why it's happening might not have anything to do with when theymos is sleeping. If it was happening while he was awake and at work, one could ask a similar question: why is it happening when theymos is working and not after work when he is home? I am guessing the dude also works somewhere in some capacity.

I don't know the technical side of this problem. But the recent blackouts are making me concerned about what is going on. These instabilities are occurring more and more frequently now. This makes me wonder, is it something to be afraid of? Or is it some random server or hardware-side issue? Or any kind of cyber attacks. We can now predict when these blackouts might happen. When the owner is sleeping. But why this specific period of time? It doesn't make sense. Why doesn't it happen when theymos is awake? So that he can analyze the cause of this issue. 

That may be one of the reasons why the Forum is experiencing instability.
The increase in visits makes the server load heavier.
Especially when Bitcoin will soon be halving, making many people start opening this forum, reading some threads, and commenting and there are more new accounts created.

Hopefully, the improvements that will be made by the forum administrator can solve all the problems that occur and the forum is no longer disturbed by some downtime that often occurs.

---

Yup, let him say whatever he wants about the signature campaign almost all active and contributing members are participating in.
Remember that before the signature as it is now, we all have been active for a long time and continue to interact.
The signature campaign is just a reward, and I won't even be hypocritical about the money earned, we all benefit from each other.