Legend
- localYour machine answered through portless (
pulse run is running it)
- betaAWS beta answered (hostname not registered locally, public DNS)
- tunnelThe beta task answered through the hybrid daemon's SSM tunnel on the alias port
- no tunnelPortless has the alias but nothing listens on the port: no tunnel yet and no local app
- mockThis very page answered: the hostname has no beta app behind it
- upSomething answered without CORS headers, so the page cannot tell local from beta
- downNo answer within 6 seconds: no DNS record, hung tunnel, portless down, or Chrome blocked local network access
How it decides
Frontends serve
/assets/version.txt: a dev server says
SNAPSHOT, a release names its version.
Backends serve
/info:
pulse run exports
INFO_ENVIRONMENT=local, so a local service answers
{"environment":"local"} and beta answers
{}.
Running a service from the IDE? Add that variable to the run configuration or it shows as beta / tunnel.
Troubleshooting
pulse portless doctor # proxy up, CA trusted
pulse portless list # local routes
lsof -nP -iTCP:8050 -sTCP:LISTEN
tail -f /tmp/com.agorapulse.cli/portforward.service.log
lsof on the port: java is a local service, session-manager-plugin the beta tunnel, nothing means no tunnel.
Everything local shows down? Chrome asks once for "local network access" on this site; check it under
chrome://settings/content/siteDetails?site=https%3A%2F%2Fdev.agorapulse.com
Stale results? Clear Chrome's DNS cache and socket pools:
chrome://net-internals/#dns
chrome://net-internals/#sockets
