You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to deploy Qdrant on Railway with a server connecting to the Qdrant instance through private network. Railway calls the ipv6 address, but it seems like Qdrant doesn't accept ipv6 http connection on its Docker. Railway is just a specific example to replicate this issue, but I believe it's true regardless.
Current Behavior
Connection refused.
Steps to Reproduce
Start a Qdrant template on Railway.
Start a basic server image.
Have the server image try to connect to the instance through the private address.
There just is a connection refused issue.
Expected Behavior
The Qdrant server should accept connections from ipv6.
Possible Solution
The equivalent of the following:
const port = process.env.PORT || 3000;
app.listen(port, '::', () => {
console.log(`Server listening on [::]${port}`);
});
Context (Environment)
Detailed Description
Possible Implementation
The text was updated successfully, but these errors were encountered:
Update: the simplest solution is to set the env variable QDRANT__SERVICE__HOST to :: -- I was able to get this to work on Railway and connect to qdrant over the internal network.
Trying to deploy Qdrant on Railway with a server connecting to the Qdrant instance through private network. Railway calls the ipv6 address, but it seems like Qdrant doesn't accept ipv6 http connection on its Docker. Railway is just a specific example to replicate this issue, but I believe it's true regardless.
Current Behavior
Connection refused.
Steps to Reproduce
There just is a connection refused issue.
Expected Behavior
The Qdrant server should accept connections from ipv6.
Possible Solution
The equivalent of the following:
Context (Environment)
Detailed Description
Possible Implementation
The text was updated successfully, but these errors were encountered: