Support Questions
Find answers, ask questions, and share your expertise

Ambari UI - Unable to login

New Contributor

Hi All,

I have setup a HDP cluster (4 nodes) using Ambari.

Everything used to work fine. But, just yesterday, all of a sudden I am not able to login to Ambari UI.

It displays below error after trying for few seconds:

"Unable to connect to Ambari Server. Confirm Ambari Server is running and you can reach Ambari Server from this machine."

I did not find any errors in ambari-server.log, ambari-server.out or ambari-alerts.log

I checked using ambari-server status that ambari is running as shown below

[root@sbxkfk001 ambari-server]# ambari-server status

Using python /usr/bin/python

Ambari-server status

Ambari Server running

Found Ambari Server PID: 28736 at: /var/run/ambari-server/

Also, netstat tells me amabri is running on port 8080

[root@sbxkfk001 ambari-server]# netstat -an | grep 8080

tcp6 0 0 :::8080 :::* LISTEN

I tried by restarting the machine, restarting ambari but with no luck.

Also, I reset admin password to admin in postgress but with no luck.

Could you please tell me how can we debug this?

Ambari version: HDP-2.4




@Shiva Moorthy

Could you please try restarting the metadata database [postgres?] and ambari-server?

New Contributor


I did restart Ambari multiple times but no luck .. since I had restarted the machine itself, postgress restart should have been don


@Shiva Moorthy

What is the ambari version? (ambari-server --version)

Do you see any error on the browser console log on the UI? (or on the network tab)

Do you use LDAP for auth or its just a simple setup? /etc/ambari-server/conf/ content can be useful too (if no confidential content there for you of course).

New Contributor

Hi Oszabo,

Below is the error shown in console log:

Failed to load resource: the server responded with a status of 403 (Full authentication is required to access this resource)

I do not use LDAP.

Below is content:

jdk1.7.dest-file=jdk-7u67-linux-x64.tar.gz kerberos.keytab.cache.dir=/var/lib/ambari-server/data/cache agent.package.install.task.timeout=1800 server.connection.max.idle.millis=900000 bootstrap.script=/usr/lib/python2.6/site-packages/ambari_server/ server.version.file=/var/lib/ambari-server/resources/version recovery.type=AUTO_START api.authenticate=true http.strict-transport-security=max-age=31536000 server.persistence.type=local jdk1.8.jcpol-url= jdk1.8.dest-file=jdk-8u60-linux-x64.tar.gz rolling.upgrade.skip.packages.prefixes= http.x-frame-options=DENY webapp.dir=/usr/lib/ambari-server/web agent.threadpool.size.max=25 recovery.lifetime_max_count=1024*)/jre ambari.python.wrap=ambari-python-wrap ambari-server.user=ambari agent.task.timeout=900 jdk1.7.url= server.os_family=redhat7 java.home=/usr/jdk64/jdk1.8.0_60 server.jdbc.postgres.schema=ambari user.inactivity.timeout.default=0 java.releases=jdk1.8,jdk1.7 skip.service.checks=false shared.resources.dir=/usr/lib/ambari-server/lib/ambari_commons/resources recommendations.dir=/var/run/ambari-server/stack-recommendations rolling.upgrade.min.stack=HDP-2.2 jdk1.8.desc=Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8 server.os_type=centos7 views.http.strict-transport-security=max-age=31536000 views.request.connect.timeout.millis=5000 resources.dir=/var/lib/ambari-server/resources custom.action.definitions=/var/lib/ambari-server/resources/custom_action_definitions views.http.x-frame-options=SAMEORIGIN recovery.enabled_components=METRICS_COLLECTOR*)/jre server.execution.scheduler.maxDbConnections=5 jdk1.7.desc=Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7 bootstrap.setup_agent.script=/usr/lib/python2.6/site-packages/ambari_server/ rolling.upgrade.max.stack= server.http.session.inactive_timeout=1800 server.execution.scheduler.misfire.toleration.minutes=480 security.server.keys_dir=/var/lib/ambari-server/keys stackadvisor.script=/var/lib/ambari-server/resources/scripts/ server.tmp.dir=/var/lib/ambari-server/data/tmp server.execution.scheduler.maxThreads=5 metadata.path=/var/lib/ambari-server/resources/stacks server.fqdn.service.url= views.http.x-xss-protection=1; mode=block bootstrap.dir=/var/run/ambari-server/bootstrap jdk1.7.home=/usr/jdk64/ jdk1.8.url= jdk1.8.home=/usr/jdk64/ user.inactivity.timeout.role.readonly.default=0 http.x-xss-protection=1; mode=block client.threadpool.size.max=25 jdk1.7.jcpol-url= server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat server.execution.scheduler.isClustered=false server.stages.parallel=true server.jdbc.database=postgres server.jdbc.database_name=ambari

@Shiva Moorthy make sure you aren't using DHCP. If the Ambari node was restarted you might have picked up a new ip address which doesn't match the DNS mappings in your hosts file.

New Contributor

Hi Scott,

I confirmed that it is using the same IP by ifconfig and DNS mappings are fine.

Expert Contributor

@Shiva Moorthy

Please make sure that firewall is still disabled. Restarting server usually enables firewall.

New Contributor

Hi Manish,

Firewall is down. Please check below:

[root@sbxkfk001 hos]# systemctl status firewalld

● firewalld.service

Loaded: not-found (Reason: No such file or directory)

Active: inactive (dead)

hi @psbhat_badaja @manish1 

Were you able to resolve this?

I am facing exactly the same issue.