Troubleshooting Self-Hosted TS Errors
TLDR A raised issues with self-hosted TS and got an empty server reply. Kishore Nallan suggested checking the configuration of SSL certs.
Powered by Struct AI
2
21mo
Mar 27, 2022 (21 months ago)
A
A
04:42 PMBeen running into some strange issues with TS self hosted and can’t find documentation for it:
• response_code=0 return_code=bad_content_encoding total_time=0.561199
•
• curl: (52) Empty reply from server
can’t send data from production server into self hosted TS, and trying to do a health check from local machine always returns in empty reply from server.
• response_code=0 return_code=bad_content_encoding total_time=0.561199
•
$ curl <http://xxx.yyy.com:443/health|xxx.yyy.com:443/health> • curl: (52) Empty reply from server
can’t send data from production server into self hosted TS, and trying to do a health check from local machine always returns in empty reply from server.
Mar 28, 2022 (21 months ago)
Kishore Nallan
Kishore Nallan
01:48 AMCheck that you have configured SSL certs properly. If you are using letscrypt you have to use the fully chained certificate.
Typesense
Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting SSL Error in Laravel Scout with Typesense on Ubuntu
Matthew faced an SSL issue with their server setup. Jason & Kishore Nallan suggested using self-signed certificates or running without HTTPS.
8
23mo
Troubleshooting CORS Issues in Self-Hosted Typesense
Ankit faced CORS issues with self-hosted Typesense. Jason suggested correct configuration but the problem was mixed content (HTTP vs HTTPS).
6
6mo
Resolve Connection Error on Records Upsert
Jainil faced consistent connection errors while upserting records. Jason identified an OOM issue, suggesting a capacity upgrade. Auto-scaling was discussed and the upgrade implementation process, which was in progress, was clarified.
11
3mo