Skip to content

Commit acfb350

Browse files
committed
docs(add): add draft
1 parent 6845722 commit acfb350

File tree

1 file changed

+52
-1
lines changed

1 file changed

+52
-1
lines changed

pages/webhosting/reference-content/shared-hosting-best-practices.mdx

Lines changed: 52 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,5 +13,56 @@ categories:
1313
- webhosting
1414
---
1515

16-
This page teaches you about security best practices when using a shared web hosting offer managed via cPanel.
16+
Your Web Hosting plan is on a shared server, meaning multiple websites are hosted on the same machine. While we have strong protections in place to isolate client environments, you are still responsible for some configurations.
17+
18+
This page teaches you about security best practices and how to secure your space properly.
19+
20+
## General best practices
21+
22+
- Choose a strong password for your account and update it regularly
23+
- Use unique usernames and passwords for each account and service
24+
- Back up your data manually or using the backup hosting option to prevent loss in case of technical issues
25+
- Use the security features provided by your control panel, such as SSL/TLS certificates
26+
- Keep your software and plugins up-to-date for the highest level of security
27+
- Enable the two-factor authentication feature provided by cPanel
28+
- Limit access to files and databases to prevent abuses
29+
- Contact our support team if you have any questions or issues
30+
31+
## Dedicated IP addresses
32+
33+
By default, your hosting plan uses a shared IP address, meaning that the same IP is used by multiple clients on the same server. In case of abuse (if another client sends spam, for example), the shared IP can be blacklisted by other providers, which can block all data coming from the server, thus impacting outgoing mail from being sent.
34+
35+
To avoid this, Scaleway offers a dedicated IP option:
36+
37+
- You get a unique IP address used only by your hosting
38+
- You control your own reputation (especially for email delivery)
39+
- You are isolated from the actions of other users on the server
40+
41+
42+
## File and folder permission settings
43+
44+
You can also keep your website secure by correctly setting file and folder permissions.
45+
46+
### Standard files
47+
48+
File permissions for files such as HTML, CSS, JavaScript, images, etc. should all be set to `644`. A permission of `644` means that the owner of the file will read and write permissions, while other users will only have read permissions.
49+
50+
### Folders
51+
52+
Permissions for folders should be set at `755`, meaning that the owner of the file has every right on the folder, while other users can only read and execute the folder but not alter it.
53+
54+
### Sensitive files
55+
56+
Sensitive files such as configuration files (`.env` files, or `wp-config.php` files for WordPress) should only be accessible by the owner. As such, they should be set to permissions `600`.
57+
58+
### PHP scripts
59+
60+
It is recommended to set PHP scripts to the `755` permissions. If you want to restrict execution to the owner of the script only, set permissions to `744`.
61+
62+
63+
64+
65+
66+
67+
1768

0 commit comments

Comments
 (0)