Preparing your experience
Topic collection
Hosting, migration, speed and performance guidance for reliable websites and applications.
19 guides
A proxy or CDN shows a 502 Bad Gateway or 503 Service Unavailable page. A 502 usually indicates an invalid upstream response, while a 503 commonly signals unavailable or intentionally overloaded capacity.
The browser says the certificate belongs to another domain or does not cover a subdomain. The request may reach the wrong virtual host, CDN or certificate bundle even though HTTPS is enabled.
Some visitors reach the new server while others still see the old website after a DNS change. Resolvers retain the prior answer until its TTL expires, but incorrect nameservers or duplicate records can mimic propagation.
A domain points to new DNS hosting and the website works, but incoming mail disappears or bounces. Nameserver changes move authority for the whole zone, so missing MX and authentication records override the previously working mail setup.
Search results expose a test domain containing duplicate, unfinished or private-looking content. The staging host was publicly crawlable and may have been discovered through links, sitemaps or copied analytics.
Uploads, backups, email or updates fail even though the control panel appears to show some disk space. Shared hosting may limit file count separately from total bytes; caches, sessions and old backups can consume many small files.
Compare shared and dedicated hosting based on traffic, control, security responsibility, performance, support and budget.
Understand what Core Web Vitals measure, why field data matters and which practical changes can improve loading, responsiveness and stability.
Identify common reasons for a slow website, including oversized media, server delays, heavy scripts, plugins, fonts, caching and database work.
