Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proxitok-chromedriver exited - code 255 #233

Open
ac615223s5 opened this issue Sep 10, 2024 · 0 comments
Open

proxitok-chromedriver exited - code 255 #233

ac615223s5 opened this issue Sep 10, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ac615223s5
Copy link

ac615223s5 commented Sep 10, 2024

Before submitting an issue, please make sure you are using the latest version of ProxiTok.

Describe the bug
proxitok-chromedriver container randomly stops with exited - code 255

To Reproduce
happens after a few hours
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Logs
If applicable, add PHP logs to help explain the issue.
no error in logs

Starting ChromeDriver 

All remote connections are allowed. Use an allowlist instead!

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.

ChromeDriver was started successfully.

Environment (please complete the following information):
Frontend version: 2.5.0.0

Scraper version: 2.6.2.0

docker

  • Deployment method (if possible): [e.g docker, heroku, manual...]
  • Frontend version: [e.g. 2.2.0.0]
  • Scrapper version: [e.g. 2.4.0.0]
  • PHP Version: [e.g. 8.0]

You can find the frontend and scrapper version on /about

@ac615223s5 ac615223s5 added the bug Something isn't working label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant