Once again Bitcointalk was inaccessible to him and showed Error 504: Gateway time-out.
After 10 days we have same issue for almost over an hour.
Topic: Bitcointalk: Error 504: Gateway time-out [Update: December 2, 2023] - page 4. (Read 989 times)
November 10, 2023, 02:51:25 AM
After 10 days we have same issue for almost over an hour.
November 02, 2023, 03:37:10 AM
And it happened again even at almost the same time as yesterday.
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.
November 02, 2023, 02:41:34 AM
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 .
And it happened again even at almost the same time as yesterday. I guess theymos need to check what's going around 06:00 UTC .
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.
November 02, 2023, 02:06:52 AM
Is everyone experiencing this error too?
Is this also the same error as yesterday?
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.
November 02, 2023, 01:52:29 AM
Yes it happened again a while ago at 2023:11-02 06:05:00 UTC.
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.
November 02, 2023, 01:44:03 AM
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 .
I guess theymos need to check what's going around 06:00 UTC .
November 02, 2023, 01:38:34 AM
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.
hero member
Activity: 1036
Merit: 933
Find your Digital Services at- cryptolibrary.pro
November 01, 2023, 03:04:21 PM
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.
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.
November 01, 2023, 02:44:10 PM
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.
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.
November 01, 2023, 02:19:27 PM
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.
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.
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.
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. 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.
November 01, 2023, 07:18:53 AM
<…>
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
November 01, 2023, 06:55:50 AM
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.
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.
November 01, 2023, 06:48:54 AM
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.
It was the same weird thing which caused a few hours of downtime 6-12 months ago, and I think it's what causes the few minutes of downtime people observe every few weeks. I've never been able to figure out what causes it. It looks like the network gets cut between the web server and the database for a while. It seems to always happen at around the same time, so I suppose it's probably some automated maintenance process messing something up, but I don't have anything running at this time, so I wonder if it's something in the web-host's networking infrastructure, or something like that. It's difficult to diagnose, since it happens rarely, and usually when I'm sleeping.
I'm planning on upgrading the main servers sometime in the next few months. (Just as part of standard maintenance: there will be no user-visible changes other than perhaps slightly improved speed.) Maybe that'll fix it just by virtue of moving things to different areas.
(The few minutes of downtime just now was due to me doing something, and is unrelated.)
I'm planning on upgrading the main servers sometime in the next few months. (Just as part of standard maintenance: there will be no user-visible changes other than perhaps slightly improved speed.) Maybe that'll fix it just by virtue of moving things to different areas.
(The few minutes of downtime just now was due to me doing something, and is unrelated.)
November 01, 2023, 04:27:25 AM
Is this some kind of silent attack when the householder is asleep?
It seems to happen mainly during sleeping time in theymos' time zone indeed.There was 39 minutes downtime between posts 63086373 and 63086374.
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 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.
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 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.
November 01, 2023, 04:05:51 AM
Once again Bitcointalk was inaccessible to him and showed Error 504: Gateway time-out.
Browser: Working
Cloudflare: Working
Host: Error
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.Browser: Working
Cloudflare: Working
Host: Error
Quote
Is everyone experiencing this error too?
Is this also the same error as yesterday?
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.Is this also the same error as yesterday?
Quote
Surely @theymos is asleep right now and this error escaped his monitoring.
Is this some kind of silent attack when the householder is asleep?
Lol...but at times too, it might be @theymos fixing things himself. Is this some kind of silent attack when the householder is asleep?
November 01, 2023, 03:16:10 AM
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.
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.
November 01, 2023, 02:11:12 AM
It seems to happen mainly during sleeping time in theymos' time zone indeed.
There was 39 minutes downtime between posts 63086373 and 63086374.
It always happens during their sleep hours.There was 39 minutes downtime between posts 63086373 and 63086374.
But why is the error clock always the same?
Downtime is not as long as before.
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.
Yes this is the case as beforetechnical issues that have not been resolved until now,
-snip-
Just remember, even Bitcointalk needs a coffee break now and then! 😉
Hahaha, Bitcointalk is quite tired it seems.Just remember, even Bitcointalk needs a coffee break now and then! 😉
He woke up from his short sleep.
But he always acts up when his boss is sleeping.
Is everyone experiencing this error too?
Is this also the same error as yesterday?
-snip-Is this also the same error as yesterday?
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.
Theymos also said it was a weird thing that caused some downtime.
Some places are still downtime
November 01, 2023, 02:07:48 AM
Is everyone experiencing this error too?
Is this also the same error as yesterday?
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. Is this also the same error as yesterday?
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.
November 01, 2023, 02:03:12 AM
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! 😉
Just remember, even Bitcointalk needs a coffee break now and then! 😉
It was the same weird thing which caused a few hours of downtime 6-12 months ago, and I think it's what causes the few minutes of downtime people observe every few weeks. I've never been able to figure out what causes it. It looks like the network gets cut between the web server and the database for a while. It seems to always happen at around the same time, so I suppose it's probably some automated maintenance process messing something up
November 01, 2023, 01:58:25 AM
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.
Jump to: