{"id":50405,"date":"2018-09-20T13:49:49","date_gmt":"2018-09-20T18:49:49","guid":{"rendered":"https:\/\/blog.cpanel.com\/?p=50405"},"modified":"2018-09-20T13:49:49","modified_gmt":"2018-09-20T18:49:49","slug":"renaming-proxy-subdomains-to-service-domains","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/products\/renaming-proxy-subdomains-to-service-domains\/","title":{"rendered":"Renaming Proxy Subdomains to Service Domains"},"content":{"rendered":"
In cPanel & WHM version 76, which we expect to be in EDGE this week, we renamed “Proxy Subdomains” to “Service Subdomains” due to improvements we are making under the hood. Let’s talk about where they came from, and why we’re changing their name!<\/p>\n
Proxy subdomains<\/a>\u00a0allow users to connect\u00a0indirectly\u00a0<\/span>to the cPanel & WHM login pages. Rather than opening <\/p>\n Users can enter\u00a0<\/em> We are currently developing a new\u00a0cPanel & WHM feature based on different kinds of\u00a0server configuration profiles<\/a>. This feature is included in version 76, but is also marked as experimental. One of these profiles is called a\u00a0Mail Profile<\/a>, and the\u00a0Mail Profile\u00a0is optimized\u00a0<\/span>for email hosting.\u00a0This server profile disables most of the services that do not\u00a0<\/span>directly\u00a0<\/span>support mail and includes other improvements<\/span>. These improvements result in leaner memory and CPU usage, and better overall experience!<\/p>\n On a cPanel & WHM server, there is a daemon that we run called\u00a0example.com:2083<\/code>,\u00a0they can open\u00a0
cpanel.example.com<\/code>. Proxy subdomains have two primary uses for hosting providers and cPanel users. First, they help make remembering how to access cPanel easier.\u00a0
cpanel.example.com<\/code>\u00a0is much easier to remember than\u00a0the port number\u00a0
2083<\/code>\u00a0or\u00a0the URL\u00a0
example.com:2083<\/code>. Second, they make it easier to access cPanel. It is fairly common for a network administrator to block access to non-standard ports. Any user who is unable to connect to port 2083 can navigate to\u00a0
cpanel.example.com<\/code>\u00a0to bypass this restriction.<\/p>\n
<\/a><\/p>\n
cpanel.example.com<\/code>\u00a0to log in to their server<\/em>.<\/p>\n
Why the change?<\/h2>\n
cpsrvd<\/code>. For this blog post, think of\u00a0
cpsrvd<\/code>\u00a0as the entire cPanel & WHM product, including cPanel, WHM, and Webmail. On a standard server, Apache (the webserver) would listen on ports\u00a0
80<\/code>\u00a0and\u00a0
443<\/code>\u00a0(the standard web ports) and proxy the cPanel, WHM, and Webmail subdomain traffic as an intermediary to\u00a0
cpsrvd<\/code>.\u00a0In the Mail Profile,\u00a0
cpsrvd<\/code>\u00a0now listens to ports\u00a0
80<\/code>\u00a0and\u00a0
443<\/code>\u00a0directly, without Apache in the middle<\/span>. Apache will not need to proxy traffic on the Mail Profile server.\u00a0For this reason, we are renaming “Proxy Subdomains” to \u201cService Subdomains.\u201d This\u00a0name more\u00a0<\/span>clearly\u00a0<\/span>describes the subdomains\u2019 purpose, rather than focusing on the implementation<\/span>.<\/p>\n