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

Pingdom DOWN alert:
bitcointalk.org (bitcointalk.org) is down since 02/12/2023 05:30:39 AM.
Reason: Could not find redirect location


PingdomAlert UP:
bitcointalk.org (bitcointalk.org) is UP again at 02/12/2023 07:09:39 AM,
after 1h 39m of downtime.

Yes, we can ignore it and the 1-minute downtime won't affect anything for the forum.
Thanks for the advice, I'll also come back with longer downtime if that happens again.
I always get early downtime notifications with the tools I use now.

I believe we can overlook this brief 1-minute downtime. It seems likely that it was caused by a network issue unrelated to the problem we typically encounter.

Therefore, we can affirm that since the last downtime on Monday, November 13, 08:17:19 UTC 2023, we haven't experienced the usual issue. Right?

This particular time-out lasted for a couple of hours. Not more than 2 hours even, how's that going to affect signature participant? Two hours of interruption won't stop you from making any amount of post you want and it also won't make you miss a deadline.

What business on the forum will make people lose millions, talk more of billions within hours of the site being down?

Your theory is too exaggerated 😂

Forums don't have a business losing huge losses due to downtime in just a matter of hours.
It's not even a state-run business or forum for commercial purposes.

This is just the Bitcointalk forum, a Crypto discussion forum with many projects that will not suffer losses due to the downtime that occurs.

---

As @Rikafip said, I can't think of anything about a business that has lost millions/billions of dollars just because of Bitcointalk downtime.

@digaran boss is all too eager to solve the downtime problem with the Billions of dollar loss conspiracy theory.
It seems that he has not seen Behind The Scene from a drama movie.

Lol you serious, forum being down for an hour or two (and often even less) once in a while resulting in loss of millions/billions of dollars? Tell me a business here that can't wait for an hour and that is seriously affected with this as I can't think of any.


You rarely see something as far fetched as your theory even in movies.

Ok, this is just a theory and don't know how valid it could possibly be.  What if there are a few members suspected to be Satoshi, and these blackouts are the works of a state trying to perhaps disconnect the internet even for a few seconds in certain countries to check if those suspected members get affected, and that way they can locate from which country he is connecting to the forum?

Just a theory, boss dragon be careful.😉

Getting Downtime information again, but only my 1 minute duration.
But it does not affect the use of forums and this is still quite normal.

This frequent scenario in the website is affecting businesses in the forum. I don't know how many millions or billions are lost whenever the forum is down. Because this happened to Facebook last year and for about 5-6 hours in the day and people lost a lot money. Not that they we scammed but business activities among customers. And I believed this is what has been happening in the forum whenever the forum is down.

Therefore I will like the admin to do something about it because the businesses in the forum is very high so whenever the forum is down clients and managers and participants too are worried.

As long as the forum can still be accessed and the downtime only takes 1-2 hours, it is not a problem and not worrying.
We both assume this is the fault of Cloudflare as the host provider, and they also need to do some checking for downtime issues that occur.

New forum software?
is this some kind of update to the SMF forum and other software

But for the Forum upgrade, @theymos said back in October that there will be a major server upgrade in the coming months (maybe next year),
as standard maintenance and there will be no significant changes to the user experience, but it may improve the speed of the forum.

No you are not alone here. We, everyone is facing the same problem.   This problem wasn't that frequent in the past. That may be the reason you hadn't noticed it until now. But it become more frequent for the past few months. Within months I faced the issue 4-5 times, if I remember correctly. Even yesterday, the same issue happen. The downtime gas also increased. Yesterday it was down for 2 hours. The highest downtime I think was, 3hr 21 minutes something. I don't  remember. But before, it wasn't that much, so it didn't caught your eyes. Just look at what theymos said.

I thought I was the only one counting. I noticed this and it is a bit worrisome. I am a technical person in the area of website downtime and Cloudflare error issues but If I may ask, and pardon my question, can these frequent issues be resolved with a new forum software(I don't know if there is anything like this) or a forum upgrade?

Sometimes, it's like turning the router on and off again and again to fix the connection issue. But little did we know that the router was fine, the problem was with the ISP. Also, the same thing happens with bitcointalk. Whenever it's slow, lagging, or not working, I keep refreshing my browser, hoping to fix it. But it won't. Later, I would realize that it's not my problem, but everyone has it because of downtime. 

BTW, did anyone find the reason for this frequent downtime? In just one month, I faced this issue 2-3 times.

The forum has an official Twitter and an unofficial Discord. You can get information there.

Invitation link to Discord https://discord.gg/9YUNn8nBGU

Twitter account https://twitter.com/bitcointalk

If we don't have access to the forum, it appears when we run out of power to access our PC, or when we leave our smartphone at home.
It seems like we don't know what to do... 

When forums cannot be accessed, we all feel disconnected and confused about where to ask. Is there a Telegram channel or maybe a Twitter handle managed by the forum administrators to provide updates on forum-related announcements?

For example, like the down case this afternoon, I felt confused about verifying if the server was actually down for everyone or just for me. I also want to ask someone who may often access the forum but still can't, because I'm new and don't have any friends yet to exchange contacts.

It was a little difficult for me to determine if it was a server issue when there was no one else with me who was familiar with the forums either.

Yes, you have to ask @Cyrus or @theymos for this problem.

---

I even stay awake and monitor the forum.
But where [ASIA-Indonesia] is at 6.00 am UTC It's still daytime for me.

---

Yup, the only one who will solve all these problems is the server owner who can access the backend server, and the forum administrator as a server customer.

---

what to fear, I think they are still trying to resolve this downtime issue.

I thought it was 10 minutes, but it seems that it took longer. It is noticeable that they happen at similar times, almost the same time interval, which appears to be an hour late in US time. The frequency of such downtimes is what scares me more than their length.

I take this as a sarcasm, sorry it sounds stupid since I have no coding skill.

Yep, I guess The Glider should be the one who will try to resolve this.

I don't think this falls under the bounty rewards. However, if someone provides a smart suggestion or a hint that aids theymos in pinpointing the exact reason, I'm sure they could earn a badge

But, to determine the exact cause, you would undoubtedly need access to the backend server during the downtime, which is not going to happen.

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.

You think? Well you may be right but I feel that it's not only those who are in sig campaigns that worry when there's a downtime because there are also users who don't visit the forum just to complete post quota but to do other things. Believe it or no, the forum is not in existence only for the signature campaigns but to disseminate information about Bitcoin and it's functionality, these campaigns are just a by product.

 The way you sound is as if it's every one that depends on the proceeds gotten from the campaigns alone. I'd love to change that impression but I find it might be unnecessary because you've chosen to believe that.

It is a website visited by thousands of people all the time.
Even the largest websites in the world suffer moments of instability, when they experience a significant increase in hits.

It will always be impossible to guarantee 100% uptime. Perhaps we have felt this more in recent times, because it has appeared more frequently.

However, @theymos has already announced that it is preparing improvements, which should come into force at the beginning of next year. Therefore, it is important to have patience and understanding when this occurs.

this becomes scary for the signature participants only

I have been on this forum since 2012. I have seen 100 outages in the 11 years I have been on this site.

There always seems to be more down time when BTC starts to bull run.

Yes, the forum crashed again for exactly 3 minutes and then came back online.

Looking at the Result Log the Downtime locations are Amsterdam, Madrid, Oslo and Seattle 2.



The Amsterdam server I see often experiences downtime compared to other servers.

Outage analysis of bitcointalk.org

Just now the forum error again showed as the OP said but it did not take long only a few seconds or approximately 1 minute, but I see lately the forum often has problems, what is really happening?

Just now you felt the same thing?

I can't answer to that, and you're right, well, even theymos just think it that way, we dont know what he already did to fix this or if there is need to fix since we didnt heard him yet.

The reading on Pingdom only starts when I add bitcointalk.org to the Pingdom uptime list.
So the uptime below 90% is the interval from the first time I added it which was when Donwtime was last yesterday.

But it will keep running and will tell how the website is working and will get email alerts when downtime occurs.
But yes this is only valid for 30 days trial and have to renew for next month to keep getting premium features.

The server update is completely done by the administrator, we just need to wait for @theymos to fix everything.
But there is no recent statement from @theymos about the downtime problem that always occurs and how to follow up.

The uptime that appears in the image is related to what time interval? A month, year, week?
If in the last year the uptime is below 90%, it is really not a good sign.

We hope that the planned renewal of the servers will resolve most of the problems that occurred.

Will it always be scheduled maintenance without any prior confirmation?
There should be an explanation for all these downtime events, as some people are starting to speculate about strange things.

---

This is just a kind of monitoring website that can do real-time testing.
The name is Pingdom
a tool used to test websites.

Pingdom Tools itself operates online and is also freely available to
anyone who wants to try it (30-day trial).
Pingdom provides valid analysis reports
related to load time, page size, website structure details, and total number of HTTP
requests.

You will also receive email alerts about website uptime, website speed, and more.

Which website/service does push out alerts like this if you don't mind sharing.

---

Lol. This has nothing to do with Bitcoin mixers. DDoS attacks or downtimes can have to any site, including big ones like Twitter or Facebook. If the Law enforcement authorities were unhappy with how mixers are being advertised in this forum. They would have already contacted admin by now or even completely seize the forum and shut it down, which wouldn't be hard for them. You are just over imagining.

This mere forum has nothing to do about those shutdown mixers. Yes, they can advertise here, but nothing more than that.

Since this forum's hosting server(namecheap) is based on US and if they wants to summon theymos to the court for some legal reasons they do that already if there is, and they can just request to namecheap to shutdown the site's server for good. But that:s not the case. As per theymos, the downtime is almost the same hours from previous ones, and conclude its just a scheduled maintenance from the hosting, nothing more.

Which mixer are you referring to? You need to be more specific, given that there have been multiple mixer sites shut down by the FBI/Europol.
But, I fail to see the relevance to the issues with the bitcointalk hosting server.


And what if the cause of the problem lies on the hosting side, as theymos has already mentioned? How will having a .onion mirror domain help in that case?

I might be wrong or it might be my ignorance. Isn't this issue of seeing the forum down became more prevalent after the Bitcoin mixer issue. I mean it is more frequent and long lasting before the mixer got down by the FBI. I think there is something wrong and I feel the admin should have two urls. One .org and the next should be .onion.

I encountered it again around 8 to 9 am my local time even as I was active around 1 am to 4am forum time I didn't experienced any downtime and this could probably be some host error, although I don't usually panicked anymore because I know too well after 20 to 40 minutes times it will get cleared off. And I want to asked is there no alternative way to get this error finally put to an end? Sometimes it's very annoying when posting and one encountered such error sometime I do lost my composed post, and again whenever you writing a post without previewing yet and you mistakenly lost the post it's very hard to create back same quality of the post you already lost.

Theymos wrote this:
I'll use my deleted posts archive to see gaps between posts, starting at post 63 million (October 17). I'll only show gaps larger than 3 minutes between posts (which could mean the server was inaccessible, but it could also mean there simply were no new posts for 3 minutes).

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

Most of those are at UTC night, but Ninjastic Space's graph confirms users are less active at that time, so there could be many false positives in my list.

Note to self for updates: see find_gaps_between_posts_to_track_server_downtime.txt

FFS. 

It's happening at 6:00 AM UTC every time. So maybe Theymos can get up at midnight once and check all webhosting scripts and/or cronjobs which are talking to the DB to find the culprit.

I do not think it was a short time as i was trying to access the site for quite some time but to no avail.

Once i knew there was some issue, i kept on refreshing on my mobile. Same Error code 504 as mentioned by the OP.

And it happened again at almost the same time with more than 1 hour.

This seems to be a fairly routine moment these days.

Cloudflare hosts are always having issues, and downtime happens during @theymos' sleeping hours.

The only thing that needs to be done is to contact the Hosting provider and make sure that the
- The origin server can respond to hostname and domain requests in visitor URLs that generate 502 or 504 errors.
- Investigate excessive load and server failures or network outages.
- Identify applications or services that are timed out or blocked.
https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/

I now also have an Alert for Bitcointalk Downtime and this will monitor what happens when downtime occurs.

Another short time attack.

After 10 days we have same issue for almost over an hour.

That definitely means it's an automated maintenance work, like a cronjob, or system updates, or the like.

Does anyone know what is the hosting provider for Bitcointalk? Maybe @Cyrus can help out with this since he's in charge of the hosting (I guess?). Or maybe this operation is self-hosted so they can look into this directly.

And it happened again even at almost the same time as yesterday.
Could this be a network anomaly or even some repair from the central server that somehow always happens at the same time with different durations.

Until now @theymos is still not active and there has been no response from theymos.

Tomorrow we should all be prepared to see if this error will happen again or not.

Since it is Error 5XX, It is a server error and you can only wait until things return to normal, but be prepared that this happens randomly and once every two weeks to three hours and often happens between 3:AM UTC and 10AM UTC.
504 Gateway Timeout Error almost indicates that the main server was unable to access the database, whether the problem was from cloudflare or from the database.

I saw this error for very short period today at least twice. So maybe something happens, as admin thought, when some program tries to start to do something. It probably tried to start at least twice today and maybe it did what it expected to do and that's why it is over so fast. Or maybe it uses so many resources that it freezes the server when overuses server resources... Both cases could look valid, but of course it would be good to know the exact reason, to not to face that one day forum will be off for days, not just minutes or hours.

Yes it happened again a while ago at 2023:11-02 06:05:00 UTC.  So it's happening frequently and we have quite a pattern, usually occurring right after 06:00 UTC

I guess theymos need to check what's going around 06:00 UTC .

We are experiencing it more now but as @theymos has already announced new updates to handle it we can expect it to run smoothly after that but have faced this issue long time ago so maybe was not online again to witness this error again.The last time I faced this error it lasted for several minutes I guess when most of us faced this situation but hope it gets better from next year.

Owh , I see I'm not the only person who have faced it. But in my case today it doesn't show the gate way time out But bitcointalk was taking a long time to load in my browser meaning it was not loading just shows a blank page and showing no error.
Then I checked bitcontalk website status on  this website(isitdownrightnow)(I actually don't know if it actually shows the correct status) and also asked my local mates if they are also facing this error.  But this website shows that it was down thirteen hours ago.  So I was little confused with the problem seems to be with my network but my other browsers were running fine.  Anyway now your topic cleared my confusion.

I didn't realize it because I just got online on the forum and saw this thread now 1 hour ago, so didn't feel today the forum experienced a '504 error' 

I wouldn't mind if it's just for a moment, maybe it's true that the forum needs a break. Lol
But when this error occurs I'm sure many will think that it's the internet that's the problem but the forum host is the problem.

It is not new to me anymore, because sometimes when I am less busy and decided to long in, it shows this error but after a while the forum will be accessible. The first time that I experienced this, I was worried because I thought that it was from my end not until I understood that it was from the from network server.

When next you experience this, just relax or take a nap and check back later, by then it will have been fixed. Although, it still depends on the time that we login to the forum. I believe some forum members rarely experience this because of their time zone and the time that they do login.

No worries, type on a notepad first before pasting it on the forum, instead of writing directly on the post that you want to reply, so that whatever happens, your post is save on your notepad. I hope that you are relieved now.

It’s not something that is really that frequent nor, in general, something that lasts for a noticeable period of time.

Concerning your post, if you happened to preview it at some point, you should find a corresponding version stored in your Drafts: https://bitcointalk.org/index.php?action=drafts

I'm new here and I don't have much experience in the forum. So It same with me I faced this problem while I was writing a post this morning this appeared ( Error 504: Gateway time-out.)
 Honestly, this is a bit annoying and I lost my post before submitting it, I hope this is something to not worry about in the future.

This has happened before. The last time it happened if I remember correctly it was more than 3 hours. Recently this is happening more frequently.  As far as I know if it's for only a small amount of time, then theymos might be doing something which caused this.

Well, maybe it's time for @theymos to change his sleep schedule! But, don't say anything to anyone, so that these "people" don't do their thing again. 




It is true that we have had several of these records. But we also cannot forget that the forum is visited by thousands of people all the time, and the more people there are, the easier it is to detect these cases.

@theymos has already informed that an upgrade to the server is planned at the beginning of next year. Therefore, we must try to know how to deal with this situation, until this upgrade occurs. The forum is too big to make these changes from one day to the next.

This is how it always happens where the Host would be the error and others would be working just fine. But I didn't experience it again after the last one that happened weeks ago.

Even yesterday? That's becoming rampant and I guess those who used the forum early experienced it. It's still good that it didn't last long compared to the earlier ones and I hope it's fixed completely ASAP.

Lol...but at times too, it might be @theymos fixing things himself.

It seems like this issue is starting to reoccur, as I can't even remember how many times I have experienced it as a result of being active when it happens or most members complaining and posting about it.
 
Have the administrators been able to talk about what usually causes this and if there is anyway to get rid of it once and for all, or is it something that we should just get used to for the time being until further notice?

The last one that happened, which lasted for almost an hour, was the longest I have ever experienced. I hope this gets fixed and we don't have such experiences again.

It always happens during their sleep hours.
But why is the error clock always the same?
Downtime is not as long as before.

Yes this is the case as before
technical issues that have not been resolved until now,

Hahaha, Bitcointalk is quite tired it seems.
He woke up from his short sleep.
But he always acts up when his boss is sleeping.

It's not a common error when it happens repeatedly and there's no fix.
Theymos also said it was a weird thing that caused some downtime.

---

Some places are still downtime

If you see error 504, it means that the site is not working. It means that everyone that wants to connect to that site will not be able to but getting the error.

This error is very common on this forum but not taking long. Yes it is the last error that makes people not able to access Bitcointalk but also just for a short time.

It looks like Bitcointalk is wide awake from its short nap, and it's running smoothly on my end (post, messages, ect) at least for now. Sometimes, these errors can be specific to certain scenarios or connections, like thyemos pointed out last time (weird thing) might be causing this issue again.

Just remember, even Bitcointalk needs a coffee break now and then! 😉

Maybe this is just a rare case just like what always happened before. If this is an attack, we will surely experience worse than this — longer timeout.

I do experienced it as well but from when I come online I didn't noticed it but after like few minutes it came back again. I was actually thinking is my network so I tried to switch between my SIM network to get a smoother operation and access to forum yet I couldn't, it was then I know is just a kind of technical issues which will be back within few moments. No too long I received a message from telegram bots then I know is back again.

It seems to happen mainly during sleeping time in theymos' time zone indeed.

There was 39 minutes downtime between posts 63086373 and 63086374.

Once again Bitcointalk was inaccessible to him and showed Error 504: Gateway time-out.

Browser: Working
Cloudflare: Working
Host: Error

Is everyone experiencing this error too?
Is this also the same error as yesterday?

Surely @theymos is asleep right now and this error escaped his monitoring.
Is this some kind of silent attack when the householder is asleep?