-
-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] community-platform down/ not reachable #1011
Comments
@chrismclarke @BenGamma Kind of urgent, as no one can use the community platform right now. I think this should be easy to fix. People in the Discord were mentioning, that the academy is not working. |
I don´t know what exactly the issue is with firebase. I created a pull request to revert the last PR on production called "Fix deploys". If that does not work i would just revert production again to #996, which was the last, bigger release. My suggestion is to just revert and wait for @BenGamma to fix the deployment as it seems it was his intention to do so anyways. This way an older version of the website will be running, but at least people can use it in the mean time 👍 :) As there is no one to review - should I just merge it? |
This did not really fix it for me... I will create a PR for reverting to the last production release.. |
yeh same here. still offline. |
Yeah. Seems like the dev site runs the latest master branch. The live version is running the latest production branch. There are also separate deployment scripts for both versions. Somehow Travis CI had problems building the last master/production releases. Could it be possible, that the site was down for 5 days already? |
Mhh. Tried all the builds locally before creating the PR´s and they were working for me 😕 Nevertheless I would suggest jumping back to v1.2.0 now, as it was the last production build which did not fail in Travis CI and then continue finding the error. |
Describe the bug
The community platform is not reachable, because of a broken firebase config/ broken deployment. Seems like the last deployment caused this.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Community platform should work.
Screenshots
![Screenshot_20200824-114533~2.png](https://user-images.githubusercontent.com/8904624/91030513-92c49780-e5ff-11ea-8084-92d5cc5edf6c.png)
The text was updated successfully, but these errors were encountered: