401 Client Error: for url: http://localhost:8080/text/serverinfo

I have been fighting with tomcat manager for the past month Installed version of tomcat-manager 3.0.0 (works with Tomcat >= 7.0 and <= 10.0)

Installed version of tomcat;

Server version: Apache Tomcat/9.0.52
Server built:   Jul 31 2021 04:12:17 UTC
Server number:  9.0.52.0
OS Name:        Linux
OS Version:     4.14.243-185.433.amzn2.aarch64
Architecture:   aarch64
JVM Version:    1.8.0_302-b08
JVM Vendor:     Red Hat, Inc.

result of cat /etc/os-release

NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"

Whenever I run any example mentioned in this page (https://tomcatmanager.readthedocs.io/en/stable/package.html), I get “connected” and a regular output, so I am sure it is working this way and the credentials are correct. here is a sample output:

connected
/ ApplicationState.RUNNING
/host-manager ApplicationState.RUNNING
/sales ApplicationState.RUNNING
/manager ApplicationState.RUNNING

However, when I try to run it from command line, it returns the error requests.exceptions.HTTPError: 401 Client Error: for url: http://localhost:8080/manager/text/serverinfo at the first attempt. The following line proves that tomcat is running at the time of the execution

sudo netstat -lnp | grep 8080
tcp6       0      0 :::8080                 :::*                    LISTEN      2438/java

[kotfu]

I’ll have a new release pushed to PYPI today (or maybe tomorrow) which should make it easier for you.

The reason the $ is causing problems is because the operating system shell uses that as an indicator for a variable. The shell is looking for a variable called EFGH, which doesn’t exist, so it uses an empty string instead.

You can tell the shell to not do so by enclosing the password in single quotes, like this:

$ tomcat-manager --user=USER --password='ABCD$EFGH' http://localhost:8080/manager

[kotfu]

I have been able to reproduce this error (linux client, linux server, tomcat 9.0.8). I’ll investigate and get it resolved.