DigitalBerg
  • HOME
  • WINDOWS VPS
  • VIRTUAL SERVER
    • Virtuozzo VPS
    • OpenStack VPS
    • Amazon Lightsail VPS
    • VMware VPS
  • DEDICATED SERVER
    • INSTAND DEDICATED SERVERS
    • HOSTING DEDICATED SERVERS
    • DEDICATED ENTERPRISE SERVERS
    • INFRA. DEDICATED SERVERS
    • DEDICATED GAME SERVERS
  • MORE
    • SSL SHOP
    • FREE SSD WEBHOSTING
  • LOGIN
  • Click to open the search input field Click to open the search input field Search
  • Menu Menu

Shared SSL and Website HTTPS

Understand certificate coverage before using a shared hostname.

Shared SSL is an older hosting arrangement in which a site may be accessed through a provider-managed secure hostname. It is different from a certificate covering your own domain. Before using any shared address, confirm that your current hosting service supports it and that the certificate matches the hostname.

shared SSL guide: plan the change, use the right tools and verify the result
A practical workflow for shared SSL tasks: plan, change and verify.

In this guide

  1. Shared SSL: understand what the certificate protects
  2. Confirm the supported address with DigitalBerg
  3. Check HTTPS on your own domain first
  4. Resolve validation and DNS problems
  5. Test before forcing HTTPS
  6. Fix mixed content and redirect loops
  7. Monitor renewal and choose a stable public URL

1. Shared SSL: understand what the certificate protects

HTTPS protects the connection to the hostname shown in the browser. A certificate for a server hostname does not automatically cover your business domain. Sharing a server IP address does not require every website to share one certificate.

For a public website, use HTTPS on the domain visitors expect to see. Treat a shared SSL address as a provider-specific option rather than a universal substitute for your own domain certificate.

2. Confirm the supported address with DigitalBerg

Ask support whether shared SSL or a secure preview address is available for your account. Use the exact hostname and path supplied. Do not invent a secure hostname by replacing words in a server name or copying another provider’s example.

A legacy /~username/ address may be disabled or unsuitable for an application that expects its own domain. Your hosting welcome details and support team are more reliable than a guessed address.

3. Check HTTPS on your own domain first

In cPanel, look for SSL/TLS Status or the status tab within SSL/TLS Certificates. Check the required domain and www variant, certificate expiry and coverage. Available tools depend on the server and account features.

If AutoSSL is available, use the provided controls or ask support about issuance. The official status documentation explains how to inspect certificate details. Avoid assuming that every account has the same certificate provider.

4. Resolve validation and DNS problems

Confirm that DNS points to the intended server and that required validation requests can reach it. Incorrect IPv6 records, restrictive CAA records or a proxy configuration can affect issuance and should be reviewed with the provider.

Use our DNS zone guide when checking records. Preserve existing mail settings and other services while correcting website records.

5. Test before forcing HTTPS

Visit the intended HTTPS address directly and inspect the certificate name and expiry. Test the homepage, login, forms and important application pages before adding a redirect from HTTP.

If the browser warns about certificate validity, stop and correct the cause. A shared SSL link is not ready for normal use merely because a warning can be dismissed. HTTPS also does not prove that the application itself is secure.

6. Fix mixed content and redirect loops

Review images, scripts and styles still requested over HTTP. Update the relevant application settings and stored URLs using tools appropriate for that application, with a backup before bulk changes.

If redirects loop, check the interaction between the application, server and any CDN. Decide which layer manages the redirect and make sure the application recognises the original connection scheme behind a trusted proxy.

7. Monitor renewal and choose a stable public URL

Set a check for certificate expiry and confirm that automatic renewal works. Test again after a hosting move, DNS change or proxy change. Keep your public links and sitemap consistent with the preferred HTTPS domain.

Shared SSL can also change cookies, paths or redirects because the hostname differs. For production sites, ask DigitalBerg to help establish a domain-based certificate and a tested redirect plan.

Shared SSL questions

Can I use the server IP address?

Only if the certificate and server configuration actually support that address. Most domain certificates are intended for named hosts, so use the confirmed hostname instead.

Do I need a dedicated IP for HTTPS?

Modern hosting commonly supports multiple domain certificates on a shared IP through SNI. Ask support about any special client compatibility requirements. If you are moving a site, include HTTPS checks in the migration plan.

Need help with your hosting?

For help with shared SSL, contact DigitalBerg with the affected domain, the step you tried and a redacted error message. Never include passwords, private keys or complete configuration files containing secrets.

Contact DigitalBerg Support

Get help with your hosting configuration and the steps in this guide.

digitalberg.com

DigitalBerg fuels apps, websites, emails, and much more for numerous clients globally.

Virtual servers to dedicated servers at affordable prices that any hostinger student can afford.

Services

  • Web Hosting
  • Virtual Server
  • Instant Servers
  • Dedicated Servers
  • Enterprise Servers
  • Infrastructure Servers
  • Gaming Servers
  • SSL Shop

SUPPORT

  • Contact Us
  • Wiki
  • FAQ
  • Blogs

Company

  • About Us
  • Partners
  • Privacy Policy
  • Term of Service
  • Acceptable Use Policy
  • Green Hosting
  • Data center

CLIENT AREA

  • Registration
  • Client Area
  • Server Status
  • Support

OTHER SERVICES

  • Domain Registration
  • Transfer Domain
  • Add ons / Management
  • SSL Certificates
  • Server Monitoring
  • Server hardware
DigitalBerg review
DigitalBerg review
© Copyright - DigitalBerg | From January 1st 2015, in accordance with the amended Directive 2006/112/EC, prices inclusive of VAT may vary depending on the country of residence of the customer.
  • Link to Facebook
  • Link to X
  • Link to LinkedIn
Link to: How to Move Your Site from Joomla to WordPress Link to: How to Move Your Site from Joomla to WordPress How to Move Your Site from Joomla to WordPress Link to: How to Export and Import in WordPress Link to: How to Export and Import in WordPress How to Export and Import in WordPress
Scroll to top Scroll to top Scroll to top