https://community.splunk.com/t5/Getting-Data-In/After-installing-and-configuring-a-universal-forwarder-on-a/m-p/167821#M33978 <P>My <STRONG>own</STRONG> answer, I fixed it<BR /> Needed to modify server.conf on the Universal forwarder to include<BR /> [general]<BR /> allowRemoteLogin =requireSetPassword<BR /> and need to change the password from the default <BR /> ./splunk edit user admin -password "new admin password" -role admin -auth admin:change me</P> <P>Definitely a documentation issue for sure. Lack thereof.</P> Tue, 03 Mar 2015 22:58:56 GMT dougcabell 2015-03-03T22:58:56Z https://community.splunk.com/t5/Getting-Data-In/After-installing-and-configuring-a-universal-forwarder-on-a/m-p/167820#M33977 <P>On the remote end I see this after installing/configuring Universal Forwarder:</P> <PRE><CODE>./splunk list forward-server Splunk username: admin Password: Active forwards: 10.40.10.69:9997 Configured but inactive forwards: None </CODE></PRE> <P>If I run setup.sh on the Splunk Server I see an option 5 per below:</P> <PRE><CODE> Please choose from one of the following options: 1 - show *nix input status 2 - manage *nix inputs 3 - install/upgrade app 4 - change credentials 5 - connect to remote instance 0 - logout and exit program </CODE></PRE> <HR /> <P>I select option 5 and try <A href="http://nvp02:8089">http://nvp02:8089</A> and I try 10.30.11.25:8089 and neither will let me login<BR /> If I try <A href="https://nvp02:8089">https://nvp02:8089</A> and I try <A href="https://10.30.11.25:8089">https://10.30.11.25:8089</A> I still cannot login<BR /> NO LOGINS WORK<BR /> If I run setup.sh on the remote server when it asks for the initial login before the menu, I can login with the default spunk uname/pwd<BR /> Yes, I can ssh and sftp from the server to the remote linux host.</P> <P>Why does this not work for me?</P> <P>Help please</P> <P>Thank You</P> Tue, 03 Mar 2015 20:08:01 GMT https://community.splunk.com/t5/Getting-Data-In/After-installing-and-configuring-a-universal-forwarder-on-a/m-p/167820#M33977 dougcabell 2015-03-03T20:08:01Z https://community.splunk.com/t5/Getting-Data-In/After-installing-and-configuring-a-universal-forwarder-on-a/m-p/167821#M33978 <P>My <STRONG>own</STRONG> answer, I fixed it<BR /> Needed to modify server.conf on the Universal forwarder to include<BR /> [general]<BR /> allowRemoteLogin =requireSetPassword<BR /> and need to change the password from the default <BR /> ./splunk edit user admin -password "new admin password" -role admin -auth admin:change me</P> <P>Definitely a documentation issue for sure. Lack thereof.</P> Tue, 03 Mar 2015 22:58:56 GMT https://community.splunk.com/t5/Getting-Data-In/After-installing-and-configuring-a-universal-forwarder-on-a/m-p/167821#M33978 dougcabell 2015-03-03T22:58:56Z https://community.splunk.com/t5/Getting-Data-In/After-installing-and-configuring-a-universal-forwarder-on-a/m-p/167822#M33979 <P>Just for reference, this is documented on this page:<BR /> <A href="http://docs.splunk.com/Documentation/Splunk/6.2.2/Admin/AccessandusetheCLIonaremoteserver">http://docs.splunk.com/Documentation/Splunk/6.2.2/Admin/AccessandusetheCLIonaremoteserver</A></P> Wed, 04 Mar 2015 21:19:37 GMT https://community.splunk.com/t5/Getting-Data-In/After-installing-and-configuring-a-universal-forwarder-on-a/m-p/167822#M33979 ppablo 2015-03-04T21:19:37Z