Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

I'm having trouble accessing my local network devices with http

  • 1 תגובה
  • 0 have this problem
  • תגובה אחרונה מאת jbr
  • Open

carles5
carles5

Hi everyone,

I'm having trouble accessing my local network devices (a 3D printer and Raspberry Pi) using short hostnames like "http://impressora3d" or "http://impressora3d/". Firefox keeps blocking the connection with the "Looks like there’s a problem with this site" error page.

I've captured a network log using 'about:networking' and I can see that: 1. DNS resolution works perfectly and points to my local IP: 

  "CompleteLookup: impressora3d has 192.168.1.10"

2. Firefox is upgrading the request to HTTPS (port 443) automatically: 

  "nsSocketTransport::ResolveHost [...] impressora3d:443" -> "pushing io layer [0:ssl]"

3. The device rejects it because it only listens on HTTP (port 80): 

  "Bad Socket 804b000d" (NS_ERROR_CONNECTION_REFUSED)

What I have already tried: - Disabled "HTTPS-Only Mode" entirely in settings. - Checked "Secure DNS" (DoH) settings (set to Increased Protection and added exceptions). - Cleared history and used "Forget about this site" on the hostname. - Typed "http://" explicitly.

Firefox still refuses to connect via plain HTTP (port 80). Is there any hidden 'about:config' preference or HSTS cache forcing this behavior for local unformatted domains?

Thank you!

Hi everyone, I'm having trouble accessing my local network devices (a 3D printer and Raspberry Pi) using short hostnames like "http://impressora3d" or "http://impressora3d/". Firefox keeps blocking the connection with the "Looks like there’s a problem with this site" error page. I've captured a network log using 'about:networking' and I can see that: 1. DNS resolution works perfectly and points to my local IP: "CompleteLookup: impressora3d has 192.168.1.10" 2. Firefox is upgrading the request to HTTPS (port 443) automatically: "nsSocketTransport::ResolveHost [...] impressora3d:443" -> "pushing io layer [0:ssl]" 3. The device rejects it because it only listens on HTTP (port 80): "Bad Socket 804b000d" (NS_ERROR_CONNECTION_REFUSED) What I have already tried: - Disabled "HTTPS-Only Mode" entirely in settings. - Checked "Secure DNS" (DoH) settings (set to Increased Protection and added exceptions). - Cleared history and used "Forget about this site" on the hostname. - Typed "http://" explicitly. Firefox still refuses to connect via plain HTTP (port 80). Is there any hidden 'about:config' preference or HSTS cache forcing this behavior for local unformatted domains? Thank you!

כל התגובות (1)

jbr
jbr
  • Top 25 Contributor

Could you attach a screenshot of the error incl. any "advanced" sections expanded? Thanks.

When you access just the IP it works as expected?

If you force the :80 port http://impressora3d:80 do you get the same, anything else, or something like "record too long" error etc.?

Are you able to open http://httpforever.com/ …?

(Normally I'd suspect an antivirus/security software force upgrading that, but I don't think you have one installed on your macOS — which macOS version it is BTW?)

פרסום שאלה

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.