View comment

Tutorial on how to setup EndGameV3

by /u/nihilist1 · 0 votes · 2024-04-13 16:09:00

Hi everyone,

Endgame needs no introduction, It enables you to scale out your operations with your hidden services.

"Endgame should be on a separate server to your backend server. It only proxies content from your backend to the user. You will still need to configure your backend to handle requests from the Endgame Front. This is the same system that anti-DDOS services like Cloudflare, Indusface, and Imperva use to protect websites from attacks. The difference is this is self-hosted and fully controlled by you for your own needs and made for darknet networks."

Anyways, it's preety simple to setup, and it helps to protect you against DDOS attempts on your .onion service, see my latest tutorial below:

http://blog.nihilhfjmj55gfbleupwl2ub7lvbhq4kkoioatiopahfqwkcnglsawyd.onion/servers/endgame/index.html

As usual, any feedback is appreciated, Make sure to point out what i missed out on, along with what you suggest so that i can improve my tutorials accordingly :)

EDIT (15/04/2024) : added the intended 2 Endgame Fronts, 2 Backend Servers setup as the second half of my tutorial. Check it out!

User: /u/HugBunter

This is the whole premise of onionbalance. It creats a descriptor with multiple onion end points, which are your front servers hosting end game. To dumb it down, the OnionBalance address you supply for users to access, is an alias address masking the front servers that users are connecting to. You access the main Dread onion, but really you are connecting to one of many front servers in our descriptor, these host end game and then proxy pass you to the true backend service. This is how the traffic is spread over multiple servers.