"502 Bad Gateway"
- Thread starter loginer
- Start date
-
Throughout the month of April 2024, participate in the FileJoker Thread Contest OPEN TO EVERYONE!
From 1st to 30th of April 2024, members can earn cash rewards by posting Filejoker-Exclusive threads in the Direct-Downloads subforums.
There are $1000 in prizes, and the top prize is $450!
For the full rules and how to enter, check out the thread -
Akiba-Online is sponsored by FileJoker.
FileJoker is a required filehost for all new posts and content replies in the Direct Downloads subforums.
Failure to include FileJoker links for Direct Download posts will result in deletion of your posts or worse.
For more information see this thread.
To be more explicit it's Hongfire, a message board with similar interests as ours. They got some trouble with their server, and they are off until they find a new one.
We guess the extra traffic is due to them.
We guess the extra traffic is due to them.
i kind of feel that this forum has very fragile connectivity ever since that great mess up of hacks and fucked up database & hardwares
high amount of bot poster are the main reason of this :scared:
before I post this I got 503 error, cannot browse (usually at this time I can browse this site a bit freely)
and suddenly when I go to room 203 ( JAV Direct Download sub forum ) there are many posts betwen my previous post and the last post (about 3 pages post )
before I post this I got 503 error, cannot browse (usually at this time I can browse this site a bit freely)
and suddenly when I go to room 203 ( JAV Direct Download sub forum ) there are many posts betwen my previous post and the last post (about 3 pages post )
I think It's not like that on purpose, how many hosts would allow some of our cherished material?
Do we have some problems? There are "only" 2,300 people online now. Seems not more than normally.
yes I am getting them as well, it maybe the server, looking into it. hopefully resolved soon
We all knew this was a possibility. I, for one, am welcome to sacrifice a little inconvience for the greater variety this host is allowing. Hopefully it will in no way resemble the worst connection problems of recent memory.
Thanks again to all the moderators and the new admin for all your efforts.
Thanks again to all the moderators and the new admin for all your efforts.
hi,
the ISP had some severe Problems with Servering so much bandwith - i'm about to fix this (in the worst case, switching the ISP)
I'm also going to tweak some settings, so we can handle even more users (so the plan
- as i said in the other thread, i haven't tewaked that much on the server yet - so hopefully we can get there some decent amount of speed)
this wil happen in the evening CEST and can take up to a few hours (during this time, there could be some more bad-gateway problems, but i will try to hold it short)
the ISP had some severe Problems with Servering so much bandwith - i'm about to fix this (in the worst case, switching the ISP)
I'm also going to tweak some settings, so we can handle even more users (so the plan
- as i said in the other thread, i haven't tewaked that much on the server yet - so hopefully we can get there some decent amount of speed)this wil happen in the evening CEST and can take up to a few hours (during this time, there could be some more bad-gateway problems, but i will try to hold it short)
i have tweaked some database-settings (some not so trivial settings)
unfortionately this can lead to some problems (as we had about an hour ago.).
I now have updated the settings - so that this will hopefully not happen again.
As for this. We probably have lost a few posts - i'm sorry about this.
unfortionately this can lead to some problems (as we had about an hour ago.).
I now have updated the settings - so that this will hopefully not happen again.
As for this. We probably have lost a few posts - i'm sorry about this.
Last edited:
so
after investigation a bit - i found no real problem at the main-servers. - The only problems found where some not existent email-adresses, to which the system tried to send mails.
(there were some DB-Problems, but the automatic analytics has found and repaired them)
as for this morning (around 10AM CEST) the Datacenter, where some of our services are hosted, had a severe routing problem - thus, there should be seen an error for some users (not all should be affected) - Though i think, the same happened at 0:00 yesterday.
i'll go and talk to the Provider - this isn't s.th. we can tollerate.
we are still trying to find hoster that will allow all the content here, and provide a good service - wich isn't that easy.
As well as managing a decentrialized system.
Everytime one of you can get an error, it's hard to track down where this has happened. I've just uppdated my monitoring adding more services - so that i hope i'm able to track down future problems better.
i've just updated our DB-Cluster in order to not overload the DB-Systems (which shouldn't happened, but well... let's see)
oh perhaps you have noticed, that posting a post can sometimes take a few seconds longer - that's the problem on clustering the DB. But it should be tollerable (i hope)
after investigation a bit - i found no real problem at the main-servers. - The only problems found where some not existent email-adresses, to which the system tried to send mails.
(there were some DB-Problems, but the automatic analytics has found and repaired them)
as for this morning (around 10AM CEST) the Datacenter, where some of our services are hosted, had a severe routing problem - thus, there should be seen an error for some users (not all should be affected) - Though i think, the same happened at 0:00 yesterday.
i'll go and talk to the Provider - this isn't s.th. we can tollerate.
we are still trying to find hoster that will allow all the content here, and provide a good service - wich isn't that easy.
As well as managing a decentrialized system.
Everytime one of you can get an error, it's hard to track down where this has happened. I've just uppdated my monitoring adding more services - so that i hope i'm able to track down future problems better.
i've just updated our DB-Cluster in order to not overload the DB-Systems (which shouldn't happened, but well... let's see)
oh perhaps you have noticed, that posting a post can sometimes take a few seconds longer - that's the problem on clustering the DB. But it should be tollerable (i hope)
Last edited:
unfortunately i've logged a few retries of database-queries on one of our notes. Though i'm not so really sure why this has happened - it's also only on one of the databases.
i'll look into it - later
Anyone still has problems with 502-error?
Up until now, it looks okay - yesterday we served over 3.5k users without a noticable slowdown of the system.
i also hope, that we can handel the load on weekens (which we should if the DC don't cut us out <.<)
i'll look into it - later
Anyone still has problems with 502-error?
Up until now, it looks okay - yesterday we served over 3.5k users without a noticable slowdown of the system.
i also hope, that we can handel the load on weekens (which we should if the DC don't cut us out <.<)
yay.
we are suffering under our first small DDOS-attack (no need to worry, it's really small) (and first one on this new server-setup)
Moreover, for the last few days, we have logged over 1k attempts trying to brute-force into our Servers - nice try
our network is mitigating the attack - the only thing is, that one of our servers will react slower as usual (mostly since it's busy inspecting the the incoming packages).
As for some 504 Errors - i've figured out that this happens when two of our users tries to insert a query in the same millisecond on the same DB. Then the board won't always try to redo the action and fails on loading the page.
This is an error, that i can't resolve - but I'll open a ticket and we will see what will happen
we are suffering under our first small DDOS-attack (no need to worry, it's really small) (and first one on this new server-setup)
Moreover, for the last few days, we have logged over 1k attempts trying to brute-force into our Servers - nice try
our network is mitigating the attack - the only thing is, that one of our servers will react slower as usual (mostly since it's busy inspecting the the incoming packages).
As for some 504 Errors - i've figured out that this happens when two of our users tries to insert a query in the same millisecond on the same DB. Then the board won't always try to redo the action and fails on loading the page.
This is an error, that i can't resolve - but I'll open a ticket and we will see what will happen