Connection keeps closing about bore HOT 15 CLOSED

Got it, let me know how it goes. China's Great Firewall at least is known to
arbitrarily send TCP RST packets to close connections, so it wouldn't surprise me if there were issues in Russia as well.

It seems to be a colab problem. I've protested with and without VPN, with and without DPI bypass. Asked friends from Kazakhstan and Japan, same thing. I would try other services, but either you need to buy there (and russia is on the block), or like in Kaggle it will take hundreds of years to confirm the number

from bore.

As I figure out how to check whether colab or the script is to blame, I'll open it.

from bore.

Could you provide more details — What "output" are you sending through bore? A minimal and reproducible example would be best so I could figure out how to best help you.

from bore.

It seems like a diffusion model of Novel AI.

from bore.

Could you provide more details — What "output" are you sending through bore? A minimal and reproducible example would be best so I could figure out how to best help you.

I am sending via the SD novelAI tunnel. They can give you a link to colab and you will test it yourself, you can also download it if necessary.

from bore.

It might not cause serious problems.
Local port open by webui.(https://github.com/AUTOMATIC1111/stable-diffusion-webui/blob/master/webui.py)
And expose it through bore by command:

bore local 7860 --to bore.pub

In the webui.py, we can see:

def wait_on_server(demo=None):
    while 1:
        time.sleep(0.5)
        if demo and getattr(demo, 'do_restart', False):
            time.sleep(0.5)
            demo.close()   //Cause "connection exited"
            time.sleep(0.5)
            break

from bore.

That's not what this is about. I'm using Naifu (I translated it into English for simplicity.). Constantly no matter what tunnel I catch an error streaming error although when running on the local pk, all is well. Also, bore.pub sometimes just stops working and when you go to it, a 404 error.

from bore.

That's strange. I'm not sure why the connection would not be working. It seems fairly reliable when I use it; connections being dropped has never been an issue from here in Boston.

How often does the connection get dropped? I wonder if it has something to do with your location or network connection?

from bore.

That's strange. I'm not sure why the connection would not be working. It seems fairly reliable when I use it; connections being dropped has never been an issue from here in Boston.

How often does the connection get dropped? I wonder if it has something to do with your location or network connection?

Well, purely in theory in russia with an awesome censorship system (slag) pages are often sluggish. I think I'll use a VPN, see if that helps. If so, I'll close the question.

from bore.

Got it, let me know how it goes. China's Great Firewall at least is known to arbitrarily send TCP RST packets to close connections, so it wouldn't surprise me if there were issues in Russia as well.

from bore.

Thanks for all of this work! Since it shows up on Colab, would you be able to share a minimal Colab notebook with me that is producing problems so I can take a look?

from bore.

Thanks for all of this work! Since it shows up on Colab, would you be able to share a minimal Colab notebook with me that is producing problems so I can take a look?

https://colab.research.google.com/drive/1SRa9ZCBWKNJMoXE5Q6Y0RuvYYvaXllyH?usp=sharing

That's where the error comes in.

from bore.

Thanks. I'm not sure what this notebook is doing, but the error message seems to indicate that a QUIC request is failing — is that what you saw? QUIC is a protocol over UDP, not TCP, so bore wouldn't be able to proxy that.

from bore.

This displays logs from cloudflare tunnel. I update notebook so that it makes a tunnel only through bore
https://colab.research.google.com/drive/1SRa9ZCBWKNJMoXE5Q6Y0RuvYYvaXllyH?usp=sharing

Thanks. I'm not sure what this notebook is doing, but the error message seems to indicate that a QUIC request is failing — is that what you saw? QUIC is a protocol over UDP, not TCP, so bore wouldn't be able to proxy that.

from bore.

Hi @bropines, unfortunately your notebook still shows errors serving a QUIC connection. And I'm not sure where the error is originating since the code is quite complicated and hidden after a few thousand lines of logs. Could you provide a minimal reproduction of the issue?

from bore.