How to access dashboard from other computer ?

[SwHaraday]

Hi there,

Qdrant is running on Windows11 as local server without docker on say 'SERVER COMPUTER'.
'qdrant.exe' was downloaded from 'https://github.com/qdrant/qdrant/releases/download/v1.15.1/qdrant-x86_64-pc-windows-msvc.zip'.
Other related files were downloaded from 'https://github.com/qdrant/qdrant/archive/refs/heads/master.zip'.
And WEB-UI files were installed accoding to '#6944'.
Setup has been done via 'Remote Desktop' without any problem.

Everything works fine as long as playing within the SERVER COMPUTER.
However if trying to access Qdrant with 'http://IP_OF_SERVER_COMPUTER:6333/dashboard' from other computer on same network, the SERVER COMPUTER denies access and never shows 'dashboard'.

Please kindly let me know how to configure to enable access from other computers.
Thank you in advance.

[SwHaraday]

Hi! anybody here ???

[generall]

this is like your network/ firewall problem, not related to qdrant

[timvisee]

That is most likely, yes.

Other than that it is possible to configure the wrong host in Qdrant.

Did you change this value in the configuration by any chance?

qdrant/config/config.yaml

Lines 242 to 243 in 5c0863a

	# Host to bind the service on
	host: 0.0.0.0

[SwHaraday]

Dear generall, timvisee,
Thank you for your reply. I'm glad someone was there.

It was my mistake to edit development.yaml in config folder. I've learned that development.yaml and production.yaml override config.yaml, if exist.
And problem was solved last evening.

I don't blame you but I think the root of this maze is that the assets for displaying the dashboard are not included in the zip file.
Various web-pages and tutorials state that once launched, you can access it at 'http://127.0.0.1:6333/dashboard'. So most people would not imagine that you would need to download the display assets separately.

Thank you anyway! BR yuji

[timvisee]

Happy to see you resolved the issue!

We do ship the web UI files in our Docker containers by default. It's our recommended way to run Qdrant.

I actually like that we also ship clean binaries without anything attached. If we'd include the web UI there it means we need to ship multiple files, instead of a single binary.