I wanted to run flaresolverr in a terminal instead as a service. I needed to create the user with this command:
sudo useradd --system -M flaresolverr
Git Clone URL: | https://aur.archlinux.org/flaresolverr.git (read-only, click to copy) |
---|---|
Package Base: | flaresolverr |
Description: | A proxy server to bypass Cloudflare protection |
Upstream URL: | https://github.com/FlareSolverr/FlareSolverr |
Keywords: | captcha cloudflare jackett proxy |
Licenses: | MIT |
Submitter: | txtsd |
Maintainer: | txtsd |
Last Packager: | txtsd |
Votes: | 7 |
Popularity: | 0.68 |
First Submitted: | 2023-01-05 11:20 (UTC) |
Last Updated: | 2024-11-10 06:58 (UTC) |
I wanted to run flaresolverr in a terminal instead as a service. I needed to create the user with this command:
sudo useradd --system -M flaresolverr
Package should be able to install normally now.
If you've installed a misconfigured user using the useradd
command from a comment, you need to remove the package, delete the user, reinstall the package.
pacman -R flaresolverr-bin
sudo userdel flaresolverr
$AUR_helper -S flaresolverr-bin
EDIT: Additionally, if you want to run flaresolverr as a user, add the user to the flaresolverr
group.
I'll try to get the flaresolverr user problem solved by today.
When trying to run as a service I get:
Jan 23 12:59:07 home-arch systemd[1]: flaresolverr.service: Main process exited, code=exited, status=1/FAILURE
Jan 23 12:59:07 home-arch flaresolverr[148309]: }
Jan 23 12:59:07 home-arch flaresolverr[148309]: path: '/home/flaresolverr'
Jan 23 12:59:07 home-arch flaresolverr[148309]: code: 'ENOENT',
Jan 23 12:59:07 home-arch flaresolverr[148309]: syscall: 'access',
Jan 23 12:59:07 home-arch flaresolverr[148309]: errno: -2,
Jan 23 12:59:07 home-arch flaresolverr[148309]: at internal/main/run_main_module.js:17:47 {
Jan 23 12:59:07 home-arch flaresolverr[148309]: at Function.runMain (pkg/prelude/bootstrap.js:1847:12)
Jan 23 12:59:07 home-arch flaresolverr[148309]: at Function.Module._load (internal/modules/cjs/loader.js:778:12)
Jan 23 12:59:07 home-arch flaresolverr[148309]: at Module.load (internal/modules/cjs/loader.js:937:32)
Jan 23 12:59:07 home-arch flaresolverr[148309]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
Jan 23 12:59:07 home-arch flaresolverr[148309]: at Module._compile (pkg/prelude/bootstrap.js:1794:22)
Jan 23 12:59:07 home-arch flaresolverr[148309]: at Object.<anonymous> (/snapshot/FlareSolverr/dist/server.js:30:43)
Jan 23 12:59:07 home-arch flaresolverr[148309]: at testWebBrowserInstallation (/snapshot/FlareSolverr/dist/services/sessions.js:67:8)
Jan 23 12:59:07 home-arch flaresolverr[148309]: at Object.accessSync (pkg/prelude/bootstrap.js:1474:34)
Jan 23 12:59:07 home-arch flaresolverr[148309]: at Object.accessSync (fs.js:229:3)
Jan 23 12:59:07 home-arch flaresolverr[148309]: 2022-01-23T12:59:07-08:00 ERROR Error: ENOENT: no such file or directory, access '/home/flaresolverr'
Jan 23 12:59:07 home-arch flaresolverr[148309]: 2022-01-23T12:59:07-08:00 INFO Testing web browser installation...
Jan 23 12:59:07 home-arch flaresolverr[148309]: 2022-01-23T12:59:07-08:00 INFO FlareSolverr v2.1.0
Not sure if the command "sudo useradd --system --shell=/usr/sbin/nologin flaresolverr" is correct (because it didn't create the home directory for flaresolverr).
Ok thanks, I updated to 2.1.0.
Okay, I added you as co-maintainer. Thanks for helping while I wait on my PSU to be fixed.
@txtsd I maintain 28 packages. If you need help, I can co-maintain or maintain, up to you.
My PSU is fried so I have no access to a desktop atm. In the mean time, if anyone wants to be a maintainer and help, let me know.
To fix the error
chown: invalid user: ‘flaresolverr:flaresolverr’
create the user using the command
sudo useradd --system --shell=/usr/sbin/nologin flaresolverr
For more information, checkout the manpage
Pinned Comments
txtsd commented on 2023-11-13 09:56 (UTC)
This package use to incorrectly build from source in the past. It now correctly builds from an archive of the source without needing dependencies like
git
.Please report any user-agent related errors that stem from running recent versions of Chrome and Chromium upstream.