After running for a while, unable to connect to chrome as it's running on different port

[samip5]

Have you checked our README?

• I have checked the README

Have you followed our Troubleshooting?

• I have followed your Troubleshooting

Is there already an issue for your problem?

• I have checked older issues, open and closed

Have you checked the discussions?

• I have read the Discussions

Environment

- FlareSolverr version: 3.3.12
- Last working FlareSolverr version: Not sure
- Operating system: Not applicable, running in Docker/Kubernetes.
- Are you using Docker: [yes/no] Yes, but rather Kubernetes.
- FlareSolverr User-Agent (see log traces or / endpoint):  Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
- Are you using a VPN: [yes/no] No
- Are you using a Proxy: [yes/no] No
- Are you using Captcha Solver: [yes/no] No
- If using captcha solver, which one:
- URL to test this issue: https://idope.se/browse.html

Description

Reproduce:

1. Try to add eg idope with Flaresolverr in Prowlarr
2. Press test
3. See the error when Flaresolverr has been running for more than a week.

Expected:

I would have imagine that it knew which port to connect to, but when I was looking in the container, I can see an chromedirver process running on port 45033 instead of the 52649 which appears in error logs.

Logged Error Messages

2023-12-31 23:52:00 ERROR    Error: Error solving the challenge. Message: Can not connect to the Service /app/chromedriver\n
2023-12-31 23:52:00 INFO     Response in 35.852 s
2023-12-31 23:52:00 INFO     10.244.1.173 POST http://flaresolverr:8191/v1 500 Internal Server Error
2023-12-31 23:52:13 ERROR    Error: Error solving the challenge. Timeout after 60.0 seconds.
2023-12-31 23:52:13 INFO     Response in 69.062 s
2023-12-31 23:52:13 INFO     10.244.1.173 POST http://flaresolverr:8191/v1 500 Internal Server Error
2023-12-31 23:55:49 INFO     Incoming request => POST /v1 body: {'maxTimeout': 60000, 'cmd': 'request.get', 'url': 'https://idope.se/browse.html', 'proxy': {}}
version_main cannot be converted to an integer
2023-12-31 23:56:59 ERROR    Error: Error solving the challenge. Message: unknown error: cannot connect to chrome at 127.0.0.1:52649\nfrom chrome not reachable\nStacktrace:\n#0 0x56534a50e203 <unknown>\n#1 0x56534a1d7e6e <unknown>\n#2 0x56534a1c6131 <unknown>\n#3 0x56534a210034 <unknown>\n#4 0x56534a207825 <unknown>\n#5 0x56534a25a370 <unknown>\n#6 0x56534a259957 <unknown>\n#7 0x56534a24f1a3 <unknown>\n#8 0x56534a21413e <unknown>\n#9 0x56534a215712 <unknown>\n#10 0x56534a4e3504 <unknown>\n#11 0x56534a4e6729 <unknown>\n#12 0x56534a4e6208 <unknown>\n#13 0x56534a4e6bd5 <unknown>\n#14 0x56534a4d5a8f <unknown>\n#15 0x56534a4e6f5e <unknown>\n#16 0x56534a4bfc56 <unknown>\n#17 0x56534a4ff3b5 <unknown>\n#18 0x56534a4ff59b <unknown>\n#19 0x56534a50d78f <unknown>\n#20 0x7f5ebff45ea7 start_thread\n
2023-12-31 23:56:59 INFO     Response in 70.905 s
2023-12-31 23:56:59 INFO     10.244.1.173 POST http://flaresolverr:8191/v1 500 Internal Server Error

Screenshots

No response

[ilike2burnthing]

Please provide the OS of the host device Kubernetes is running on and the response to uname -a.

Mostly just for reference, but feel free to look at these:
#1004
#986
#932

[samip5]

Debian 12 and uname -a:
Linux w-amd-3 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) x86_64 GNU/Linux
Linux w7 6.1.0-15-arm64 #1 SMP Debian 6.1.66-1 (2023-12-09) aarch64 GNU/Linux
Linux w-amd-storage-1 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) x86_64 GNU/Linux
Linux w1 6.1.0-15-arm64 #1 SMP Debian 6.1.66-1 (2023-12-09) aarch64 GNU/Linux

[ilike2burnthing]

These are 4 separate devices, and are all similarly affected with different FlareSolverr containers?

[samip5]

These are 4 separate devices, and are all similarly affected with different FlareSolverr containers?

Correct.

[ilike2burnthing]

Is there anything in the logs before this happens about Chrome crashing, or any other errors? Might go some way to explaining why Chrome is running on a different port.

How much RAM do you have for each of the devices? Are you setting any resource limits for the containers?

[samip5]

Is there anything in the logs before this happens about Chrome crashing, or any other errors? Might go some way to explaining why Chrome is running on a different port.

There is nothing about Chrome crashing, but instead it seemed to have stalled (aka not processing things), but still somehow not crashing.

How much RAM do you have for each of the devices? Are you setting any resource limits for the containers?

It varies, but most of them have plenty (2GB+) free. No resource limits originally.

[ilike2burnthing]

Unlikely to resolve your issue, but v3.3.13 is now out, please try it.

[ilike2burnthing]

Please test with v3.3.16.