Too many request about flaresolverr

[CxTracker]

This loser was fucking with mine too
In your docker-compose.yml change the ports option to this, this will stop the retard viewbotting and block anyone from outside your local network from sending requests to it.

ports: - "127.0.0.1:8191:8191"

[CxTracker]

Thanks for the tip, it's ok now but I don't understand who make theses calls on flaresolverr ports from outside ?

a cybercriminal, using it to viewbot.

[CxTracker]

FlareSolverr should be behind your router's firewall and should not be port-forwarded.

On dedicated servers you have no port forwarding. This is an issue for people on dedicated linux servers, not noobs using windows.

[Mrmel94]

Same here I thought the problem was on my side, but even after stop my apps that pointed on flaresolverr I have this incoming request on piped.xyd.lol that failed every second.

[Mrmel94]

Thanks for the tip, it's ok now but I don't understand who make theses calls on flaresolverr ports from outside ?

[ilike2burnthing]

Don't expose FlareSolverr to the internet.

[bob1321]

@ilike2burnthing Why I would expose to the internet? Im in a docker and use your installation method…

[ilike2burnthing]

FlareSolverr should be behind your router's firewall and should not be port-forwarded.

[CxTracker]

Don't expose FlareSolverr to the internet.

FlareSolverr's default docker container should be local network only.
Currently its setup to be publicly open.

[UnicodeApocalypse]

@CxTracker Even if you look like an agressive a**hole here is your fix looser :
iptables -I INPUT -p tcp --dport 8191 -j DROP

[CxTracker]

@CxTracker Even if you look like an agressive a**hole here is your fix looser : iptables -I INPUT -p tcp --dport 8191 -j DROP

I don't need a fix, I just put the container on local network instead, as i said in my above posts.