J-Novel Club
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Users

    Site hardly loading / timing-out when using IPv6

    Support
    1
    3
    224
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • hasezoey
      hasezoey Premium Member last edited by hasezoey

      I have recently noticed that jnovel loads very badly sometimes to the point of timing-out. Thanks to another user on discord (in #report-issues) also having a similar problem and then noting that disabling ipv6 for them fixed the issue. Then once it happened to me again (today), i tried forcing j-novel.club to be ipv4 and the problem instantly went away.

      It might also be possible that my previous post was affected by this https://forums.j-novel.club/topic/7692/slow-book-downloads?_=1716305606019

      For reference, the ipv6 that was badly loading was 2a06:98c1:3121::b:.
      DNS provider 2001:4860:4860:0:0:0:0:8888 (google ipv6) & 2606:4700:4700::1111 (cloudflare ipv6).

      Locating: Europe / Germany

      hasezoey 1 Reply Last reply Reply Quote 0
      • hasezoey
        hasezoey Premium Member @hasezoey last edited by hasezoey

        Now some hours later, i see that it actually still happens, even with forced IPv4.

        EDIT: i had just tried re-enabling IPv6, but that made it even worse.
        So my conclusion currently is:

        • IPv6 is definitely broken, with a connection of at max 7kb/s to timeouts
        • IPv4 has a stable connection of 10kb/s to 100kb/s without timeouts

        This happens randomly at times and i dont know why (is it high traffic times?)

        1 Reply Last reply Reply Quote 0
        • hasezoey
          hasezoey Premium Member last edited by

          After creating this issue, i basically forgot about it with the fix of disabling ipv6 for j-novel.club.
          Recently i removed the block on ipv6 and did not have this problem anymore, consider it having been a intermittent problem which is now fixed.

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post