Member Avatar for DavidBlumenson

Hello There,
I am David Blumenson. I am here to discuss a problem with one of the website. When I try to open the website with http:// it gives error while it show with https:// . Please suggest me what should I do?

  • 3 Contributors
  • 4 Replies
  • 131 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by stopscamsonline

Dani AI

Generated

The thread shows the site loads over HTTPS but fails over HTTP. pointed toward server-side configuration; below is a concise diagnostic checklist and practical fixes to get HTTP working (or reliably redirect it to HTTPS).

First, capture the exact browser error and test reachability from a remote machine: check DNS, then test TCP and HTTP connectivity. Useful quick checks:

nslookup example.com
curl -I http://example.com -v
# on Linux
ss -tlnp | grep ':80'
# on Windows
netstat -an | find ":80"

If DNS resolves but the HTTP request times out or is refused, the issue is network/firewall or the webserver not accepting connections for port 80.

On the server itself verify the webserver has an HTTP binding or virtual host. Typical fixes:

# Apache: redirect every HTTP request to HTTPS
<VirtualHost *:80>
  ServerName example.com
  Redirect permanent / https://example.com/
</VirtualHost>
# Nginx: simple 301 to HTTPS
server {
  listen 80;
  server_name example.com;
  return 301 https://$host$request_uri;
}

For IIS, add an HTTP site binding in IIS Manager and, if you want automatic upgrade, create a redirect rule with the URL Rewrite module. Microsoft has a how‑to for SSL and bindings: Set up SSL on IIS.

Also check perimeter controls: host firewall, router/NAT, cloud security groups, or a load‑balancer/reverse proxy that might accept HTTPS only. If you plan to force HTTPS, enable a 301 redirect on port 80 and consider HSTS only after certs are confirmed; see the HSTS header details at MDN Web Docs. For server‑specific SSL/TLS setup see Apache SSL/TLS How‑To and Nginx HTTPS server docs.

Note: the comment by concerns moderation, which is separate from the technical steps above.

Recommended Answers

All 4 Replies

Member Avatar for JorgeM

What is the error?

It could simply be that the website was configured to only listen on port 443 (https). While most web site administrators will configure the web to listen on at least port 80 (http), there is no rule that states it must be.

Member Avatar for DavidBlumenson

Hi
What should I do that, my website work for both HTTP and HTTPS

Member Avatar for JorgeM

First make sure that your website is listening on port 80. Provide the error message that you see in the browser.

Member Avatar for stopscamsonline

Mods, lock this thread up (or better yet, delete it). This is a scam. It's known as SEO to clean up a reputation. Type in 'David Blumenson scam' on Google to find out more about this guy. He's obviously looking for new investment funding and wanting to hide his previous exploits by spamming page 1 results for 'David Blumenson' on Google. Now people will find random results with fake questions on page 1, hiding what he's done. best thing would be either to rename this thread to highlight the scam or just delete it completely so that it disappears from Google.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.