Broken/Missing Medium URL Redirections #64
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
renovate-bot
renovate-security
security
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: realaravinth/libmedium#64
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
I have attempted to deploy a LibMedium instance with limited success. However, none of the URLs are being redirected properly, instead resulting in a blank page instead. Here is the
config/default.toml
contents, which currently lacks clear documentation:Additionally, here is the truncated Caddyfile contents:
Command:
I have previously deployed a Scribe instance using the unofficial community Docker instructions, but its SourceHut repository is unmaintained, so I want to switch to deploying a LibMedium instance instead.
Frank
Hi, can you please share the container logs?
I'm guessing it has something to do with Cloudflare captcha protection. medium.com API, which libmedium uses, is behind Cloudflare captcha wall. Libmedium doesn't work when the captcha is tripped. There's an open issue here.
aside: I love your nick and domain :)
Executing
docker logs libmedium
produces the following output:Thank you! It looks like Cloudflare is being tripped. When you have the chance, can you please run this command on the machine running libmedium and share its output?
It's the HTTP request that libmedium makes to medium.com to fetch posts. If cloudflare is being tripped, then we should see the captcha page instead of a GrahpQL response.
Output:
Thanks again. Cloudflare is tripped as suspected. I don't think it can be bypassed. Were you able to run Scribe on this machine/IP?
Yes, it was working fine for a few weeks. Within the last week, it was unable to parse any Medium URLs, so I figured it was time to transition to LibMedium to see if the issue resolves itself.
This is probably the same reason why Scribe stopped working too. I had another person email me about the same. I'll try to look into it this weekend and update on here, if I find a fix :)
Additional information:
I barely used the Scribe instance, maybe only viewing one Medium article per week maximum.