If your Java or Spring Boot app responds on localhost but not on the VPS public IP, check four separate layers in order: the effective application port, the socket’s bind address, the VPS firewall, and the cloud provider’s ingress firewall. A running JVM alone proves none of these. The most common cause is a listener bound to 127.0.0.1, which accepts loopback requests but cannot accept packets arriving through the VPS network interface.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Start locally, move to the VPS interface, then test from a genuinely external network. The first point at which the request fails identifies the fault domain. Spring Boot’s standalone HTTP port defaults to 8080, but server.port, environment variables, and command-line properties can change it.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What must be true before the public IP can work
Four conditions have to line up:
- The Java process must have started successfully and created an HTTP listener.
- The listener must use the port you are testing, not a different port or context path.
- The listener must bind to an interface reachable from the network. A listener on
127.0.0.1is local-only. - Both firewall layers must allow the connection: the operating-system firewall on the VPS and the provider’s network firewall or security group.
A reverse proxy adds another boundary. If Nginx, Apache, or a load balancer owns ports 80 or 443, the public endpoint is the proxy, while the Java process may remain on a private port such as 8080. In that design, testing the public IP with :8080 is usually testing the wrong endpoint.
1. Confirm the effective Spring Boot configuration
Do not assume that the value in a checked-in application.properties file is active. Spring Boot allows environment variables and command-line properties to override file settings, and deployment managers often inject those values at startup.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Read the startup log
Find the line that reports the embedded server starting and record the port. Also note whether the application uses TLS, a context path, or a non-root management port. A successful JVM startup without an HTTP-listener message can indicate that the application failed during web-server initialization or was launched as a non-web process.
Check the deployment environment
For a direct HTTP deployment, a typical configuration is:
server.address=0.0.0.0
server.port=80800.0.0.0 means the process listens on all IPv4 interfaces. Use it only when that exposure matches your design. If a reverse proxy is the only caller, bind the Java service to the private interface or loopback address used by that proxy and expose only the proxy publicly.
When a service is managed by systemd, inspect the unit and its environment rather than only the project directory. Look for an Environment= line, an EnvironmentFile=, or an ExecStart argument such as --server.port=9090. The value that matters is the one present in the running process’s startup command and environment.
Record the complete URL you intend to test
Write down the scheme, address, port, and path. For example, these are different requests:
http://203.0.113.10:8080/https://203.0.113.10/http://203.0.113.10/myapp/
A TLS listener will not respond correctly to plain HTTP, and an application deployed under a context path may return a 404 at / while working at /myapp/.
Recommended Free Tools
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
2. Prove that a listener exists
Run the socket check on the VPS itself. The Java PID and the listening address are more reliable than assumptions based on a process list.
sudo ss -lntpLook for the expected TCP port and identify the owning Java process. Typical results have very different meanings:
| Socket shown | What it means | Next check |
|---|---|---|
127.0.0.1:8080 |
The app accepts loopback traffic only. | Change server.address or test through the intended local proxy. |
0.0.0.0:8080 |
The app listens on every IPv4 interface. | Check host and provider firewalls, routing, and the tested URL. |
<private-interface>:8080 |
The app listens on one interface. | Ensure that interface is the one receiving traffic and that the proxy or client can route to it. |
| A different port | The JVM is healthy but the requested port is wrong. | Use the reported port or correct the effective configuration. |
| No matching listener | No HTTP socket exists on that port. | Inspect startup errors, service status, and command-line configuration. |
The process can be running while the listener is absent. Startup may have failed after the JVM launched, the application may have selected another port, or another service may have claimed the expected port.
3. Test from the VPS outward
Use a local request before changing firewall rules. Verbose curl output shows whether DNS, TCP, TLS, and HTTP each got as far as expected.
curl -v http://127.0.0.1:8080/
curl -v http://<vps-private-address>:8080/Interpret the local response
- HTTP 200, 3xx, 401, 403, or 404: a web server accepted the TCP connection and generated an HTTP response. A 404 proves that TCP reached the server; it points to the path, context path, or routing rather than a closed port.
- Connection refused: the target address answered but no process accepted that port, or a local rule actively rejected it. Confirm the socket listing and effective port.
- Timeout: packets are being dropped, routed incorrectly, or sent to an address that is not answering. Inspect the interface, route, and firewall instead of treating the timeout as proof of an application failure.
- TLS or protocol errors: the listener may require HTTPS, or plain HTTP is being sent to an HTTPS port. Match the scheme to the server configuration.
Next, use the VPS’s private address. If loopback succeeds but the private-address request fails, the bind address, local routing, or host firewall is the likely boundary. If both succeed, the Java listener is probably working and the investigation moves to ingress and external networking.
4. Fix a loopback-only bind
A listener on 127.0.0.1:8080 explains the classic symptom: curl http://127.0.0.1:8080 works, while the same port on the VPS address fails. Packets arriving on the public or private network interface are not delivered to a loopback-only socket.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Expose the app directly
Set the effective configuration to the intended address and port, then restart the service:
server.address=0.0.0.0
server.port=8080After restarting, run sudo ss -lntp again. Confirm that the new socket is present before testing externally. If IPv6 is part of the deployment, check for a corresponding IPv6 listener; an IPv4 bind does not automatically establish the IPv6 behavior you want.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep the app private behind a proxy
If Nginx, Apache, or a load balancer is the public edge, do not broaden the Java listener unnecessarily. Bind it to the interface or loopback address that the proxy uses, configure the proxy upstream to that exact address and port, and expose only the proxy’s public ports. This reduces the number of services reachable from the Internet and makes TLS termination and request filtering easier to control.
5. Open both firewall layers
Passing the socket and local curl tests does not guarantee Internet reachability. VPS environments commonly have an operating-system firewall plus a provider-level ingress policy.
Operating-system firewall
Inspect the active firewall and allow only the port required by the design. For a direct temporary test, that may be TCP 8080. For a reverse-proxy deployment, it is normally TCP 80 and 443, while the backend port remains restricted to the proxy or a private network.
sudo ufw status
sudo firewall-cmd --list-allThe commands above are examples for systems using UFW or firewalld; use the firewall manager actually enabled on your distribution. After changing a rule, repeat the VPS-interface curl and then test from outside.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Provider ingress or security-group firewall
The cloud provider’s network firewall can drop traffic before it reaches the VPS. Google Cloud’s guidance states that when a VM has a public IP, only intended services and traffic should be reachable, and that firewall rules can restrict selected ports and source IP ranges. Apply the same least-open principle to any provider:
- Allow TCP 80 and 443 from the Internet when a public reverse proxy is intended.
- Allow a backend port such as 8080 only from the proxy’s address range or a private network.
- For a short diagnostic, allow your own test IP rather than opening an administrative port globally.
- Verify that the public IP is actually attached to this VPS and that the rule targets the correct instance, network, tag, or security group.
Do not expose management or actuator endpoints broadly. A port being reachable is not the same as an endpoint being safe to publish.
6. Account for a reverse proxy or load balancer
A proxy changes the public endpoint. If it owns port 80 or 443, users should connect to http://<public-ip>/ or https://<hostname>/, not automatically to :8080.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Verify the proxy chain
- Confirm that the proxy service is running and listening on the expected public port.
- Check that its upstream points to the Java listener’s actual address and port.
- Ensure the VPS firewall permits proxy-to-backend traffic.
- Request the public endpoint and inspect the proxy’s access and error logs.
- Request the backend locally to separate Java errors from proxy routing errors.
If the proxy returns a 502 or 504, the public port is reachable but the proxy cannot complete the upstream connection. Recheck the backend bind address, port, service status, and any host firewall rule between proxy and application.
Handle forwarded host, port, and scheme
A proxy or load balancer can change the apparent host, port, and scheme seen by Spring Boot. Forwarded or X-Forwarded-* headers must be handled consistently so redirects and generated links use the public URL rather than an internal address or port. A redirect to http://127.0.0.1:8080 is a proxy/header configuration problem even though the initial request reached the application.
7. Test from a genuinely external network
Once loopback and the VPS interface work, test from a separate network, such as a mobile connection or an external monitoring probe. A request made from inside the same private network can be affected by NAT loopback or hairpin behavior and may not represent what an Internet client sees.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Use the literal public IPv4 address first
Test the public address before relying on DNS:
curl -v http://<vps-public-ip>:8080/
# If a reverse proxy owns port 80 or 443:
curl -v http://<vps-public-ip>/
curl -vk https://<vps-public-ip>/After the literal address works, test the hostname. If the hostname fails while the address succeeds, inspect the DNS record, stale addresses, proxy records, and IPv6 behavior. A DNS name can still point to an old VPS even when the current machine is configured correctly.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute8. Use the first failed layer to choose the fix
| Observed result | Most likely fault domain | Action |
|---|---|---|
| Localhost fails | Application process, startup, port, path, or TLS | Read startup logs, inspect the listener, and verify the scheme and context path. |
| Localhost works; VPS interface fails | Bind address, local routing, or host firewall | Inspect ss -lntp, set the intended bind address, and review local firewall rules. |
| VPS interface works; external access fails | Provider ingress, public-IP attachment, upstream routing, or external policy | Check cloud firewall rules, public-IP assignment, and the external test network. |
| TCP connects; HTTP response is wrong | Path, context path, proxy route, virtual host, TLS scheme, authentication, or application error | Use verbose curl and proxy/application logs; fix routing or URL details rather than opening more ports. |
| Public proxy returns 502 or 504 | Proxy-to-Java connection | Verify upstream address, backend port, service status, bind interface, and inter-service firewall rules. |
Direct port versus reverse proxy
Choose the public-facing design deliberately rather than exposing every port that happens to work during testing.
| Concern | Direct Java port | Reverse proxy in front |
|---|---|---|
| Public endpoint | The Java port, such as 8080 | Usually 80 and 443; Java stays on a backend port |
| Java bind requirement | Must bind to a reachable public or routed interface | Can bind privately to the proxy’s interface |
| TLS termination | Handled by the Java application or another edge service | Commonly handled at the proxy |
| Firewall surface | Open the application port to intended clients | Open 80/443 publicly and restrict the backend port |
| Forwarded headers | Usually no proxy translation | Must handle forwarded host, port, and scheme correctly |
| Best use | Temporary testing or a deliberately simple service | Public production service requiring TLS, filtering, or centralized routing |
A direct port can be useful for proving that the application works, but a reverse proxy generally gives you a smaller public surface and a single place to enforce TLS and request policy.
Common failure scenarios and repairs
“The JVM is running, so port 8080 must be open”
A process list only proves that a Java process exists. Check the listening socket and correlate it with the Java PID. The app may have selected another port, failed before web-server startup, or be listening only on loopback.
“I changed application.properties, but nothing changed”
An environment variable or command-line option can override the file. Inspect the service unit and startup command, restart the service, and verify the resulting socket rather than trusting the edited file.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems“The public request times out, so the app is broken”
First run the loopback and VPS-interface requests. If they return HTTP responses, the app is serving traffic and the timeout is farther out: host firewall, provider ingress, routing, or the wrong public IP.
“I opened 8080, but users still cannot connect”
Confirm whether the design actually uses a proxy on 80/443, whether the provider firewall also allows 8080, and whether the public IP belongs to this VPS. Opening a port in only one firewall layer is insufficient.
“The request reaches the server but redirects to an internal URL”
Fix proxy forwarding and Spring Boot forwarded-header handling. The initial network path is working; the generated redirect is exposing an internal host, port, or scheme.
Security checks before declaring the fix complete
- Expose only the public ports required by the chosen architecture.
- Restrict backend and administrative ports to trusted source ranges or private interfaces.
- Use HTTPS at the public edge when credentials, sessions, or personal data are involved.
- Keep actuator and management endpoints off the public interface unless they are explicitly protected.
- Remove temporary broad firewall rules created during testing.
- Retest after a service restart so the result reflects the persistent configuration, not a one-off manual launch.
Final diagnostic checklist
- Read the startup log and record the effective port, context path, TLS mode, and bind address.
- Run
sudo ss -lntpand match the listener to the Java PID. - Request
127.0.0.1with verbose curl. - Request the VPS private address with the same port.
- If loopback-only binding is not intentional, configure
server.addressfor the required interface and restart. - Check the VPS operating-system firewall.
- Check the provider ingress or security-group rule and the public-IP attachment.
- If a proxy is present, test its public port and verify its upstream separately.
- Test the literal public IPv4 address from an external network, then test DNS.
- Use the first failed layer—not the last visible error—to select the repair.
The durable fix is not simply “open port 8080.” It is a matched configuration in which the application listens on the intended interface and port, the public endpoint is the one users actually call, and both firewall layers permit only that designed path.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
