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/Paris

If you are running endgame and onionbalance on the same server are you doing it wrong. Onionbalance is designed to combine multiple fronts into a single descriptor for load balancing. One address with multiple fronts holding it up. If you only have a single server just run endgame and pass the ending address to others. No onionbalance needed at all. If you want to have a custom address created use a tool like mkp224o and generate a custom one. You can then transfer the custom one over to your front (replacing the /etc/tor/hidden_service files with the generated one). Then go into /etc/nginx/sites-enabled/site.conf and change out the onion address to your new one. After that reboot and your new custom address should be live on your front.