A 403 response means the server understood the request but refused access. Determine whether it affects one file, one directory, one IP address, or the whole site.
Before you begin
Sign in through the official client area and keep account-specific values from your activation email available. Make a backup before changing production data or configuration.
Steps
- Check the path and index: Confirm the domain’s document root and that a permitted index file exists.
- Review permissions and ownership: Compare affected files with known-good files. Typical values are 644 for files and 755 for directories, but follow platform guidance.
- Inspect access rules: Review .htaccess or equivalent server rules for deny directives, password protection, hotlink controls, and malformed rewrites.
- Check security blocks: Temporarily test from another network and review firewall or application-security logs for your public IP.
- Check account state: Storage limits, malware quarantine, or service restrictions may intentionally deny access.
- Revert safely: Restore the last known-good rule set or file from backup, then test the exact URL again.
Important notes
- Do not set files or directories to world-writable permissions as a workaround.
- If only your network is affected, give support your public IP and the timestamp of a blocked request.
When to contact support
Contact support if the documented controls are unavailable, the service reports an account-level restriction, or the issue continues after these checks. Include the affected domain or service, the exact error, a timestamp with timezone, and the steps already tried. Never include passwords, one-time codes, private keys, or complete payment details.
