416 error in LinkedIn Post Inspector
Hello,
When my site (https://scribr.me) which is hosted on your servers, is reviewed by the LinkedIn Post Inspector (https://www.linkedin.com/post-inspector/) it returns a 416 Http response. I believe this may be due to how you have setup your servers to handle range requests.
Is there anything you can do to look into this? Or advise me how I should best manage this if this is completely out of your control?
Scribr
Scribr - Your all-in-one tool for AI-powered transcription and tran...
Scribr supports real-time, high-accuracy transcriptions and translations in over 50 languages. Ideal for meetings, interviews, podcasts, language studies, and more.
Post Inspector
Get insights into how your content shows up on LinkedIn with Post Inspector.
Solution:Jump to solution
Hello,
When my site (https://scribr.me) which is hosted on your servers, is reviewed by the LinkedIn Post Inspector (https://www.linkedin.com/post-inspector/) it returns a 416 Http response. I believe this may be due to how you have setup your servers to handle range requests.
Is there anything you can do to look into this? Or advise me how I should best manage this if this is completely out of your control?...
Scribr
Scribr - Your all-in-one tool for AI-powered transcription and tran...
Scribr supports real-time, high-accuracy transcriptions and translations in over 50 languages. Ideal for meetings, interviews, podcasts, language studies, and more.
Post Inspector
Get insights into how your content shows up on LinkedIn with Post Inspector.
25 Replies
Project ID:
7160cca6-80d3-4d76-a0c9-ebc86b66dd4e7160cca6-80d3-4d76-a0c9-ebc86b66dd4e
at first glance this seems like a code issue
or even a misconfiguration with your custom domain
The react frontend is hosted on railway with the domain provided by namecheap. If it were a code issue, where would you customise how range requests are handled in the react front end?
If it's a misconfiguration with the namecheap domain hosting, what should be changed to fix this?
what's your start script for your react app
"build": "tsc && vite build --mode=production"what is your start script
Actually, sorry it runs this one
"start": "vite preview --host"there we go, the true issue
please follow this guide, expect
serve build ... will become serve dist ...
https://help.railway.app/project-help/f9v3gkPQRy4UShk5SnoPDH/getting-your-create-react-app-running-on-railway/qHRsgxa5n57xLp1yVgk9fPNot sure if you've correctly identified the issue. The application runs perfectly on railway. There's no issues there. The real issue is how range requests are being handled by the server which results in the 416 error code:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/416
416 Range Not Satisfiable - HTTP | MDN
The HyperText Transfer Protocol (HTTP) 416 Range Not Satisfiable error response code indicates that a server cannot serve the requested ranges. The most likely reason is that the document doesn't contain such ranges, or that the Range header value, though syntactically correct, doesn't make sense.
please follow the guide
how did it go?
Still working through the deployment. Now getting 404 errors which I'm working through
what's your current start command
serve build -s -n -L -p $PORTplease review what I have said in this message
OK. That's not in the guide you sent me. I'll try changing the start command to
serve dist -s -n -L -p $PORTyes I know, there is a issue with the guide where the note about vite is hidden, that is why I made that remark in the message before sending the link
Thank you @Brody, now is working as intended:
see, not issue with railway 🙂
you just gotta trust the process
I trusted! Tried back and forth with [email protected] for a week and they couldn't help me. @Brody is the MVP
ha they should have sent you to the discord
They did after 9 days!
9 days, ouch
and what? 30 minutes after opening a thread to solved lol
Haha yeah. 9 days isn't so bad. At least it's sorted now! Thanks again!
no problem!