Control Panel FAQs

For hosting control, open https://plesk1.globalmcs.net/ and sign in with the hosting credentials supplied for your account. Plesk manages hosting files, databases, mail, and other enabled subscription features.

For user account and billing management, open https://dashboard.globalmcs.net/. These are separate destinations; no automatic single sign-on is assumed. If you cannot sign in, contact support without sending your password.

You do not have to move your domain registration or use Global MCS nameservers to host a website or mailbox here. You may keep external DNS and apply the exact website and email records supplied for your account.

If you choose Global MCS-managed DNS, confirm the nameserver assignment in your activation details before changing delegation. The Global MCS nameserver set is:

• NS1.GLOBALMCS.NET
• NS2.GLOBALMCS.NET
• NS3.GLOBALMCS.NET
• NS4.GLOBALMCS.NET

Ensure the destination DNS zone contains your website, mail, verification, and other required records before switching nameservers. Ask support for the assigned IP/MX values rather than guessing.

DNS changes often start working within a few hours, but allow up to 48 hours as a general estimate. Existing record TTLs, resolver caches, and registry updates affect timing; this is not a guaranteed deadline.

Use your activation details for any account-specific differences from these standard mail settings:

• Username: Your full email address; use your mailbox password.
• IMAP (recommended): webmail.globalmcs.net, port 993, SSL/TLS.
• POP3 (alternative): webmail.globalmcs.net, port 995, SSL/TLS.
• SMTP: webmail.globalmcs.net, port 465 with SSL/TLS, or port 587 with STARTTLS.
• SMTP authentication: Required, using the same full email address and mailbox password as incoming mail.

Use the server hostname supplied for your account. A custom name such as mail.yourdomain.com works only when its DNS and valid certificate are configured for that name. If a certificate warning appears, stop and contact support to correct the hostname or certificate. Do not bypass the warning or disable certificate validation. Enter your password only in your own mail application or verified control panel, never in a support chat.

For typical Linux hosting, 755 is a common directory permission and 644 is common for files, including PHP files served through the web server. These are starting points, not universal rules: ownership, the PHP handler, application requirements, and ACLs determine the right access.

PHP files do not normally need an executable bit. CGI or command-line executables may need different permissions. Sensitive configuration files may use 400 or 440 only when the required service user can still read them and the application does not need to write them. Windows hosting uses different permission controls.

1. In Plesk Files, find the specific file/folder and open its permissions control, where available.
2. Alternatively, use the permissions/properties control in an authorized file-transfer client such as FileZilla or WinSCP, if supported by the server/protocol.
3. Record the existing permissions, change only the required item, and verify the application afterward. Do not apply blanket recursive changes or 777 to solve an error; ask support when ownership or required access is unclear.