Find the correct URL
curl -I http://127.0.0.1:8080/geoserver/
# If nothing responds, identify the 8080 listener
# Windows PowerShell
Get-NetTCPConnection -LocalPort 8080 -State Listen
# macOS or Linux
lsof -nP -iTCP:8080 -sTCP:LISTEN| Result | Interpretation |
|---|---|
Tomcat page at /, 404 at /geoserver | The container is running, but GeoServer is not deployed under that context or failed during deployment. |
GeoServer page at /geoserver | Network, servlet container, and context path are working. |
| Connection refused everywhere | No process is accepting connections at 8080. |
| Another product’s page | A different process owns the port. |
Change the initial admin password
GeoServer’s official quickstart documents initial admin / geoserver credentials for a new data directory and instructs administrators to change them. Treat those values only as bootstrap credentials for a fresh instance—not a universal recovery password.
- Sign in to the local web administration interface.
- Open Security → Users, Groups, and Roles.
- Select the
adminuser, set a unique password, and save. - Also review Security → Passwords and the keystore-password warning.
Never leave initial credentials on a shared or remotely reachable instance. Restrict network access until the user and keystore passwords are changed.
Recover access without deleting security configuration
Current GeoServer documentation provides recovery options under Security → Passwords for the keystore password. If you still have another administrator account, use the supported user-management interface or authenticated REST endpoints to repair the affected account.
If all administrative access is lost:
- Stop GeoServer and take a complete, restorable backup of the data directory.
- Confirm the exact GeoServer version and active user/group service.
- Follow the recovery procedure for that version and service, or restore a known-good data-directory backup.
- Test recovery on a copy before touching the only working data directory.
Do not delete the security directory. It contains users, roles, services, keys, and other security state. Recreating it can remove access controls and is not a safe password-reset shortcut.
Locate the active data directory
The location depends on how GeoServer was installed and can be overridden. Use the server status page or startup log rather than guessing a home-directory path. In the default XML-backed user/group service, current GeoServer documentation places the user database at:
<data-directory>/security/usergroup/<service-name>/users.xmlOlder articles that instruct you to edit users.properties may describe a different or obsolete security setup. Confirm your active version and service before editing files, and do not replace encrypted values with plain text.
Official references
- GeoServer: Preflight checklistInitial credentials, password changes, keystore recovery, and local example URL.
- GeoServer: PasswordsPassword policies, keystore password, and temporary root-access guidance.
- GeoServer: User/group servicesCurrent XML user-store path and supported service types.
- GeoServer: Web administration quickstartLogin interface and security configuration.