Skip to main content
protocols.pageprotocols.page
8085

Port 8085 – InfluxDB HTTP

TCP

Port 8085 was the legacy InfluxDB HTTP API port in older versions. InfluxDB 1.x used port 8086 for HTTP writes/queries. Port 8085 was used for some clustering and relay configurations. Modern InfluxDB 2.x/3.x uses only port 8086. Check which version is running if you see port 8085 active.

Port Number

8085

Protocol

TCP

Service

InfluxDB HTTP API (Legacy)

Range

IANA Registered (1024–49151)

Description

Port 8085 appeared in InfluxDB relay configurations and some legacy InfluxDB Enterprise clustering setups. The relay component received writes on port 8085 and distributed them to multiple InfluxDB instances for replication. Modern InfluxDB (2.x and 3.x) consolidates all HTTP API traffic on port 8086. If you see port 8085 in use, it likely indicates either an outdated InfluxDB relay setup or another application. The Gogs Git service also defaults to port 8085 in some configurations.

Security risks

  • 1Legacy relay without auth: InfluxDB relay on port 8085 forwards writes without authentication – any client can inject arbitrary time-series data into your monitoring pipeline.
  • 2Orphaned service: legacy relay processes may continue running after migration to InfluxDB 2.x, creating an unmonitored attack surface with no security patches.
  • 3Gogs Git exposure: if Gogs uses 8085, exposed instances allow repository enumeration and potentially unauthenticated clone access to private repositories.

Firewall guidance

If running InfluxDB relay: migrate to InfluxDB 2.x or Telegraf with multiple outputs (eliminates relay). Block port 8085 from external access. If Gogs: bind to 127.0.0.1 and proxy via nginx with authentication.

Diagnosis commands

Identify what process is using port 8085

shell
ss -tnlp sport = :8085

Check if a health endpoint responds

shell
curl -s http://localhost:8085/health

Identify the service by response headers

shell
curl -s http://localhost:8085/

Usage examples

Port 8085 – InfluxDB HTTP
shell
curl http://localhost:8085/health
influx-relay --config relay.toml
nmap -sV -p 8085 target

Common services on this port

InfluxDB relay (deprecated)Gogs GitCustom HTTP services

Related ports

8086

InfluxDB HTTP API (current)

8088

InfluxDB backup/restore

3000

Gogs web UI (alternate)

History

InfluxDB relay was a community tool for replicating writes to multiple InfluxDB 1.x instances before InfluxDB Enterprise added native clustering. Port 8085 was the relay's default listener. The relay project was archived when InfluxDB 2.x introduced native replication. Gogs (a self-hosted Git service written in Go) also uses 8085 in some deployment guides.

FAQ

Should I still use InfluxDB relay?

No. The influxdb-relay project is archived and unmaintained. For InfluxDB 1.x: use Telegraf with multiple output plugins to write to multiple instances. For InfluxDB 2.x/3.x: use native replication or InfluxDB Cloud. For high availability: deploy InfluxDB Enterprise or migrate to VictoriaMetrics which has built-in clustering.