First Login
RSSMonster is multi-user by default. It does not ship with a shared default username or password: each user first creates an account and then signs in with their own credentials.

Create Your Account
After starting RSSMonster, open its address in a browser. The default Docker installation is available at http://localhost:3000.
- Select Create an account on the sign-in page.
- Enter a username and password, then repeat the password.
- Select Register.
- Return to the sign-in form and enter the credentials you just created.
The first account registered in a new RSSMonster database receives the admin role. Later registrations create regular user accounts. Each person should register and use their own credentials so that subscriptions, articles, reading state, preferences, and other user data remain scoped correctly.
Keep your credentials somewhere safe. RSSMonster has no default account to fall back to.
Optional Development Login
RSSMonster can automatically establish a session for one existing user. This can be convenient during debugging or for a personal installation on a trusted network where repeatedly entering credentials is undesirable.
Add the following to server/.env:
NODE_ENV=development
ENABLE_DEVELOPMENT_LOGIN=true
DEVELOPMENT_LOGIN_USER_ID=1
server/.env applies to a manual installation. Docker Compose does not pass arbitrary values from the root .env into the container. For Docker, change the rssmonster service’s existing NODE_ENV value to development and add the other two variables under environment:
services:
rssmonster:
environment:
NODE_ENV: development
ENABLE_DEVELOPMENT_LOGIN: "true"
DEVELOPMENT_LOGIN_USER_ID: "1"
All three settings are required:
NODE_ENV=developmentgates the development-login endpoint. It does not operate whenNODE_ENVisproductionortest.ENABLE_DEVELOPMENT_LOGIN=trueexplicitly enables the bypass.DEVELOPMENT_LOGIN_USER_ID=1selects the existing user whose session will be created. Replace1if the intended user’s database ID is different.
Restart the server after changing server/.env. When the browser has no active session, the client requests a development session and opens RSSMonster as the configured user without showing the normal credential step.
The selected user must already exist. On a new installation, register the user normally before enabling development login. If the ID is missing or invalid, RSSMonster leaves the sign-in page available and reports that development login is unavailable.
Security Considerations
Development login bypasses the username and password check for the configured account. Anyone who can reach that RSSMonster instance can obtain a session as that user. Use it only for local debugging or a personal instance whose network access is already restricted. Do not expose it to the public internet or use it for a shared installation.
To restore normal authentication, set:
ENABLE_DEVELOPMENT_LOGIN=false
Then restart the server. You may also return NODE_ENV to production for a production deployment; development login is disabled unless both of its gates are explicitly enabled.
For all related environment options, see the configuration guide.