Topic: 502 Bad Gateway (Read 3992 times)
Fixed it. Sorry about that. There are branches being merged in. I will completely be honest that we are untangling some things at the moment. Thanks for being patient guys!
Seems to be bit old but I am encountering new error. Its error (504) via master 1 , forum is overloaded . However this happened to me two times only. Willing to know if this has happend with any other community people.
I believe you are referring to this forum software (SMF)? I haven't faced any issues on the new beta myself but I'm getting that 504 error here while trying to post or sending private messages sometimes, refreshing the page seem to do the trick. It's worth reporting If you get more errors in the future.
The old error is completely resolved now.
Your "new error" is one I get on this forum and I believe it's due to sending two requests to the server in a second (the server sends the 504 error in order to stabilise itself as it is designed not to do more than one thing to each ip in the same second because it isn't really useful for a forum to neeed to be faster.
Seems to be bit old but I am encountering new error. Its error (504) via master 1 , forum is overloaded . However this happened to me two times only. Willing to know if this has happend with any other community people.
I believe you are referring to this forum software (SMF)? I haven't faced any issues on the new beta myself but I'm getting that 504 error here while trying to post or sending private messages sometimes, refreshing the page seem to do the trick. It's worth reporting If you get more errors in the future.
Seems to be bit old but I am encountering new error. Its error (504) via master 1 , forum is overloaded . However this happened to me two times only. Willing to know if this has happend with any other community people.
Not sure if this has been discussed before but are you accepting any pull requests at the moment ? I can write end to end tests with jasmine and cross verify if the things are working as they should be.In case of a feature request or a bug,it would only make sense to write code if you're accepting requests..
Yes we are. It'd be great if you're open to contribute! There's also a developer slack. Please contact me on Github if you would like access.
Sure, our source code isn't in Java though. Take a look at our repos and see what you have to offer. Data migration isn't a small thing 
Take a look:
https://github.com/epochtalk/epochtalk
Not sure if this has been discussed before but are you accepting any pull requests at the moment ? I can write end to end tests with jasmine and cross verify if the things are working as they should be.In case of a feature request or a bug,it would only make sense to write code if you're accepting requests.. Take a look:
https://github.com/epochtalk/epochtalk
Server's back online.
Just checked it then, no 502 error.
Just checked it then, no 502 error.
Sure, our source code isn't in Java though. Take a look at our repos and see what you have to offer. Data migration isn't a small thing
Take a look:
https://github.com/epochtalk/epochtalk
Take a look:
https://github.com/epochtalk/epochtalk
Sorry about this sorting out data migration issues. Will update when finished.
this is not funny brother
over $1 MILLION USD paid for development and sorting out data migration issues for weeks
502 Bad Gateway
please, no - do you need help? i am a professional java developer
Sorry about this sorting out data migration issues. Will update when finished.
Hi all, beta will be back up this week.
It's being almost two weeks now, Is there is anything to be worried about at this point? Honestly, I know you are doing your best but If this continues, the final release will never see the light.
Looking forward to seeing the new forum software. While I am not as active as I once was I came along to Meta to read the "where is the new forum software" posts, to find that there is a beta in flight (or not) at the moment.
Exciting times, hopefully worth the wait ;-)
Exciting times, hopefully worth the wait ;-)
Hi all, beta will be back up this week.
Theymos should be smart enough to not deal with people through the internet only and instead meet with them face to face sometimes. It's better to stay optimistic, they made a couple of communits a couple of days ago, hopefully they are working on something : https://github.com/epochtalk/epochtalk/commits/master
So our work has been happening parts of the system that's not master. Also users like Mitchell (moderator) has been contributing some work. Master is now a protected branch and needs peer review before merging.
I wonder if we will be seeing a seven figure Scam Accusation soon...
Theymos should be smart enough to not deal with people through the internet only and instead meet with them face to face sometimes. It's better to stay optimistic, they made a couple of communits a couple of days ago, hopefully they are working on something : https://github.com/epochtalk/epochtalk/commits/master
So our work has been happening parts of the system that's not master. Also users like Mitchell (moderator) has been contributing some work. Master is now a protected branch and needs peer review before merging.
I wonder if we will be seeing a seven figure Scam Accusation soon...
Theymos should be smart enough to not deal with people through the internet only and instead meet with them face to face sometimes. It's better to stay optimistic, they made a couple of communits a couple of days ago, hopefully they are working on something : https://github.com/epochtalk/epochtalk/commits/master
It's being almost a month now, anyone knows what's the issue or If the developers announced anything? theymos removed that message on the news section regarding changing our emails, I guess we will have to wait even more until the final release
I wonder if we will be seeing a seven figure Scam Accusation soon...
It's being almost a month now, anyone knows what's the issue or If the developers announced anything? theymos removed that message on the news section regarding changing our emails, I guess we will have to wait even more until the final release
I'm currently getting a 502 Bad Gateway Error when trying to access beta.bitcointalk.org --
on another note,
is the day approaching at which I come to bitcointalk.org and am greeted with the new EpochTalk software by default?
on another note,
is the day approaching at which I come to bitcointalk.org and am greeted with the new EpochTalk software by default?
I'm getting the same problem.
They're probably just updating the site or experiencing some downtime, it'll proably be back soon.
How long has this error been going? (the release is probably close now).
EDIT: I think the server's offline. When I tried pinging it, all that was returned was "request timed out".
it would just timeout outright if that was the case. I think there is an error in their nginx conf file that is causing it to return the 503 error. I've had it happen when i configured rate limiting wrong that it would throw this to my users.
I think when I pinged it from the command line, it returned a "request timed out" due to it being configured well. If you ping this forum, you also get the same error and you can see that it is online.
This is the current IP of beta.bitcointalk.org: 75.101.133.199
If you type that into any browser you get the nginx setup index file which is used to test that a server is configured well with it.
This means that some of the site has been taken down? Possibly to improve it as there were a lot of bugs from the github "issues" page.
I'm currently getting a 502 Bad Gateway Error when trying to access beta.bitcointalk.org --
on another note,
is the day approaching at which I come to bitcointalk.org and am greeted with the new EpochTalk software by default?
on another note,
is the day approaching at which I come to bitcointalk.org and am greeted with the new EpochTalk software by default?
I'm getting the same problem.
They're probably just updating the site or experiencing some downtime, it'll proably be back soon.
How long has this error been going? (the release is probably close now).
EDIT: I think the server's offline. When I tried pinging it, all that was returned was "request timed out".
it would just timeout outright if that was the case. I think there is an error in their nginx conf file that is causing it to return the 503 error. I've had it happen when i configured rate limiting wrong that it would throw this to my users.
Still 502 here 
Not just you. Also tried accessing it today and gets the same error. Tried refreshing and nothing happened. 
Still 502 here
Jump to: