ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

Slow connection to localhost, all time spent in "blocking" and "connecting"

  • 1 การตอบกลับ
  • 0 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย albertymliu

more options

When connecting to a sveltekit development server on localhost, the connection takes 4 seconds to connect. These 4 seconds are almost entirely spent in "blocked" and "connecting." I'm unsure what to do, other development servers I've set up do not have this problem, and other browsers do not have a problem connecting to the sveltekit development server.

OS: Windows 11 Firefox version: 108.0.1 Reproduction code: https://github.com/A1Liu/testing/tree/repro Reproduction: 1. Use Git to clone the repository 2. Checkout the "repro" branch in Git 3. Run the development server by installing dependencies with Yarn and then running 'yarn dev' 4. Go to localhost:5173, open network pane, and then hard refresh

Expected behavior: When hard refreshing, since I'm connecting to a server running on my own computer, the refresh should be fast

Actual behavior: See image. Blocking and connecting both take 2 seconds, everything else takes less than 100 milliseconds combined.

When connecting to a sveltekit development server on localhost, the connection takes 4 seconds to connect. These 4 seconds are almost entirely spent in "blocked" and "connecting." I'm unsure what to do, other development servers I've set up do not have this problem, and other browsers do not have a problem connecting to the sveltekit development server. OS: Windows 11 Firefox version: 108.0.1 Reproduction code: https://github.com/A1Liu/testing/tree/repro Reproduction: 1. Use Git to clone the repository 2. Checkout the "repro" branch in Git 3. Run the development server by installing dependencies with Yarn and then running 'yarn dev' 4. Go to localhost:5173, open network pane, and then hard refresh Expected behavior: When hard refreshing, since I'm connecting to a server running on my own computer, the refresh should be fast Actual behavior: See image. Blocking and connecting both take 2 seconds, everything else takes less than 100 milliseconds combined.
ภาพหน้าจอที่แนบมา

การตอบกลับทั้งหมด (1)

more options

Some things I've tried so far:

1. Open the server in Edge (did not have any network slowness) 2. Open other things on localhost in Firefox (did not have any network slowness) 3. Simplify the code under development (no change) 4. checked for service workers (none found) 5. Edit etc\hosts (no effect) 6. Increase maximum connections allowed through about:config - network.http.max-persistent-connections-per-server (no effect) 7. Only use ipv4 through about:config - network.dns.ipv4OnlyDomains (no effect)

เปลี่ยนแปลงโดย albertymliu เมื่อ