Accessing Server Page on Typesense Docker Image
TLDR gab inquired about accessing the server page of a Typesense Docker image. Kishore Nallan clarified that Typesense does not have server admin pages and APIs are exposed on port 8108.
Jul 27, 2021 (28 months ago)
gab
09:05 AMI'm trying to use a docker image for Typesense. Even if it runs well, I cannot find how to access the server page.
I20210726 14:26:01.141592 1 typesense_server_utils.cpp:306] Starting Typesense 0.21.0
I20210726 14:26:01.141644 1 typesense_server_utils.cpp:309] Typesense is using jemalloc.
I20210726 14:26:01.141834 1 typesense_server_utils.cpp:358] Thread pool size: 96
I20210726 14:26:01.157956 1 store.h:61] Initializing DB by opening state dir: /data/db
I20210726 14:26:01.169329 1 store.h:61] Initializing DB by opening state dir: /data/meta
I20210726 14:26:01.174690 1 typesense_server_utils.cpp:422] Starting API service...
I20210726 14:26:01.174698 256 typesense_server_utils.cpp:209] Since no --nodes argument is provided, starting a single node Typesense cluster.
I20210726 14:26:01.174878 1 http_server.cpp:172] Typesense has started listening on port 8108
I20210726 14:26:01.191908 256 server.cpp:1045] Server[braft::RaftStatImpl+braft::FileServiceImpl+braft::RaftServiceImpl+braft::CliServiceImpl] is serving on port=8107.
I20210726 14:26:01.191936 256 server.cpp:1048] Check out in web browser I tried this one
<http://5df18691f6a5:8107>Thanks for help :)
Kishore Nallan
09:06 AMKishore Nallan
09:08 AMCheck out in web browser is the Raft diagnostic page. It's used for troubleshooting the clustering. It does not have any information about Typesense collections or data etc.
gab
09:09 AMKishore Nallan
09:09 AMgab
09:18 AM8108it will expose all api's there <http://localhost:8108> ?Kishore Nallan
09:18 AMgab
09:26 AM
Typesense
Indexed 2776 threads (79% resolved)
Similar Threads
Typesense Issues in Kubernetes Environment
siva.sunkara experienced Typesense issues in Kubernetes and shared logs. Kishore Nallan recommended stand-alone nodes and shared a Github issue thread. Sergio suggested fine-tuning Kubernetes deployment and linked to a working setup.
Typesense Node Stuck in Segfault Loop After Stress Test
Adrian encountered a segfault loop when stress testing a Typesense cluster. Kishore Nallan recommended trying a newer RC build and suggested potential issues with hostname resolution.
"Resolving Startup Issue with Typesense Single Replica Set in Local `K8s` Setup"
Vishal encountered issues starting a Typesense single replica set due to directory permission issues. Kishore Nallan suggested checking if the volume was accessible for writes. Vishal resolved the problem by adjusting permissions on the host.
Resolving Server Stoppage Issues in Typesense Multi VM Cluster
gaurav faced issues with the Typesense server in a multi VM cluster, including automatic stoppage and errors. Kishore Nallan identified the lack of a quorum and suggested using three nodes. When the issue persisted, they advised running Typesense via `nohup` or `systemd` to prevent session closure from stopping the process.
Connection Refused Issue with Typesense and Nginx Reverse Proxy
Karthik experiences a connection refused problem with Typesense and Nginx reverse proxy. Jason helps troubleshoot, but the issue remains unresolved.