BUGOUT
BUGOUT copied to clipboard
Terkwood
Please wait while we reestablish internet communication
Dears,
thank you for great game development solution,
I'm facing this error in every click "Please wait while we reestablish internet communication"
Hi! This just means that your browser cannot establish a connection to the server. So you'll see this if you have a weak wifi signal, weak cellular connection, or if your device's internet is offline.
Oh, interesting! Well, in that case I'm not sure. Something else is causing trouble with the websocket connection between your browser and the BUGOUT server.
I wonder if you'll experience the same trouble using a different device entirely, either on the same network, or on a different network
OK. So it's probably not your device causing the problem. I wonder what happens if you try from a different network
Hmm! Are you able to see a basic web page when you go here?
https://bg03.terkwood.farm/
This web page is running on the server which handles talking to the AI and dealing with Multiplayer games. I would guess you can't see it,based on the other trouble you're having
Bizarre! I'm stumped. I'll hope for some inspiration to help troubleshoot this, but for now I'm out of ideas.
I asked another friend and they're having the same issue. I'll see if restarting the server helps
Thanks, is their any recommendations for nodejs and npm version or other dependencies not mentioned in the wiki
You really shouldn't have to mess with any of that! This should just work for you 😁 But there is a problem with BUGOUT itself, since my friend is able to reproduce the problem. I'll post again once I have fully restarted the system.
OK, it's restarted now. I'm not very hopeful that this fixed it, but please feel free to try again.
I did raise #514 as a potential avenue of exploration for addressing this issue, though I think it's unlikely it will fix the problem. Thanks very much for raising this issue, you definitely uncovered a weakness in BUGOUT! 🚒
Raising #515 as well. I know that my friend who was able to reproduce this issue was connecting from Europe to the BUGOUT server in AWS us-east-1. Although the bandwidth reported in this thread is really good, there may still be a high latency in the websocket connection.
Wow, it is very flaky under many circumstances. 😅 Thanks so much for making the effort to try from Azure!
it's interested, if you want I can share VPS access information via private message if you want to make any debug
Since you've successfully reproduced the issue in US Azure, I plan to do that also! 🤸🏻♂️ This will give me a personal path for testing and iterating on the behavior.
Previously my tests have come from my own devices, which wasn't a great strategy!😁
the issue her I want to install it :(, what to do to make this success
So far I'm not sure! I apologize for that.
I am pretty confident that this is an issue with the websocket connection between browser and gateway service, but I don't want to estimate the difficulty of the fix until I understand more!
Appreciate your quick response, can I play the role of the fool and share with me detailed instructions for successful installation, please
On Fri, Jun 25, 2021, 5:04 PM Terkwood @.***> wrote:
So far I'm not sure! I apologize for that.
I am pretty confident that this is an issue with the websocket connection between browser and gateway service, but I don't want to estimate the difficulty of the fix until I understand more!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Terkwood/BUGOUT/issues/513#issuecomment-868523880, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUTILIY7Z2WAIEHWTJ5VU5LTUSEHZANCNFSM47HUQWJQ .
Self-hosting BUGOUT is difficult. It is designed for most components to be run in a cloud environment(we use AWS for prod), but the KataGo AI runs on an NVIDIA Jetson nano hosted in my home.
All of this combines for a very difficult developer experience should anyone try to run BUGOUT themselves 😇
There is some incomplete information in the README.
Thanks, I'm taking about BUGOUT, is thier something else needed to be installed rather than nodejs redis server
This what I mean
On Fri, Jun 25, 2021, 5:18 PM Terkwood @.***> wrote:
Self-hosting BUGOUT is difficult. It is designed for most components to be run in a cloud environment(we use AWS for prod), but the KataGo AI runs on an NVIDIA Jetson nano hosted in my home.
All of this combines for a very difficult developer experience should anyone try to run BUGOUT themselves 😇
There is some incomplete information in the README.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Terkwood/BUGOUT/issues/513#issuecomment-868533671, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUTILI3YL24FI2RGIHAXE3TTUSFZ7ANCNFSM47HUQWJQ .
I'm sorry. BUGOUT is pretty difficult to set up locally right now. You do need docker-compose. The distributed nature of the system, with KataGo needing to run on a separate device, which is a specific piece of hardware -- NVIDIA Jetson Nano, is problematic. Further, the design of this system assumes a valid SSL certificate for the cloud portion, so that tinybrain / katago can talk to the cloud deployment.
Some of this is captured in https://github.com/Terkwood/BUGOUT#-stop-potential-developers-please-read-carefully
If you do decide to take on the difficult path of building this locally, we should probably move the discussion to a separate ticket.
Also see #473 and #471 (not necessarily helpful, but related)
Why not and we could help in developing and localized the game
On Sat, Jun 26, 2021, 8:14 PM Terkwood @.***> wrote:
I'm sorry. BUGOUT is pretty difficult to set up locally right now. You do need docker-compose. The distributed nature of the system, with KataGo needing to run on a separate device, which is a specific piece of hardware -- NVIDIA Jetson Nano, is problematic. Further, the design of this system assumes a valid SSL certificate for the cloud portion, so that tinybrain / katago can talk to the cloud deployment.
Some of this is captured in https://github.com/Terkwood/BUGOUT#-stop-potential-developers-please-read-carefully
If you do decide to take on the difficult path of building this locally, we should probably move the discussion to a separate ticket.
Also see #473 https://github.com/Terkwood/BUGOUT/issues/473 and #571 (not necessarily helpful, but related)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Terkwood/BUGOUT/issues/513#issuecomment-869031756, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUTILIZAJJTKDE2EJLD4UC3TUYDFRANCNFSM47HUQWJQ .
Localization is clearly a big need. I'll raise a ticket for that also, so that we can start breaking down the task. My time has been really constrained during the last month; I appreciate the input on all of these problems!
For reproducing on US Azure, this looks like the default solution: https://azure.microsoft.com/en-us/services/virtual-desktop/#features
Hm, what browser and operating system did you use when testing with Azure? I was able to launch a VM in Azure and install Brave browser using Windows Server 2019, then play some moves with KataGo.