4get configuation options

Welcome! This guide assumes that you have a working 4get instance. This will help you configure your instance to the best it can be!

Files location

The main configuration file is located at data/config.php
The proxies are located in data/proxies/*.txt
The captcha imagesets are located in data/captcha/your_image_set/*.png
The captcha font is located in data/fonts/captcha.ttf

Cloudflare bypass (TLS check)

These instructions have been updated to work with Debian 13 Trixie.

Note: this only allows you to bypass the browser integrity checks. Captchas & javascript challenges will not be bypassed by this program!

Configuring this lets you fetch images sitting behind Cloudflare and allows you to scrape the Yep search engine.

To come up with this set of instructions, I used this guide as a reference, but trust me you probably want to stick to what's written on this page.

First, compile curl-impersonate (the firefox flavor).

git clone https://github.com/lwthiker/curl-impersonate/
cd curl-impersonate
sudo apt install build-essential pkg-config cmake ninja-build curl autoconf automake libtool python3-pip libnss3 libnss3-dev
mkdir build
cd build
../configure
make firefox-build
sudo make firefox-install
sudo ldconfig

Now, after compiling, you should have a libcurl-impersonate-ff.so sitting somewhere. Mine is located at /usr/local/lib/libcurl-impersonate-ff.so. Patch your PHP install so that it loads the right library:

sudo systemctl edit php8.4-fpm.service

^This will open a text editor. Add the following shit in there, in between those 2 comments I pasted for ya just for reference:

### Editing /etc/systemd/system/php8.4-fpm.service.d/override.conf
### Anything between here and the comment below will become the contents of the>

[Service]
Environment="LD_PRELOAD=/usr/local/lib/libcurl-impersonate-ff.so"
Environment="CURL_IMPERSONATE=firefox117"

### Edits below this comment will be discarded

Restart php8.4-fpm. (sudo service php8.4-fpm restart). To test things out, try making a search on "Yep", they check for SSL. If you get results (or a timeout, this piece of shit engine is slow as fuck) that means it works!

Robots.txt

Make sure you configure this right to optimize your search engine presence! Head over to /robots.txt and change the 4get.ca domain to your own domain.

Server listing

To be listed on https://4get.ca/instances , you must contact any of the people in the server list and ask them to add you to their list of instances in their configuration. The instance list is distributed, and I don't have control over it.

If you see spammy entries in your instances list, simply remove the instance from your list that pushes the offending entries.

Proxies

4get supports rotating proxies for scrapers! Configuring one is really easy.

Head over to the proxies folder. Give it any name you want, like myproxy, but make sure it has the txt extension.

Add your proxies to the file. Examples:

# format -> <protocol>:<address>:<port>:<username>:<password>
# protocol list:
# raw_ip, http, https, socks4, socks5, socks4a, socks5_hostname
socks5:1.1.1.1:juicy:cloaca00
http:1.3.3.7::
raw_ip::::

Go to the main configuration file. Then, find which website you want to setup a proxy for.
Modify the value false with "myproxy", with quotes included and the semicolon at the end.

Done! The scraper you chose should now be using the rotating proxies. When asking for the next page of results, it will use the same proxy to avoid detection!

Important!

If you ever test out a socks5 proxy locally on your machine and find out it works but doesn't on your server, try supplying the socks5_hostname protocol instead. Hopefully this tip can save you 3 hours of your life!

4play

4play is a botfaggotry Firefox extension. I made it, and it allows me to control a Firefox browser through code. More information about the project here. It allows you to scrape Google (& probably more sites in the future)

Install the firefox extension onto a clean Firefox profile. Make sure you have a real display connected and that you use real hardware with an user-grade GPU. Websites detect this shit now.
Navigate to /extra/4play/
Install the 4play server: npm install @lawlers/4play
Edit the render-server.js file. Change the line var password = "cnc"; so that it uses a secure password.
Edit /data/config.php and update the 4play password. Also update the FPLAY_EXTERNAL_ENDPOINT so that it points to the render HTTP server.

Now, if you did everything correctly, you should be able to render search pages on scrapers that require it. If your render server sits on a different server, I highly recommend setting up a reverse proxy to add TLS support.

In my case, the 4get website & scrapers sits at the OVH datacenter, while the render server is at my home running on a mini-PC I bought for the occasion. This wouldn't have been possible without your financial support, thank you all!!

5.2 KiB Raw Blame History