IP-lock for ecommerce admin
A public admin URL on a store handling real payments is an invitation for credential stuffing. Self-hosted means you set the access rules, not a shared SaaS panel.
What this is
NitroCart supports IP allowlist for admin access and SSH. The Windows desktop deployer also respects IP allowlist and uses the ncadmin path — your VPS, your lockdown policy.
How it works in NitroCart
- Deploy-time lockdown: restrict admin and SSH to allowlisted IPs or VPN.
- Desktop deployer: IP allowlist on the Windows tool plus ncadmin admin path.
- Per-VPS policy: each copy on your license can have its own allowlist.
- Engine settings → Backup: secure snapshot before access rule changes.
Who it is for
- Operators handling real payment volume on self-hosted stores.
- Agencies isolating client admin access by office IP.
- Teams replacing shared SaaS admin with VPN-only access.
Workflow
- List office and home IPs that need admin access.
- Configure allowlist during deploy via desktop deployer or post-deploy settings.
- Verify ncadmin path loads only from allowed IPs.
- Test checkout from a non-admin IP to confirm storefront stays public.
- Document VPN fallback for travelers on the ops team.
FAQ
Lock myself out?
Use VPS provider console to adjust firewall if allowlist is wrong.
Storefront blocked too?
IP lock applies to admin — customers reach the shop normally.
SaaS-style 2FA?
IP/VPN lockdown is the primary self-hosted access control.
Next: Self-hosted store engine: your VPS, your data, no turnover cut, Docker and patches: a closed update contour.