-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
Webmentions fail with a HTTP 500 error message #3199
Comments
I tried webmention.rocks to see what went wrong, and it does indeed return an error 500, as seen here: https://webmention.rocks/receive/1/5adc8828e60114ed40ac5bc9bc70d4b3 (only live for 48hrs), with the error message:
I will raise this with my hosting provider, but I'm also curious if anyone using Known have come across this issue before. I've not been able to find any other issues filed describing this. |
I'm going to run some tests at my end and see if I can reproduce the issue. |
It's happening for me too.... |
Hi @lindner
Would you by any chance happen to be using shared hosting on Dreamhost? |
While trying to do this:
Backfeeding comments and reactions from Mastodon to my Known site using brid.gy
I encountered this error:
brid.gy gives me error icons for webmentions.
Ryan from brid.gy says my webmentions endpoint is failing with the following HTTP 500 error:
Some other notes:
This seems to have started happening around 4 months ago. The last post where webmentions were working, is this one. It might all be down to my shared hosting provider (Dreamhost), but I wanted to bring it to your attention as well.
I'm not sure where to look for a fix (my Webmention troubleshooting skills are highly underdeveloped), short of upgrading to the 1.6 release.
Any suggestions appreciated (:
Give us some context:
It'd also be really handy if you could tell us the contents of your
version.known
fileWhat database are you using? (e.g. mongo, mysql, postgres)
Any warnings or errors in your admin/diagnostics page?
If this is a programming bug, can you include examples of any Micropub / API calls / webhook pings you make? Otherwise please don't worry about what this means!
Bonus points - are you able to illustrate the issue with a unit test? If so, submit it as a pull request!
The text was updated successfully, but these errors were encountered: