Weaviate 1.33-dev fails to start cloud meta store on single-node setup (fd12 DNS lookup error)

Support
1

Description

I am running Weaviate in binary on a single-node local server. Previously, I could start the server without issues, but recently I encountered the following fatal error when starting Weaviate:

{"action":"startup","build_git_commit":"","build_go_version":"go1.24.0","build_image_tag":"","build_wv_version":"1.33.0-dev","error":"start rpc service: server tcp net.listen: listen tcp: lookup fd12 on 77.88.8.8:53: no such host","level":"fatal","msg":"could not open cloud meta store","time":"2025-11-23T23:30:02+08:00"

Script I used:

#!/bin/bash

export LOG_LEVEL=info       

# vector / schema
export DEFAULT_VECTORIZER_MODULE=none
export AUTOSCHEMA_ENABLED=false

# persistence
export PERSISTENCE_DATA_PATH=./data
export DISABLE_TELEMETRY=true

# authentication / authorization
export AUTHENTICATION_ANONYMOUS_ACCESS_ENABLED=true
export AUTHORIZATION_ADMINLIST_ENABLED=false

./weaviate-server --host 0.0.0.0 --port 8080 --scheme http

Server Setup Information

  • Weaviate Server Version: 1.33.0-dev
  • Deployment Method: binary
  • Multi Node? Number of Running Nodes: Single Node

Any additional Information

  • Running on local Linux server (School server)
  • I suspect this might be related to a recent DNS/networking change, since this never happened before.
2

Hi @Jacky_Yee,

The error shows Weaviate can’t resolve your hostname fd12 via DNS, which is blocking as you suspect it is indeed DNS networking issue.

Since you’re on a school server, this is likely caused by a proxy intercepting Weaviate’s internal communication.

  1. Check if proxy is configured:

    env | grep -i proxy

Best regards,
Mohamed Shahin
Weaviate Support Engineer
(Ireland, UTC±00:00/+01:00)

3

Thanks for the pointer regarding the proxy.

I ran env | grep -i proxy and confirmed that no proxy is configured on my school server.

However, I investigated the DNS configuration (/etc/resolv.conf) and found that the school server is using public DNS resolvers.

nameserver 77.88.8.8
nameserver 114.114.115.115

The error lookup fd12 on 77.88.8.8:53: no such host persists even when I try to start a completely FRESH instance (using a brand new, empty PERSISTENCE_DATA_PATH).

This suggests that upon startup, Weaviate automatically detects the local IPv6 interface (starts with fd12...), and immediately tries to resolve its hostname via the public DNS. Since fd12 is a private ULA address, the public DNS fails to resolve it, causing Weaviate to crash with a fatal error immediately.

Do you have any insights or suggestions on how to resolve this problem?

4

Could you try to set the CLUSTER_ADVERTISE_ADDR environment variable to 127.0.0.1

Add this line before starting Weaviate:

export CLUSTER_ADVERTISE_ADDR=127.0.0.1

Best regards,
Mohamed Shahin
Weaviate Support Engineer
(Ireland, UTC±00:00/+01:00)

5

Thanks a lot! You really saved my day!

6

Awesome news @Jacky_Yee, thank you for confirming.

Have a lovely day!

Best regards,
Mohamed Shahin
Weaviate Support Engineer
(Ireland, UTC±00:00/+01:00)