Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Default node name has changed between CouchDB 3.3.2 and 3.42

Open
  • Is something wrong?
#5,456 12 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
erlang
Domain
backend, databases

Research direction

Start by comparing etc/vm.args and local.ini between fresh and upgraded CouchDB 3.3.2 and 3.4.2 installations on Windows 10. Read the 3.4 upgrade notes and the linked 2.1 upgrade notes, then trace how the node name relates to Fauxton database loading and authentication. Done means the version change and its upgrade impact are explained and the relevant documentation is updated.

Written by the indexing model from the issue text.

Description

bug needs-triage

I have recently attempted to upgrade an existing 3.3.2 installation to 3.4.2 on Windows 10.

The upgrade appeared successful, but Fauxton showed "database failed to load" for all my databases.

Upon inspecting etc/vm.args and comparing with another PC running 3.3.2, I noticed that 3.4.2 had changed the node name to

-name [email protected]

I changed it to couchdb@localhost and then could no longer log in to Fauxton (incorrect credentials, although I was definitely using the same username and password!).

Reinstalling 3.4.2 and setting my original admin user and password did not help as part of the installer did not help. Editing local.ini to set my admin password did not work either:

[admins]
admin = <my password>

I'm now in the process of rolling back to 3.3.2 and reinstating my databases, but I can confirm that a completely fresh install of 3.4.2 has -name [email protected] while a completely fresh install of 3.3.2 -name couchdb@localhost.

Having had no problems upgrading from 3.2.2 in the past, and also checking an older machine with 3.2.2 on it having localhost as the node name, I would suspect it has been localhost for some time on 3.x

I noted that the following wiki page indicated the change from localhost to 127.0.0.1 for 2.x to 2.1.1 but:

a) this is not mentioned when upgrading to 3.4.x
https://docs.couchdb.org/en/stable/whatsnew/3.4.html

b) why did it go from 127.0.0.1 in 2.1.1 back to localhost in 3.2.x/3.3.x and now back to 127.0.0.1 again in 3.4.x?

https://docs.couchdb.org/en/latest/whatsnew/2.1.html#upgrade-notes

Dominant language
Erlang
Stars
7k
Forks
1.1k
Avg merge
1d 23m
Merged PRs (30d)
30

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/couchdb

All issues in apache/couchdb

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.