I've just set up Tomcat 8 on an Ubuntu 14.04 VM and I'm not able to access the Manager App at http://[hostname]:8080/manager/html
from my browser. I get a "403 Access Denied" error as soon as I click on it. I am running Tomcat as a service defined in a config file in /etc/init.d/tomcat8-dev
. The error message indicates that Tomcat is set up to be accessible only from localhost initially, but as it is a hosted VM I'm not able to run a browser on it.
I have set up a user in the tomcat-users.xml
file as several people have recommended. However, I am not prompted to provide the credentials for that user, and I can't find any kind of login button on the default page. That file currently looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<tomcat-users xmlns="http://tomcat.apache.org/xml"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://tomcat.apache.org/xml tomcat-users.xsd"
version="1.0">
<role rolename="manager-script"/>
<role rolename="manager-jmx"/>
<role rolename="manager-gui"/>
<role rolename="manager-status"/>
<user username="(redacted)" password="(redacted)"
roles="manager-gui,manager-jmx,manager-status,manager-script"/>
</tomcat-users>
After reading the Tomcat documentation page here, I have also tried adding <Valve />
tags into context.xml
that look something like this:
<Context privileged="true" antiResourceLocking="false"
docBase="${catalina.home}/webapps/manager">
<Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127\.0\.0\.1" />
<!--Another valve for my local machine's IP-->
</Context>
However, as soon as I set privileged="true"
, I get a blank white page when I connect to the server with my browser regardless of the valves I provide afterwards.
I restart my service with sudo service tomcat8-dev restart
whenever I make changes.
Other things I have tried based on posts I read here and on other sites:
address="0.0.0.0"
to server.xml
inside the <Connector />
taginitctl
instead of setting up a service based on the instructions here, which doesn't load the default page on my server for some reasonNothing I've tried works. Please let me know if you would like more details about my situation. Any suggestions?
Edit: The problem was that I was editing the wrong context.xml
file. The correct file is in tomcat/webapps/manager/META-INF
. I had incorrectly been making changes to tomcat/conf/context.xml
.
Using the Web. Let's open http://localhost:8080/manager/html/ to view the Tomcat Manager App webpage. We need to authenticate as the tomcatgui user to do so.
The Tomcat Host Manager application is a part of Tomcat installation, by default available using the following context: /host-manager . You can use the host manager in the following ways: Utilizing the graphical user interface, accessible at: {server}:{port}/host-manager/html .
By default the Host Manager is only accessible from a browser running on the same machine as Tomcat. If you wish to modify this restriction, you'll need to edit the Host Manager's context. xml file.
AFAIK Tomcat blocks access to the Manager App (manager/html) for all hosts but localhost in its default configuration.
To be able to access the manager GUI with http://[hostname]:8080/manager/html, configure this in the configuration files server.xml and the context.xml of the manager application:
Step 1: In [tomcat-install-dir]/conf/server.xml edit the Connector element and add your IP as well as useIPVHosts="true", i.e.:
<Connector port="9009" protocol="AJP/1.3" redirectPort="9443"
address="192.168.0.9" useIPVHosts="true" />
address="0.0.0.0"
is probably not what you want to insert here, as it exposes the manager GUI to all machines on the network.
Step 2: In [tomcat-install-dir]/webapps/manager/META-INF/context.xml, edit the Valve element and add your IP:
<Context antiResourceLocking="false" privileged="true">
<Valve className="org.apache.catalina.valves.RemoteAddrValve"
allow="192\.168\.0\.9|127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1" />
</Context>
From Tomcat 8 context documentation
privileged : Set to true to allow this context to use container servlets, like the manager servlet.
antiResourceLocking : If true, Tomcat will prevent any file locking. This will significantly impact startup time of applications, but allows full webapp hot deploy and undeploy on platforms or configurations where file locking can occur
Note, that I don't add another Valve element as you mentioned in the list of things you tried but instead I edit the existing one and just add my IP (192.168.0.9).
Step 3: Restart Tomcat and you should be able to access the manager GUI with localhost / 127.0.0.1 as well as with your hostname / IP.
Regarding your tomcat-users.xml, the Tomcat Manager HOW-TO states:
It is recommended to never grant the manager-script or manager-jmx roles to users that have the manager-gui role.
So you might want to introduce two users in your tomcat-users.xml, i.e.:
<role rolename="manager-script"/>
<role rolename="manager-jmx"/>
<role rolename="manager-gui"/>
<role rolename="manager-status"/>
<user username="alice" password="whatever" roles="manager-script,manager-jmx"/>
<user username="bob" password="whatever" roles="manager-gui,manager-status"/>
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With