503 error using v3 endpoint #307
Comments
|
Working on the same project, as unpreceden7ed, giving a screenshot of the error. Seems to be CORS related.
|
|
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. |
|
Thanks for the great info. Looks like I need to spin up a new instance for myself. Always fun. |
|
I also hit this error by using the default API endpoint in the theme Hugo Future Imperfect Slim.
Needs to try other instances: |
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.
* 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
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.
Staticman official instances are unavaible, as reported in eduardoboucas/staticman#307
|
I've picked up this project. The staticman public instance is not functional right now and your best bet is rolling back to a previous commit you know was working before and self hosting. |
|
Duplicate of #317 |
|
@VincentTam I still get this error, using staticman master ("deploy to heroku"), and Hugo Future Imperfect Slim. I assumed that this master branch would have resolved this at this point (based on #319 and such). Do you have any tips? |
@RyanTG I'm sorry I'm now occupied with my job training & I'm learning C#. I haven't followed the development of Staticman for a year. I might retake this if I've free time again. |
|
No problem, good luck with your training. I opted to use staticmanlab, and that's been working for me. But, I question if that's a sustainable approach, given that you're not actively involved. But at any rate, thanks for that tool! |
I'll leave this question to others, while trying to find time to pick up Node.JS (maybe several months) later. |
|
@RyanTG when did you deploy Staticman to Heroku? Prior to about 9 days ago when #346 was merged, master was still broken. As of right now, deploying master to Heroku should be working. As far as sustainable approaches, this project currently in need of maintainers. I do my best to resolve any breaking issues as they pop up but do not have much time to actively work on Staticman development lately. |
|
Yes, it was within 9 days (7 days ago). I don't know enough about staticmanlab to know what is different with that setup. But once it worked with that app, I gave up on troubleshooting my 503 error. |
|
@alexwaibel I can confirm master works on Heroku, or at least the master I forked yesterday: https://github.com/shaftoe/staticman I might have some time to help out here, where should I start from? |
I'd greatly appreciate your contributions @shaftoe! The highest-value item right now is definitely updating the docs on the website. They're super out of date at the moment so it would help a lot of new users if we added things like notes about setting up Heroku instances and whatnot. Should be a good starter task too getting used to the whole system. Right now we have some great articles that I've been pointing users to, but having this info on the site would be better. Relevant links: |
|
I wonder if my issues were theme-related. I read all those relevant links when setting it up. I'll give it a shot with another theme, not https://github.com/pacollins/hugo-future-imperfect-slim, just to rule that out. |
Revert "[Feature] Archives"
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.
The text was updated successfully, but these errors were encountered: