Skip to content
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

503 error using v3 endpoint #307

Open
unpreceden7ed opened this issue Jul 23, 2019 · 4 comments

Comments

@unpreceden7ed
Copy link

commented Jul 23, 2019

Hello,

Our team has been using v3 endpoint of the application for a while now and we're experiencing a 503 error. This normally infers an issue with the application's end, so I'm pinging @eduardoboucas for assistance on getting the application back up to speed, if needed.

@casually-creative

This comment has been minimized.

Copy link

commented Jul 23, 2019

Working on the same project, as unpreceden7ed, giving a screenshot of the error. Seems to be CORS related.

image

@casually-creative

This comment has been minimized.

Copy link

commented Jul 26, 2019

I want to make a statement to our progress.

We moved away from the public instance because it's not working anymore, as what this issue is about. We have set up our own instance on heroku and it's working fine as of now. However, we didn't clone this repository because apparently, it's in a broken state. Instead, we cloned the deploy branch of @VincentTam's fork. He went through the effort of merging PRs which brought the repo back to a working state, as explained in #299. Thank you Vincent for that!

So to recap: the public instance is broken because of a CORS / internal issue, the self-hosted instance is broken because of legacy functionalities not working because of v3.

Pinging @eduardoboucas to make you aware of this situation.

@dancwilliams

This comment has been minimized.

Copy link

commented Aug 16, 2019

Thanks for the great info. Looks like I need to spin up a new instance for myself. Always fun.

@VincentTam

This comment has been minimized.

Copy link
Contributor

commented Aug 16, 2019

I also hit this error by using the default API endpoint in the theme Hugo Future Imperfect Slim.

Screenshot_2019-08-16_23-15-28

Needs to try other instances:

VincentTam added a commit to VincentTam/hugo-future-imperfect-slim that referenced this issue Aug 17, 2019
Staticman nested comments support from Huginn
which is in turn a port from halogenical/beautifulhugo#222.  Introduced true
nested comments with reply functionality.

1. Reply target anchors to easily jump between replies.
2. Interactive reply target display with Gravatar and name.
3. Improved input type for "website" field.
4. Implemented FR pacollins#63 to construct POST URL in JS.
5. Clearer instructions for Google reCAPTCHA v2.
6. Introduced some SCSS variables for layout control
7. Fixed missing "id" attribute in each comment.
8. Fixed missing translation UI text for Staticman forms.
9. Changed default API endpoint to the one serving @staticmanlab due to
eduardoboucas/staticman#307.
VincentTam added a commit to pacollins/hugo-future-imperfect-slim that referenced this issue Aug 22, 2019
Staticman nested comments support from Huginn (#69)
* Staticman nested comments support from Huginn

which is in turn a port from halogenical/beautifulhugo#222.  Introduced true
nested comments with reply functionality.

1. Reply target anchors to easily jump between replies.
2. Interactive reply target display with Gravatar and name.
3. Improved input type for "website" field.
4. Implemented FR #63 to construct POST URL in JS.
5. Clearer instructions for Google reCAPTCHA v2.
6. Introduced some SCSS variables for layout control
7. Fixed missing "id" attribute in each comment.
8. Fixed missing translation UI text for Staticman forms.
9. Changed default API endpoint to the one serving @staticmanlab due to
eduardoboucas/staticman#307.

* Added image alt text in response to the review bot

Gravatar alt text wasn't there in the original code, but I agree with the bot.

* Fixed clearForm() to clear fields after submit

* Set opacity to 0.5 when submitted

* Regenerated resources

* Fixed clearForm() again to empt textarea

* Corrected Eng submission msg
VincentTam added a commit to VincentTam/hugo-swift-theme that referenced this issue Aug 23, 2019
Updated site config file template's default API
So as to match the change in Staticman's default API introduced in onweru#36.  Note
that onweru#36 is a breaking change. for users who have set Staticman `endpoint` to
the empty string "".  However, the official production instance has already
broken, as reported in eduardoboucas/staticman#307, so this commit is simply an
info update.
VincentTam added a commit to VincentTam/beautiful-jekyll that referenced this issue Aug 28, 2019
Revert 559840c
Staticman official instances are unavaible, as reported in eduardoboucas/staticman#307
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.