Getting Data In

Cannot Login to Forwarder

pchukwuma
New Member

After installing the Forwarder, I cannot login to it. I have executed SPLUNK CLEAN ALL, but cannot login. I also tried placing the user-seed.conf in the etc/system/local directory, but I still cannot login. What am I missing?

Tags (2)
0 Karma

Paolo_Prigione
Builder

Was the admin's default password of "changeme" ever changed? If you can not figure out the password, then

  1. stop the UF
  2. rename the $SPLUNK_HOME/etc/passwd file

Now you have the default credentials (admin/changeme) back.

However, if you want to achieve similar results to clean all, then:

  1. stop the UF
  2. rename $SPLUNK_HOME/var to something else
  3. rename $SPLUNK_HOME/etc/users to something else
  4. start the UF
  5. if everything works fine, drop the renamed folders.

Ayn
Legend

How are you trying to login? What credentials are you using?

0 Karma

DaveSavage
Builder

When you say 'log in' you are trying to connect to it through the GUI? It doesn't support that. You can access it via the CLI and there is a rich thread on the commands at http://docs.splunk.com/Documentation/Splunk/latest/Admin/CLIadmincommands (thanks Drainy 😉

0 Karma

pchukwuma
New Member

I am trying to login through the CLI. The Splunk Clean All is a CLI command.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...