h1bsalarydata.com runs on a DigitalOcean droplet managed through Ploi and built with PHP-Laravel. Although a Let’s Encrypt certificate is installed, some visitors still see “insecure” warnings or fail to load the site at all. Browsers report mixed-content calls—scripts, images and CSS are still being requested over HTTP—so the padlock is inconsistent, and overall reachability varies by user. Your task is to pinpoint the exact cause, correct the SSL chain, and make sure every asset loads securely over HTTPS across all regions. That means reviewing and adjusting the current DNS records, Ploi configuration, Nginx/Apache (if relevant) rules, Laravel asset references and any server-level settings that could be forcing or blocking HTTP/HTTPS traffic. Deliverables (all must be met): • Fully trusted Let’s Encrypt certificate served on www and non-www domains. • Automatic 301 redirection from HTTP to HTTPS with no infinite loops. • All scripts, images and CSS loading via HTTPS—no mixed-content warnings. • Consistent global reach confirmed by tools such as SSL Labs and DNS propagation checkers. • A concise summary of changes made so I can replicate the setup on future deployments.