boringproxy: server killed

Hi , boringproxy was running boring and smoothly yesterday with 2 clients , then i tried to add another client the server was killed , first i was thinking maybe there is a number of connections limit , then i deleted one connection and tried again but no luck , server killed, then i started from fresh ; setcap -r boringproxy-xxxxxx deleted boringproxy.json deleted boringproxy-xxxxxx

curl again boringproxy chmod +x setcap settings

aquire certificate and runs nicely , clients can connect without problems , but when i try to add a tunnel , on the terminal prints only “killed”
since there is no logs and no more info prints on the terminal someone know what ca be the problem?? now it`s really boring… to get this works

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 20 (2 by maintainers)

Most upvoted comments

@anderspitman no issues 😃. In case that helps, my authorized_keys file on my tunnel server has 2162688 lines. I don’t know the reason, I have nothing else running on it.