IP Whitelisting and Editing Your Database
ជំពូកនេះមិនទាន់ត្រូវបានបកប្រែជាភាសាខ្មែរនៅឡើយទេ — សូមអានជាភាសាអង់គ្លេសខាងក្រោម។
Table of Contents
- What the IP whitelist does
- Setting the whitelist
- Choosing what to allow
- Editing an existing database
- Beginner Pitfalls
1. What the IP whitelist does
A database that accepts connections from anywhere will be found and attacked within hours of going online; bots scan for open database ports constantly. The IP Whitelist limits which addresses may connect. With it enabled, only listed IPs get in; everyone else is turned away before they can even try a password.
It is the single most effective protection you control, so decide on purpose rather than by default.
2. Setting the whitelist
You can set it in two places:
- At creation — on the Database Information step, tick Enable
next to IP Whitelists. A tag input appears (placeholder e.g.
192.168.0.1): type an address and press Enter to add it as a chip;
click the
xon a chip to remove it. - Later — on the database's detail page, the IP Whitelist panel on the right lists current entries. Click Add + to add one.
Entries can be single addresses (203.0.113.25) or ranges in CIDR form
(203.0.113.0/24). The special entry 0.0.0.0/0 means every
address — the dashboard shows it as a chip when you enable the
whitelist without narrowing it.
3. Choosing what to allow
| Situation | What to add |
|---|---|
| Just you, from home or the office | Your public IP (search "what is my IP") |
| A small team in one office | The office's public IP, or its CIDR range |
| A Run App stack on Cloud+ | Nothing to look up: the stack connects using the RunApp Connection host name |
| Quick throwaway test | 0.0.0.0/0 — then remove it when you're done |
Home internet connections often change public IP now and then. If you suddenly can't connect and nothing else changed, your IP probably moved — update the entry.
0.0.0.0/0is "open to the world". It's fine for a disposable practice database. For anything with real data it should never be the final setting; the strength of your password is then your only defense.
4. Editing an existing database
Click EDIT at the top right of the detail page. You get the same form as creation, pre-filled, with a few differences:
- The DB Administrator is still read-only
root. - You can change the IP whitelist and the Back Up option.
- Changes apply when you click UPDATE.
To change the size of the instance (CPU, RAM, disk), use NEW PLAN in the Your Plan card instead, which takes you through plan selection again.
5. Beginner Pitfalls
- Whitelist enabled with an empty or wrong list — everything, including you, is blocked. Add your own IP first.
- Forgetting that your IP changed after a router restart or moving networks.
- Leaving
0.0.0.0/0in place after "just testing". - Treating the whitelist as a substitute for a strong password. Use both.
ទិញកាហ្វេជូនខ្ញុំ
ចូលចិត្តមេរៀននេះមែនទេ? សូមពិចារណាទិញកាហ្វេជូនខ្ញុំមួយកែវ ដើម្បីគាំទ្រការបង្កើតមាតិកាឥតគិតថ្លៃបន្ថែមទៀត!