Apache Tomcat 10 on Ubuntu 24.04 LTS — Support & Quick Start

At a glance

Application ports	80 (HTTP via the Apache reverse proxy), 443; 8080 (Tomcat direct) is NOT opened in the in-image firewall
Open in browser	http://<VM-IP>/
Service(s)	tomcat, apache2
Configuration	/opt/tomcat/conf/ (server.xml, tomcat-users.xml); deploy WARs to /opt/tomcat/webapps/; proxy vhost /etc/apache2/sites-available/tomcat-proxy.conf
Logs	/opt/tomcat/logs/catalina.out; /var/log/apache2/
Version	Apache Tomcat 10.1.55 on OpenJDK 17, fronted by Apache 2.4
Platform	Ubuntu 24.04 LTS

Quick start

1. Deploy from the Azure Marketplace (Get It Now → Create), choosing your SSH key at the Administration step.
2. Allow inbound SSH (22) for yourself plus the application port(s): 80 (HTTP) and 443 — restrict to your own IP where possible. The in-image firewall already allows them; only the Network Security Group (NSG) keeps them closed.
3. Browse to http://<VM-IP>/ — Apache proxies to Tomcat on 8080 and answers immediately.
4. Copy your WAR into /opt/tomcat/webapps/ (owned by the `tomcat` user); Tomcat auto-deploys it. Restart with `sudo systemctl restart tomcat`.

First login

1. No credential is generated: browse to http://<VM-IP>/ — Apache proxies to Tomcat and serves the placeholder ROOT app.
2. The examples, docs and host-manager webapps are removed; no Manager user is configured (add a role in /opt/tomcat/conf/tomcat-users.xml only if you need the Manager app, and restrict it).

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.