Quick answer
A web proxy and non-web services use different connection paths. Use the service endpoint and proxy setting appropriate to the protocol rather than assuming the website hostname is also the SSH or mail server. The correct settings depend on your DNS and service provider.
Before you start
Identify which hostnames handle the website, mail, SSH/SFTP, and control panel. Obtain the documented connection details and preserve the current DNS records before changing proxy behavior.
What to do
- Use the hosting-provided SSH hostname and port for shell or SFTP access, and verify the server fingerprint independently.
- Use the secure mail host and ports shown in the mailbox's connection settings. Do not guess from the public website URL.
- Review proxy status for non-web service names against the DNS provider's supported protocols and your service instructions.
- Change only the intended record and test that protocol separately from normal browser access.
Check the result
A working homepage does not prove that SMTP, IMAP, or SSH is correctly configured. Verify each service with its own client and authentication flow.
If something does not work
If a connection fails, share the hostname, selected protocol, port, and sanitized error with support. Do not expose an origin address unnecessarily or disable unrelated protection rules while diagnosing a non-web service.
Related help
- Troubleshoot cPanel, SSH and SFTP login problems
- Find the correct secure IMAP and SMTP settings for your mailbox
- Find where your domain's DNS is managed before changing records
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
