Chmod Calculator Full Guide: 644/755/7000 Permission speed and security configuration
On the server. chmod 644 file Can I read and write about someone else?chmod 755 dir Can the directory be executed?chmod 777 Is it safe? The error in the document permission at the time of the coup resulted in 403-percent or the fact that the students in the school were only able to tell you "change 644" without indicating whether it was a document or a catalogue, a document owner or a group ... The most time-saving approach is to read it and change it. Map of the focus values and symbols, safe boundaries, actionable steps, directly in KiloCell of cells in this Guide Chmod Calculator。
The core sentence.
It is readable and written (document), and 755 is readable and enforceable (catalogue). Symbol mode changes only the permission slot and not the owner/group.
(a) The permission mode is understood and the value or symbol is determined; We'll figure it out first. We'll do it. chmod (a) Orders; Try again and implement it on a large scale in the production environment.
1. Basis of competence: three-digit category
Linux file permissions are made up of three parts (ls-l see drwxr-xr-x）：
- File type (d = directory, -- = file, l = link...)
- Owner (owner) permission: r w x
- Group Permissions
- Other (others/world) permissions
Each with three abilities to read/write/implement, for use r=4, w=2, x=1 Composes the octal number.
| Permission Position | Value | Documentation | Table of contents | Meaning |
|---|---|---|---|---|
| Read (r) | 4 | Readable | Columnable Directory Contents | cat / ls / kubectl get |
| Write | 2 | Modifyable | Sub-paragraphs that can be created/deleted | touch / rm |
| Implementation (x) | 1 | Executable | Yeah. cd / ls Sub-items |
Script / Enter Directory |
Three digits: Owner + Group + Others. Typical 644(rw-r-r-) or 755（rwxr-xr-x）。
Symbol Mode(Really used) chmod u+x file):u = owner, g = group, o = others, a = all; + = Add, - = Remove, = Set.u=rwx The project is "Road and write execution by the owner".
2. Value vs symbol: when to use
| scene | Numeric Mode | Symbol Mode | Advantages |
|---|---|---|---|
| One-time quick count | 644、755、700 | More flexible. | Values are easy to remember. |
| Script / Automation | Value | Both. | Scripts are more visible |
| Multi-person understanding | Value | Symbol | Teams are different. |
| Batch changes | Value | Common Symbols | Batch symbols are easier |
| Permission Embedded Understanding | Value | Symbol | Bring + - Clearer |
Decision-making recommendations:
- Only "to 644" should be used to fill the numbers directly in the calculator or with a symbol
u=rw,g=r,o=r。 - Also need to use a symbol for "add execution" or "extract group privileges".
chmod u=rw,g=r,o=r file。 - The group flat value (e.g. 644 for the file) is safer.
- Day
lsSee permissions to → numeric mode most visible.
The KiloCell calculator provides both numerical input boxes (644/755/7000 pre-set buttons) and symbol mode input, which allows for the switchover of the two habits.
3. Competence trap and security border
| Traps | Example | Consequences | How? |
|---|---|---|---|
| 777 | Anyone who reads or writes execution | Security risk highest | (b) Temporary debugging or public network testing only; Production documents are changed 644 |
| 666 | Read and write for all (no execution) | Script cannot be executed | For 644/754 |
| 600 | I'm the only one who can read and write. | The group/others can't see at all. | (b) The common use of production of sensitive documents; Not for Shared Directory |
| 644 Documentation | All right, read and write, group/others only read | Normal; No enforcement is not possible cat > file |
Common server files |
| Contents | Read-and-write execution for all | Normal; Default for sub-items 755 | Recommended Directory Mode |
| No execution position | File Unenforceable | chmod +x file Or change 755. |
Scripts must be enforceable once deployed |
| Group Permission modified | Replace 640 with | Only by yourself and by a specific group. | Production 644/660 Distinction |
| Directory not executed | ls dir Failed |
chmod +x dir |
Directory must be searchable |
| Symbol mode is misused | chmod +x file And then it's changed. 644. |
Missing Executor | (a) Recalculating and re-engineering; Or use numerical mode |
Clear checklist.
- Production documents/catalogues don't want 777
- Sensitive files (e. g. key, token script)600 or 400
- Shared directories (e.g. upload)755 + Group 664
- Scripts must have an execution place
- Before changing permissions,
ls -lConfirm file type with owner - Batch change
find+ xargs or Ansible, avoid one by one
4. Operational steps (directing to calculator)
- Open Chmod Calculator(Standpoint has dev classification page, same effect).
- Select mode:
- Value: Fill in 644/755 700 or customize
rwxValue - Symbol: Filling
u=rwx,g=r,o=rora=rx
- Enter the filename (optional, only result does not change the system).
- Click 「Calculate」 or a preset button.
- View results:
- Numerical mode shows the final octal (e.g. 755)
- Symbol mode displaying final
rwxr-xr-x - Replicable command to clipboard (
chmod 755 dir）
- Copy command to terminal or script:
chmod 644 file.txtchmod -R 644 .(Machine)
- Execute Authentication: Renumbered
ls -l file.txt(a) Confirmation of the position of authority;ls -l dir/Checking the enforcement position;test -x fileInspection is enforceable. - Batch scene: used
find /path -type f -exec chmod 644 {} +Or Anseble Playbook.
Common failure check
- Can't change it? Checks file locks, inadequate access, file system read-only.
- Redirection 644 after lls No sub-sections? The contents of the directory must be listed at 755 or more.
- You want to re-establish the authority? 664 (group) or 640 (ungrouped).
5. Common errors
| phenomena | Reason | Processing |
|---|---|---|
| Change 644 after directory is not available | Missing execution slot | Rephrase 755 |
| Script "Low Permissions" | The executive position is removed. | chmod +x script.sh |
| Rephrase 777 and release data. | Anyone can write. | Renumber 600 |
Symbol Mode chmod g+w The post-grouping didn't work. |
Father directory is not executed or file type is not correct | Check Type and Directory |
Batch changes chmod -R 644 The rear directory is not accessible |
Subdirectories Overwrite | Use find + -exec chmod Deal with directories and files separately |
| Numerical mode 644 Post file grouping is removed | Symbol mode unexpectedly | The number pattern is more stable. |
| The owner can't see his file after the change. | I've changed the position of the wrong person. | Use ls -l Confirm 3 digit |
6. Real scene
Scenario A: deployment of scripts with executive position
chmod +x deploy.sh or value 755。 The production environment script must be enforceable, otherwise the CI cannot run. It is recommended that the numerical model should be harmonized for the warehouse engagement.
scene B: Share Upload Directory
chmod 775 /uploads(grouping)+ chmod 755 /uploads。 Avoid 777 exposure of sensitive documents. Calculator provides 775 presets.
Scenario C: Sensitive Key File
chmod 600 /secrets/key.json。 No one has the right to go, group/other must be 000. Calculator can fill 600.
scene D:Docker mirror or container file
(b) The usual documentation in the packaging 644; Watch directory mode when volume mounted. Confirm by the aligning calculator ls -l /var/log Result。
Scenario E: Batch-to-lot multiple settings
Change the same privileges on multiple servers or containers in scripts:
find /path/to/configs -type f -exec chmod 644 {} +
chmod -R 755 /etc/myapp/
Calculator can calculate 644/755 in one-time.
8. Pre-publication checklist
- [ ] Selected values or symbol modes, matching team habits
- [ ] Target document or directory (directorial must be executed)
- [ ] No production environment confirmed 777
- [ ] Sensitive documents already 600/400
- [ ] The command has been copied to the terminal or script and executed
- [ ] Implementation of validation
ls -landtest -xPass. - [ ] Batch orders
+, not recursive overlay subdirectories - [ ] Non-dissensitization of sensitive data leaks
9. Common issues
What difference does it make between documents and documents 755?
The following is a list of the "document" (no execution position) and 755 is "catalogue" (execution position). The error will fail or not be enforceable.
What happens when the symbol mode `chmod u+x ' is changed to 644?
Will remove the execution slot and become 644. It is suggested that the final values be calculated and then the numerical pattern used.
Could you use 777 temporary debugging?
Temporary debugging, but production environments are strictly forbidden. Calculator provides a 777 preset to facilitate demonstration.
Will anyone else see the document after the re-organisation of the authority?
chmod 640 None but is still readable;chmod 600 No one can read it.
Does changing the privileges in the container affect the host?
Not unless you use the Privileged mode or mount the host file system. The modifications in the packaging do not affect the host of the host.
Next steps
- Yes. Chmod Calculator Fill in 644/755 700, copy command to terminal validation.
- Write a sensitive script, then 600.
ls -lConfirm. - Quits the use of the user permissions (644 files, 755 directories, 600 keys) and consolidates them into the project README or CI configuration.
- When daily traffic is “regulating” the results and then changing them, the error is avoided.
--title: Full guide to HTTP status code: 2x/4xx5/xse: Description: Description of HTTP status code classification, common 2x/4xx5/x scenes, typographical steps and inter-coordination strategies, and a control table, scene and selection, with KiloCell of HTTP status code query tools. Keywords: HTTP state code, HTTP Status Code, 2x success, 4x client error, 5x server error, incoordination, API debug tag: development tool type: how to slug: http-status-guide datePublished: "2026-08" dateModified: "2026-08" reminds Minutes: 12 PrimaryTool: /tools/dev/http-status-codes relatedTools:
- /tools/dev/api-testing
ToolCta: HTTP Status Code Scatter — 2x/4x5/xx Query sideBtn: immediately open the HTTP Status Code Query ShortCrumb: full guide to HTTP status code lead: > 401 "Unauthorized" ; 404 "Unable to find" ; 500 "Schiller error" Quest when you connect: "What is this? I have no idea where I'm going. This Guide describes 2x/4xx/5xx classification, typical scenes, sorting steps and tool selection, directly in KiloCell HTTP Status Code Query。 ---
The core sentence.
2xx succeeded, 4xx client error, 5xx server error; First, look at the status code, then look at the response.
Distinction of categories and repositioning of specific sub-codes; First, we use the tools to define it and then we think about the response in the context of the alignment.
1. Three types of status code
HTTP status code is divided into five categories (RFC 9110), the first two are of a determinative nature and the latter two are more detailed.
| Category | Scope | Meaning | Typical tool |
|---|---|---|---|
| 1xx | 100-199 | Information (testing) | Use less debugging |
| 2xx | 200-299 | Success | Here's the flow of production. |
| 3xx | 300-399 | Redirect | 302/301 Common |
| 4xx | 400-499 | Client Error | - Yeah, I'm gonna go ahead and get it. |
| 5xx | 500-599 | Server error | Checking logs/monitoring |
| 6xx | 600-699 | Undefined | Very rare. |
2xx Core: Expressed the successful completion of the request. Common subcode:
- 200 OK: Everything's fine.
- 201 Created: Resources successfully created
- No Content: Successful but non-contentive returns
- 206 Partial Content: Partial Request Successful
4xx Core: Request has a syntax error or the server cannot process it. Common subcode:
- 400 Bad Request: General client error
- Unauthorized: Uncertified
- 403 Forbidden: Certification passed but not authorized
- Not Found: Resources do not exist
- Method Not Allowed: Method not supported
- 409 Conflict
- Unproven enterprise: semantic error
5xx Core: Server-end problem. Common subcode:
- 500 Internal Server Error: General
- 502 Bad Gateway: Upstream error
- Service Unaviable: Services temporarily unavailable
- 504 Gateway Timeout: Gateway timeout
2. Typical conjunctive scenes
Scenario A: Back-to-back interface is not working
- 401/403: Frontend expired with token or token
- 404: Interface path or resource does not exist
- 500: Backend code anomaly, database connectors pool, configuration error → Log, metrics
- 422: JSON authentication failed → Check requested field
Scenario B: Greyscale/Abnormal Production Flow
- 503: Melting, restricted flow, full container, see melting strategy, QPS
- 504: Upstream timeout Check networks, databases, third-party dependence
C:K8s / Container Environment
- 404: ConfigMap / Secret unmounted
kubectl describe - 500: Pod startup failed
kubectl logs、kubectl describe pod
scene D: Move / Cross-domain
- 403: CORS pre-screen failed → Check Access-Control-Allow-Origin
- 429: Limit flow → Backend returns Retry-After
3. Operational steps
- Open HTTP Status Code Query。
- Enter a status code in the search box (e.g.
401、500、404）。 - View title, description, category.
- Reasons for the screening in conjunction with the response, if any.
- Copys a common command or script to locale.
4. Common errors
| phenomena | Reason | Processing |
|---|---|---|
| 401 but thought it was 403. | The authentication process is not complete | Check token validity and signature |
| 500, but I thought it was 400. | Server peer code anomaly | Logs, metrics, stacks. |
| 404. Resources exist. | Path error or permission question | Check OpenAPI, permissions |
| 503 Response empty | Service is restarting. | Checking for health. |
| 429, but I thought it was 404. | The flow is limited. | Check the name of the RateLimit header |
| 502, but I thought it was 500. | Upstream gateway issues | Check load balance, timeout |
6. Checklist
- [ ] Is it clear that 4xx or 5xx
- [ ] See if the response contains the wrong message.
- [ ] Check logs/mecrics
- [ ] Think of responses in the context of the joint scenario
7. Common problems
Can 2x and 4x switch?
Can't. 2xx indicates success, 4xx indicates error on client. Returns 200 with the wrong message is a backend code problem.
500. Is the server broken?
Not necessarily. It may be a question of database connectivity, configuration, and dependence. Read the log for specific reasons.
404 Resources exist. Why return?
Path error, inadequate permissions, or resources deleted. Check OpenAPI or path.
Can you use 2xx status code to indicate "warn"?
Not regulated. 2xx must be successful. The warning is 200+additional fields or 206.
You want to read the status code or the responder when you're in touch?
First, the state code, 4xx/5xx, is usually the core issue.
8. Next steps
- Yes. HTTP Status Code Query Zaa, 401/500/404.
- Take a real interface response, look at the status code, then look at the response.
- Write a connection checklist: status code → response → log.
- Teams share common state codes to avoid every check.