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

Issue with specifying host in K6 browser experimental feature, leading to virtual user limitation #3685

Closed
dylandifilippo opened this issue Apr 10, 2024 · 2 comments
Assignees

Comments

@dylandifilippo
Copy link

dylandifilippo commented Apr 10, 2024

Brief summary

At work, I'm using the K6 browser experimental feature for testing a website we're going to lunch next week and I cannot specify a host to prevent being flagged as a DDoS attack by the Akamai layer in place, limiting me to 10 virtual users before it breaks.

Using the standard K6 library for average load testing, specifying the host works fine. However, with the K6 browser feature on my Mac, despite setting the host in the K6 script options and using sudo nano /etc/hosts in the terminal, the issue remains.

k6 version

0.50

OS

macOS 14.4.1

Docker version and image (if applicable)

No response

Steps to reproduce the problem

Try to specify an host in the code.

Expected behaviour

Being able to add an host.

Actual behaviour

Not being able to add an host and assuming I'm doing a DDoS attack.

@oleiade
Copy link
Member

oleiade commented Apr 12, 2024

Hi @dylandifilippo 👋🏻

Thanks for reaching out. Could you be more specific as to how the problem you experience manifests itself and provide us a test script we could use to reproduce the issue and assert whether it's related to a bug already? 🙇🏻

cc @ankur22 @inancgumus

@inancgumus
Copy link
Member

inancgumus commented Apr 15, 2024

Hi @dylandifilippo, Thanks for letting us know. We usually prefer it if you first create a new post in our k6 browser community forum so that we can identify exactly what new feature we might need to help with your issue. Closing this issue for now (we can always reopen it later if necessary).

@inancgumus inancgumus closed this as not planned Won't fix, can't repro, duplicate, stale Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants