Closed mikwee closed 1 year ago
Hello, I just stumbled upon this same issue. I noticed the api calls depend on the SITE_URI
environment variable being set to your domain correctly. For local development, the steps below should allow you to access the posts
mv .env.example .env
Then, set SITE_URI
var.
SITE_URI=http://localhost:3000
I know it's not a good final solution, but gets the job done
Thank you for the help @LemosLucas 🙏 Greatly appreciated!
@mikwee SITE_URI
as shared by Lucas is the right way to get rid of the error. The post detail pages use the value to form the endpoint that needs to be hit to increment the read count. The SITE_URI
needs to be changed to the actual URL when your site is up/deployed through environment settings.
This is documented under "View counter feat. Redis/Upstash Redis" in the README. Let me know if this could've been easier with some improvement in the README.
@mikwee Marking this as closed, as what I shared above is the recommended solution.
When trying to read one of my posts in dev mode, I get this error:
Why could this be happening? Feel free to ask for info. Thanks.